Tobias Ellinghaus <me@...> writes:
> Wrong. darktable uses whatever it's configured to use. True. It is the automatic selection that goes to kwallet for KDE and libsecret for the other desktops. Does KDE come with kwallet by default and is libsecret an option? Libsecret is a Gnome project so I suppose it is well integrated with the Gnome desktop. > Libsecret itself doesn't store any passwords. It's just an abstraction so that > applications (like dt) only need to talk to one service. In the background the > secret service is supposed to hand the data to Gnome Keyring, Kwallet or > others. So eventually only libsecret should be needed to make everyone happy. Correct. In my first patch I used gnome-keyring specific standards (libsecret rreplaces libgnome-keyring but it can use gnome-keyring as a secret service). > However, until now I didn't find any way to actually configure what backend > should be used. Or to determine which is used. secret_service_get_sync() gets a proxy for "the" secret service. Does this mean that only one secret service can run at the same time? Or is there a mechanism to select one of several as default? This is all new to me and I dived in this stuff because I was frustrated with redefining my connections every day. > As pointed out that is only true for the "auto" setting. I agree, I wrongly took the default selection as the only option. > Directly talking to kwallet works like a charm. But that is not the issue we > are having. The problem is that libsecret isn't working as intended. And > limiting its use to environments where Gnome Keyring is used in the back is > not acceptable as it's intended to work across different DEs. I fully agree. The two problems I found in backend_libsecret.c are: - searching for the existing "darktable" keyring returned the first keyring found (due to the g_strcmp0() interpretation bug) - using "darktable" as an alias when creating a new keyring. Libsecret seems to support only the "default" alias (that is what the error message says when trying another value). Changing the user's default to darktable would be bad behavior, so I use no alias at all in my second patch. I do use the default keyring if one exists, but that can be changed very easily. Could you try the patch on your system? I am interested to know if it solves the problem in other environments than Gnome-desktop/gnome-keyring? Hans ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
