bug: password not found in secret manager

[yvan-algoo]

Hi Bux,

I would like trsync_manager to retrieve the Tracim instance password has described in the README:

trsync_manager will try to get passwords from system secret manager with key trsync::<instance name> and current logged user as user.

• In ~/.trsync.conf, I have a Tracim instance called algoo
• In Seahorse (Gnome's secret manager), I have created a password with description trsync::algoo
• But when I run trsync_manager it says:

ERROR trsync_core::config] Unable to read password from config for instance 'algoo.tracim.fr' and user 'yvan', this instance will be ignored : 'No matching entry found in secure storage'

Do you have a idea about what I am doing wrong?

Thanks,
Yvan

[buxx]

Hello @yvan-algoo !
I have to investigate a bit to take a look about which key is expected in secret manager.
Hope find some time in next days :)

[buxx]

@yvan-algoo I think the documentation is wrong and the key should be (example for mon.tracim.fr) : trsync::mon.tracim.fr.

[buxx]

@yvan-algoo If you are using trsync_manager standalone (without trsync_systray). Please not I just updated the repository with fixed version.

I'm publishing a new release.

[buxx]

@yvan-algoo I found how password should be manually stored. I updated the doc : 51ffeab

[yvan-algoo]

Thanks @buxx ! I tried what you explain but trsync still doesn't find the password. I don't know how these secret managers are queried, but maybe it is just Seahorse that is not "standard" and thus not compatible with trsync?

[buxx]

@yvan-algoo Seahorse is just a graphic interface for system secret manager. I tested with success deployment of trsync_manager and manually set password with

secret-tool store --label "TrSync MyInstance" application rust-keyring service trsync::<instance address> username <linux logged username>

Are you able to "read" the password with command

secret-tool lookup application rust-keyring service trsync::<instance address like mon.tracim.fr> username <linux user like root>

?

[yvan-algoo]

Thanks for the explanation! It works now for me.

Here is what I understood, based on your explanations, my reading and some testing. It may be obvious but it was not for me, so it might be useful for others:

• "system secret manager" refers to any application which implement the freedesktop.org Secret Service DBUS API (https://specifications.freedesktop.org/secret-service-spec/latest/index.html), which is Gnome Keyring in my case, and its GUI Seahorse. The KDE equivalent seems to be KDE Wallet.
• trsync_manager searches for a login that MUST have the following attributes:
  • application = rust-keyring
  • service = trsync::<tracim instance FQDN>
  • username = <user running trsync_manager>
• I do know if the property schema = org.freedesktop.Secret.Generic is required or not.
• The login can indeed be added to the system secret manager with the above command. It can not be added with Seahorse (at least with version 3.36-1 I am using) because you can not create/edit the required attributes.
• You can show the items stored in the system secret manager with secret-tool, as long as you provide a "filter" like:
  • secret-tool search --all xdg:schema org.gnome.keyring.Note
  • secret-tool search --all xdg:schema org.freedesktop.Secret.Generic
  • secret-tool search --all username <your username>

Maybe @buxx you could also add to the README.md the required attributes (application, service and username, and maybe schema)?

Thanks again :-)