Changed/Updated Linux O/S and reinstalled Duplicacy. Now I can’t get gnome-keyring to save the Duplicacy Master Password; it simply never saves. Is there a configuration process that I’m not finding this time?
Old O/S was KDE-Neon. New O/S is Kubuntu. Neither uses Gnome by default, but apparently that’s the only keyring/wallet that Duplicacy will work with.
Thanks!
Lance
Check if dbus is running and if DBUS_SESSION_BUS_ADDRESS is set to the correct address. You can try running the CLI with a test repository to see if the password can be stored. The web GUI and the CLI use the same code to retrieve passwords from gnome-keyring.
With a fair amount of trial and error, here’s what is needed for those of us not using a gnome based system:
You need to install:
• gnome-keyring, plus whatever dependencies it needs
• seahorse, plus whatever dependencies it needs
Seahorse is the GUI for gnome-keyring (and a few other privacy tools).
Use seahorse to create a gnome keyring for your Duplicacy Master Password, and other gnome-like applications. You should name the keyring login; that is still a requirement on some systems. Use seahorse, again, to set login as your default keyring; remember, this only affects gnome-like applications.
Here’s where it gets weird:
Since no one wants to be asked to enter a separate keyring passphrase every time you sit-down at your computer, you have two options:
There isn’t a third option; it’s either lockup both your user login and your keyring, or lockup neither.
For those of us backing-up a home, or a home-office computer, letting the Duplicacy Master Password sit exposed on an unlocked keyring makes perfect sense. Here’s why:
If your adversary has physically broken into your house or office, and is sitting in front of your unencrypted computer, s/he does not need to hack into your backups, because they already have your entire computer, and everything on the hard drive!
So, the Duplicacy Master Password is really only advantageous if you have a group of users (employees, students, etc.), with multiple computers, backing-up to a common storage. In that scenario having a password login (therefore a locked keyring) helps limit exposure if one computer is lost or stolen—your other computers’ backups are not also placed at risk. If this is you, use seahorse to set the keyring password to match your computer login password.
But if you’re like me, running a one-person office; go crazy, and store your Duplicacy Master Password in the clear. Your remote backups are still secure, because that’s handled by the encryption password, not by the Duplicacy Master Password.
Thank you for such detailed information. This is very helpful!