Repository info doesn't indicate RSA encryption being used

Bug
#1

Please describe what you are doing to trigger the bug:

Following the instructions here: RSA encryption · gilbertchen/duplicacy Wiki · GitHub

I ran 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!

#2

Run duplicacy -d info storage_url and the RSA public key will be displayed.

#3

Do you mean do NOT replace storage_url with my predefined storage URL? When I do that, I get an error right away:

derek@localhost:/.duplicacy# duplicacy -d info storage_url

Unrecognizable storage URL: storage_url
#4

It does not seem like duplicacy -d info storage_url is giving any information about RSA encryption as described in New feature: RSA encryption

$ ~/../duplicacy/.duplicacy-web/bin/duplicacy_linux_x64_2.7.2 -d info /volume2/backup/duplicacy_store
The storage is encrypted with a password
nas_docs
nas_media

I had to use the list command to get the relevant info:

$ ~/../duplicacy/.duplicacy-web/bin/duplicacy_linux_x64_2.7.2 -d list -r 1
Repository set to /volume1/private/docs
Storage set to /volume2/backup/duplicacy_store
Reading the environment variable DUPLICACY_LOCAL_DUPLICACY_STORE_PASSWORD
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 storage password:*******************************************
Using 16384 iterations for key derivation
Chunk read levels: [1], write level: 1
Compression level: 100
Average chunk size: 4194304
Maximum chunk size: 16777216
Minimum chunk size: 1048576
Chunk seed: xxx
Hash key: xxx
ID key: xxx
File chunks are encrypted
Metadata chunks are encrypted
Data shards: 5, parity shards: 2
RSA public key: -----BEGIN PUBLIC KEY-----
MIIB...
...
...
-----END PUBLIC KEY-----

Reading the environment variable DUPLICACY_LOCAL_DUPLICACY_STORE_PASSWORD
Failed to store the value to the keyring: keyring/dbus: Error connecting to dbus session, not registering SecretService provider: dbus: DBUS_SESSION_BUS_ADDRESS not set
id: nas_docs, revisions: [1], tag: , showFiles: false, showChunks: false
Chunk size: 550 bytes, data size: 1032, parity: 5/2
Downloaded file snapshots/nas_docs/1
Snapshot nas_docs revision 1 created at 2020-12-03 17:09 -hash
#5

My bad. info isn’t supposed to tell you all the details about a storage – it can only tell if the storage is encrypted or not. Yes, duplicacy -d list is the right way.