BIT doesn't work when location is encrypted
Bug #1440639 reported by
.
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Back In Time |
Expired
|
Undecided
|
Unassigned |
Bug Description
When BIT is set for scheduled backups on a location, such as another hard drive, which is encrypted, it does not recognize this and immediately crashes.
Recommendation for a fix here would be that BIT at least recognize encrypted drives and either
1) Execute the unlock mechanism prompt
2) Display an error (with option to continue) that the drive is encrypted
Changed in backintime: | |
status: | New → Incomplete |
To post a comment you must log in.
Which encryption do you use (dm-crypt+luks, Truecrypt, encfs, ...)? Normally if your drive is encrypted and it's not unlocked it's not mounted neither. So BIT will not find the snapshot path. In this case BIT should show a message "Can't find snapshots folder. If it is on a removable drive please plug it." and wait for 30sec for the path to become available. Do you get this message? Do you run BIT as user or as root?
To run some script which will unlock your drive you can use user-callback (http:// backintime. le-web. org/documentati on/usercallback /). With BIT >= 1.1.0 you can use reason $3=7 for mount scripts and $3=8 for unmount scripts