BIT doesn't work when location is encrypted

Bug #1440639 reported by .
6
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

Tags: encryption
Revision history for this message
Germar (germar) wrote :

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/documentation/usercallback/). With BIT >= 1.1.0 you can use reason $3=7 for mount scripts and $3=8 for unmount scripts

Revision history for this message
. (jbrown3264) wrote :

I'm using Fedora default which looks like dm-crypt+luks.

Yes, the drive happened to not be unlocked or mounted at the same. But, I did not see any message about not being able to find snapshots, only the crash reporter.

I'm using the BIT scheduler, unsure it it's running as root or user by default.

Not sure if that script is applicable to the scenario, now. Or is it?

Thanks for your help!

Revision history for this message
Germar (germar) wrote :

If you didn't start BIT with 'Back In Time (root)' you're running as normal user.

Please run 'env -i HOME=$HOME DISPLAY=$DISPLAY PATH=$PATH backintime --backup-job' from Terminal and post the output in here if it crashes again. Otherwise please run 'crontab -e' and replace '>/dev/null' with '>/tmp/bit.log'. Then wait for BIT to crash again and post /tmp/bit.log

You'd need to write your own script for this of course. Something like 'cryptsetup luksOpen <name> <device>' in combination with ssh-askpass to get a GUI password dialog.

Germar (germar)
Changed in backintime:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Back In Time because there has been no activity for 60 days.]

Changed in backintime:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.