Can't backup to same area with different user
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Back In Time |
Fix Released
|
Critical
|
Unassigned |
Bug Description
Back In Time 0.9.99.37 Ubuntu 10.04
If you backup to an area as one user, and then try to backup to the same area as another user it fails.
Login as User1
Set Where to save snapshots: /var/tmp
Take backup
Login as User2
Set Where to save snapshots also to: /var/tmp
Take backup
Backup fails with permission denied/unable to write to backup area since /var/tmp/backintime and /var/tmp/
If its supposed to be this way then no problem as its easy to workaround, and its not clear any of the alternatives are any better. Its not actually a problem I have, just something I noticed. As you've considered all of this when creating profiles I was wondering what your thoughts were?
Current backup path:
SNAPSHOTLOCA
backintime/ - user writable
MACHINE/ - user writable
USER/ - user writable
Issue:
Once one user uses the location, they have sole write permissions to the area (they can use different machines in the area, but other users can't use the area even on the same machine)
Option 1:
Issue can be avoided if users specify a different Where to save Snapshot directory/
But this means you are specifying user directory twice (not a bit deal, but then why have USER subdirectory)
SNAPSHOTLOC
Option 2:
Change permissions on top levels to allow write access:
SNAPSHOTLO
But this means another user can rename the MACHINE directory (or even backintime directory) to another name to 'hide' it from the other users, even if they can't delete the directory (since its contents can't be deleted)
Option 3:
Change the order of the backup path to per user only:
SNAPSHOTLOC
backintime - world writable
USER - user writable
But you still have the issue with backintime being world writable
Although you could make the argument that SNAPSHOTLOCATION has that issue as well so it doesn't matter
Option 4:
Change to user at top level:
SNAPSHOTLOC
USER - user writable
or to make it more specific to backintime:
SNAPSHOTLOC
or the same as now, or something else...
Changed in backintime: | |
status: | Confirmed → Fix Committed |
Changed in backintime: | |
status: | Fix Committed → Fix Released |
This is not the way it should work. "backintime/host" should be available to everybody. "backintime/ host/user" should be seen only by user. This is a huge bug.