Change library backend (from gnomekeyring to universal keyring)

[wilzbach]

For some reason, some items have a name in seahorse that is not accessible by gnomekeyring library, only their 'description'. So it might seem that you can only query for some items (the items created in the old keyring). It's probably cased by the fact that newer GNOME moved to SecretService backend. There's a library that might be better than the current one to access these items:

https://pypi.python.org/pypi/keyring

keyring provides support for OSXKeychain, KDEKWallet, GnomeKeyring, SecretServiceKeyring, WinVaultKeyring, Win32CryptoKeyring, CryptedFileKeyring, UncryptedFileKeyring

[kparal]

Yeah, but see the readme. I don't intend to develop this further. But if you decide to provide a patch, I'll be glad to merge it if it looks reasonable.

[wilzbach]

I currently don't have time either, but I wanted to create this issue in case anyone (maybe even myself in the future) wants to contribute to this project.

[fedelibre]

For the records: the mentioned keyring is not only a library, but also a command-line utility. So it's enough to set mutt and related applications (like mbsync) correctly.
On Linux you need these two packages:

sudo pip install keyring secretstorage

[kparal]

FWIW, I've just played with secret-tool command line utility which is a part of the official libsecret library, and it's fully capable of performing basic operations with the keyring. I like it more than the aforementioned keyring library (but it's not that universal).

Because Python 2 is going away, and gkeyring uses a Python2-only library as the backend (now even obsolete), and there is a good enough replacement with secret-tool at least for my use cases, I'll most probably mark gkeyring as obsolete very soon. People are of course welcome to fork this code and if they have any reasonable improvements over my version, I'll gladly redirect visitors towards their project instead.