Problem with gnome keyring after upgrade to 1.0.22

Bug #1162299 reported by Daniel Betschart on 2013-03-30
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Back In Time
Fix Released

Bug Description

I cannot change settings if I call BackInTime as root. Even I have not changed some thing, after clicking the OK butten I receive:
Can't connect to gnomekeyring to save password.
I can close the settings dialog only with the button cancel. It is not possible to do changes anymore.

Germar (germar) wrote :

Thanks for reporting this. For workaround you can switch Mode to SSH deactivate 'Save Password to Keyring' and switch back to Mode Local.

Changed in backintime:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Germar (germar)
gerlos (gerlosgm) wrote :

I confirm that this workaround works: in general tab, just switch to "ssh", untick "save password to keyring" and then switch back mode to "local".
I suppose this change exposes my password in some configuration file, is it right?

Germar (germar) wrote :

Nope. Your password will never be stored in a config file. BIT does only save passwords to systems keyring (gnome-keyring aka seahorse for gnome or kwallet for kde) which will store them them encrypted with your users password.

This bug has two reasons:
- first I forgot to limit the check for keyring only to modes that needs passwords (mode local does not). This is already fixed for the next version. I also set 'save password' to default off to avoid other problems with existing profiles.
- second I didn't recognised that keyring isn't available in a 'sudo' session. For this I don't have a solution yet.


Daniel Betschart (dbet1) wrote :

Thank your for clarification and the workaround. Whith this it works now for me.

Germar (germar) on 2013-05-21
Changed in backintime:
status: Confirmed → Fix Committed
Germar (germar) on 2013-09-07
Changed in backintime:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions