-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New security changes broke remote access to repos #292
Comments
Right, I sort of expected that somebody would run into something like this. We could always extend this feature to a list of known locations. |
It is triggered by the script, but when I try to do it manually, its the same things. Furthermore, even if it gets fixed, I would suggest that the list of secure locations is an opt-in feature. For people who travel a lot with their laptops, it makes attic not work on its defaults. |
Same problem here. Created the repository like that:
Now, if I try something like the following:
|
Attic-0.15 (and possibly earlier -- didn't check when it was introduced) checks if an environment variable |
I just ran into this after rsyncing an attic repo to a different vps. I was able to fix it using that environment variable. I'm on 0.16. |
If one is consistently using same pathes (always absolute xor always relative (with same amount of dir levels)) and also is consistent about using or not using trailing slashes, this issue does not happen. os.path.normpath could solve some of these cases, but not all. |
If I have a backup server which can be accessed with public IP and LAN IP, updating a repo from public IP makes it inaccessible from LAN IP (and vice-versa):
The text was updated successfully, but these errors were encountered: