Please describe what you are doing to trigger the bug:
Following the instructions here: RSA encryption · gilbertchen/duplicacy Wiki · GitHub
duplicacy -d info storage_url (replaced
storage_url with what I have defined in my
preferences file) to verify that RSA encryption was enabled but all that came back was that “The storage is encrypted with a password”:
derek@localhost:~/testrestore$ duplicacy -d info wasabi://… Reading the environment variable DUPLICACY_WASABI_KEY Failed to get the value from the keyring: keyring/dbus: Error connecting to dbus session, not registering SecretService provider: dbus: DBUS_SESSION_BUS_ADDRESS not set Enter Wasabi key:*** Reading the environment variable DUPLICACY_WASABI_SECRET Failed to get the value from the keyring: keyring/dbus: Error connecting to dbus session, not registering SecretService provider: dbus: DBUS_SESSION_BUS_ADDRESS not set Enter Wasabi secret:*** The storage is encrypted with a password localhost
Please describe what you expect to happen (but doesn’t):
I expected to see the RSA key that I had used to initialize the repository or at least some indication that RSA encryption is being used.
Please describe what actually happens (the wrong behaviour):
No RSA key is output but I can confirm that RSA encryption is being used because when I attempt to restore a file from this repository, I am prompted for both the storage password (if it’s not already in my
preferences file) and the private RSA key:
derek@localhost:~/testrestore$ duplicacy restore -r 1 test.txt Storage set to wasabi://… Enter storage password:** Loaded 1 include/exclude pattern(s) Parsing filter file /home/derek/testrestore/.duplicacy/filters Loaded 0 include/exclude pattern(s) Restoring /home/derek/testrestore to revision 1 An RSA private key is required to decrypt the chunk
The fact that
info never displayed an RSA key threw me for a loop many times during initial repository setup because duplicacy never confirmed whether my
init command had successfully worked with the key I provided. Some sort of confirmation would have been nice!