On Thursday 09 June 2016 08:46:49 Hans Vanpee wrote: > Tobias Ellinghaus <me@...> writes: > > Tobias Ellinghaus <me <at> ...> writes: > > Unless you provide a link to the specifications that guarantee that > > "Login" > > exists that would be no better than using "darktable" I fear. > > This text explains how the "Login" keyring works: > https://wiki.gnome.org/Projects/GnomeKeyring/Pam
That is Gnome specific. Doesn't apply to us. > > Oh, good catch. I wonder why no one found that bug earlier. Thank you very > > much. I will have a look and fix that at least. > > You're welcome, it took me some time to find this. > > > See above, it's not a fix, just a band aid hiding the problem for you (and > > maybe others, we don't know that). > > I left the code to create the new collection when "Login" is not found. I > should add some code to check for "darktable" when "Login" isn't there so we > can manage both. But the advantage of the "Login" collection is that it > gets unlocked automatically when logging into the system. > > With our own collection the user needs to create a new password or leave the > credentials unprotected (this is how I understand things from reading the > documentation). Most Gnome applications seem to use the "Login" collection > as it makes everything transparent to the user. darktable is not a Gnome application. > > > I'll try to get the patch to you somehow. > > done. > > Before continuing we'll need to decide which way to go: login, darktable or > both. > > Hans > > > ___________________________________________________________________________ > darktable developer mailing list > to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
signature.asc
Description: This is a digitally signed message part.
