Version 4 (modified by 11 years ago) (diff) | ,
---|
Keyrings cryptographically secure your password in a way that would generally be more secure (although not perfect). It would require a master password, shared amongst all the applications on your computer, to get at your passwords.
Pidgin does not currently support storing passwords in keyrings; currently you must either store passwords unencrypted or not at all.
Status
This is being actively worked on by Tomasz Wasilczyk in the soc.2008.masterpassword branch of https://hg.pidgin.im/cpw/tomkiewicz/masterpassword The code has not been merged into the main development tree yet.
This code initially came from a Google Summer of Code project in 2008.
The GSoC branch (im.pidgin.soc.2008.masterpassword
) has implementations for Freedesktop and KWallet.
See also
- wiki:PlainTextPasswords
- The feature request is ticket #673
- Launchpad bug
Specific keyrings
GNOME Keyring and KDE KSecretsService
Status: implemented but not integrated
These are the GNOME and KDE implementations of the Freedesktop Secret Service API, intended to provide a standard interface for Linux apps to store passwords and stuff.
Pidgin would need to connect to the DBus API to store and retrieve passwords. There are several libraries to do this, including libsecret and python-keyring.
KDE KWallet
Status: implemented but not integrated
Currently uses its own API, but there has been discussion about replacing it with KSecretsService using the standard API.
KeePass
Cross-platform, open-source password manager.
Integrating with Pidgin would involve either writing a KeePass plug-in, or using one of the existing plugins that facilitate communicating with other apps. See for example KeeFox (KeePass–Firefox bridge), which includes the KeePassRPC plugin.