All Versions
Latest Version
Avg Release Cycle
37 days
Latest Release

Changelog History
Page 11

  • v0.9.2 Changes

    • Keyring 0.9.1 introduced a whole different storage format for the CryptedFileKeyring, but this introduced some potential compatibility issues. This release incorporates the security updates but reverts to the INI file format for storage, only encrypting the passwords and leaving the service and usernames in plaintext. Subsequent releases may incorporate a new keyring to implement a whole-file encrypted version. Fixes #64.
    • The CryptedFileKeyring now requires simplejson for Python 2.5 clients.
  • v0.9.1 Changes

    • ๐Ÿ›  Fix for issue where SecretServiceBackend.set_password would raise a UnicodeError on Python 3 or when a unicode password was provided on Python 2.
    • CryptedFileKeyring now uses PBKDF2 to derive the key from the user's password and a random hash. The IV is chosen randomly as well. All the stored passwords are encrypted at once. Any keyrings using the old format will be automatically converted to the new format (but will no longer be compatible with 0.9 and earlier). The user's password is no longer limited to 32 characters. PyCrypto 2.5 or greater is now required for this keyring.


    • โž• Add support for GTK 3 and secret service D-Bus. Fixes #52.
    • Issue #60 - Use correct method for decoding.
  • v0.8.1 Changes

    • ๐Ÿ›  Fix regression in keyring lib on Windows XP where the LOCALAPPDATA environment variable is not present.


    • ๐Ÿ”’ Mac OS X keyring backend now uses subprocess calls to the security command instead of calling the API, which with the latest updates, no longer allows Python to invoke from a virtualenv. Fixes issue #13.
    • When using file-based storage, the keyring files are no longer stored in the user's home directory, but are instead stored in platform-friendly locations (%localappdata%\Python Keyring on Windows and according to the Base Dir Specification ($XDG_DATA_HOME/python_keyring or $HOME/.local/share/python_keyring) on other operating systems). This fixes #21.

    Backward Compatibility Notice

    Due to the new storage location for file-based keyrings, keyring 0.8 ๐Ÿ‘Œ supports backward compatibility by automatically moving the password โšก๏ธ files to the updated location. In general, users can upgrade to 0.8 and continue to operate normally. Any applications that customize the storage location or make assumptions about the storage location will need to take โฌ†๏ธ this change into consideration. Additionally, after upgrading to 0.8, โฌ‡๏ธ it is not possible to downgrade to 0.7 without manually moving ๐Ÿ”ง configuration files. In 1.0, the backward compatibility ๐Ÿšš will be removed.

  • v0.7.1 Changes

    • โœ‚ Removed non-ASCII characters from README and CHANGES docs (required by distutils if we're to include them in the long_description). Fixes #55.


    • โœ… Python 3 is now supported. All tests now pass under Python 3.2 on Windows and Linux (although Linux backend support is limited). Fixes #28.
    • ๐Ÿ Extension modules on Mac and Windows replaced by pure-Python ctypes implementations. Thanks to Jerome Laheurte.
    • ๐Ÿ›  WinVaultKeyring now supports multiple passwords for the same service. Fixes #47.
    • โœ… Most of the tests don't require user interaction anymore.
    • Entries stored in Gnome Keyring appears now with a meaningful name if you try to browser your keyring (for ex. with Seahorse)
    • โœ… Tests from Gnome Keyring no longer pollute the user own keyring.
    • keyring.util.escape now accepts only unicode strings. Don't try to encode strings passed to it.
  • v0.6.2 Changes

    • ๐Ÿ›  fix compiling on OSX with XCode 4.0
  • v0.6.1 Changes

    • Gnome keyring should not be used if there is no DISPLAY or if the dbus is not around (

    • โž• Added keyring.http for facilitating HTTP Auth using keyring.

    • โž• Add a utility to access the keyring from the command line.

  • v0.5.1 Changes


    • Now using the existing Gnome and KDE python libs instead of custom C++ code.

    • Using the getpass module instead of custom code


    • ๐Ÿ›  Fixed the setup script (some subdirs were not included in the release.)


    • ๐Ÿ›  Fixed keyring.core when the user doesn't have a cfg, or is not properly configured.

    • ๐Ÿ›  Fixed escaping issues for usernames with non-ascii characters