Created attachment 741348 [details] emerge--info.txt Currently protonmail-bridge depends on app-crypt/libsecret - I presume it is to fulfill keychain requirements for the program (program requires some form of keychain to store passwords). But according to official repo (see README.md file section "Keychain" in protonmail-bridge github repo) protonmail-bridge right now only works with gnome-keyring or pass - I personally use gnome-keyring. mail-mta/protonmail-bridge-bin somehow pulled in gnome-keyring as dependency, although quickly looking back at repo I don't see it stated explicitly. Anyway, after removal of protonmail-bridge-bin I had to install gnome-keyring manually to have protonmail-bridge still working so it looks to me dependencies need some fixing. I'll attach emerge--info.txt just in case, although I doubt its needed.
protonmail-bridge does not require any specific Secret Service API provider, that's what libsecret is here for. As for what the README says - one really cannot expect upstream to test, or even know about, every single SS-API provider out there... Anyway, SS-API providers are now pulled in by virtual/secret-service - which currently allows choosing between Gnome Keyring and KeepassXC. I for one have been using protonmail-bridge (as well as quite a few other programs) with the keyring managed the latter since June, without any problems.
I can see here that protonmail-bridge itegrated itself with my app-admin/pass. Maybe we should extend virtual/secret-service with app-admin/pass?
Thank you for reply. I can confirm now that protonmail-bridge can indeed work with Secret Service providers other than gnome-keyring or pass - I've managed to make it work with KeepassXC. My previous assessment resulted from some github tickets which suggested to me that protonmail-bridge officialy only supports gnome-keyring and pass and my failure to make it work with KeepassXC previously (which was due to my misunderstanding how protonmail-bridge works with keyring).
(In reply to Piotr Karbowski from comment #2) > I can see here that protonmail-bridge itegrated itself with my > app-admin/pass. Maybe we should extend virtual/secret-service with > app-admin/pass? Once you have run-tested it enough to be satisfied that it works properly, go ahead.
Ok, right now I'll have to go back with this to something other than "RESOLVED" - marking as UNCONFIRMED. Explanation: unmerging gnome-keyring broke my protonmail-bridge. It looks like even if protonmail-bridge can use secret service API and actually uses it to communicate with it, it is hardcoded to work only with pass or gnome-keyring. There's actually an open pull request in protonmail-bridge repo intending to fix that (https://github.com/ProtonMail/proton-bridge/pull/217), but as of now protonmail-bridge requires either pass or gnome-keyring in the system.
Hacky solution to this problem could be adding dummy gnome-keyring executable file somewhere in PATH, as flatpak for protonmail-bridge does: https://github.com/flathub/ch.protonmail.protonmail-bridge/commit/266c7c4c0745de0fd2363394ea0e771c82b6342e That's how I can make it work with keepassxc and gnome-keyring unmerged
