Mounting encfs under /tmp might be a bad idea.
Bug #1374343 reported by
ivh
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Back In Time |
Fix Released
|
Critical
|
Germar |
Bug Description
I used backintime 1.0.34 from Debian/jessie with a local (usb-disk) encrypted volume. It turns out the gnome-settings-
I don't want to start the blame-game between gnome and backintime, but ask whether /tmp is a good choice of mount point at all.
Related branches
Changed in backintime: | |
milestone: | none → 1.0.38 |
status: | Triaged → Fix Committed |
Changed in backintime: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Urgs! That's really bad! Didn't know of such a 'feature'. I'm already downloading jessie image to confirm this in a VM.
We choosed /tmp because it get cleaned up during restart (or when speaking correctly, it is a ram disk which doesn't survive a reboot). So if the mountpoint would get messed up for what ever reason it would work again after next reboot. Also we need to have a path which is writeable for every user.