aebrahim / pidgin-gnome-keyring Goto Github PK

35.0 8.0 8.0 40 KB

Save pidgin passwords to the system keyring instead of as plaintext

License: Other

C 76.68% Makefile 5.53% Python 17.79%

pidgin-gnome-keyring's Introduction

pidgin-gnome-keyring

Pidgin usually stores passwords as plaintext. This plugin instead saves all passwords to the system keyring, which some would argue is a more secure form of password storage.

After the plugin is enabled, whenever an account with a pidgin-stored password signs on, its password will automatically be saved to the keyring and removed from the plaintext accounts.xml file.

The plugin is available as a ppa for Ubuntu: ppa:pidgin-gnome-keyring/ppa

Building from source

You will need the libpurple and libsecret development libraries, along with pkg-config. On Ubuntu, install these with sudo apt-get install pkg-config libsecret-1-dev libpurple-dev

Afterwards, use git clone to download the source (the version is set by git), and run make to compile. For installation:

local ($HOME/.purple/plugins): make install_local
global (/usr/lib/purple-2): sudo make install

pidgin-gnome-keyring's People

Contributors

Stargazers

Watchers

Forkers

bluca moebiuseye teotikalki sahwar mailaender edwardbetts top-ranger ejabbered

pidgin-gnome-keyring's Issues

Clarify license

Hi, I'd be interested in packaging this software more "properly" for Debian, e.g. like mozilla-gnome-keyring. This requires clarifying the license. I see that make_package.py mentions gpl2 but could you explicitly state this in a COPYING file, and also clarify if you'd like to make it "GPL-2" or "GPL-2 or later"?

Gnome purple keyring for Pidgin "cannot load collection:"

Hi, I am new to both pidgin and to the Gnome keyring, and so unsure that this is the right place to query about the following:
Running Gnome3 desktop on 4-13.5-1-ARCH (x86_64), I just installed 'pidgin', 'purple-plugin-pack', 'purple-skype-web', 'pidgin-lib-notify'... Also installed Purple Telegram, and 'purple-gnome-keyring 1.1-3' from AUR.
All is well except that, everytime I launch pidgin, I get a small window with the foll0wong message: "Gnome Keyring Plugin could not load collection" with a close button. Can you give me pointers so I can troubleshoot this ? Or is it just me ?
Any pointer will do so I can be on my way. Cheers. -ced

Do not use hardcoded destination directory

Hello,

At the moment, running 'make install' places the plug-in in $DESTDIR/usr/lib/purple-2/. This will not work as expected in a lot of cases, for instance on amd64 machines running RedHat-compatible distros (in which case the plug-in should go into /usr/lib64/purple-2/ - /usr/lib is for 32-bit libraries only). A much better way would be to simply ask libpurple, via pkg-config, where its plug-in directory is:

PLUGINDIR = $(pkg-config --variable=plugindir purple)

...

mkdir -p ${DESTDIR}/${PLUGINDIR}/
cp ${TARGET}.so ${DESTDIR}/${PLUGINDIR}/

PPA builds are failing

Based on https://launchpadlibrarian.net/158290638/pidgin-gnome-keyring_1.22~saucy-1_source.changes and fcec00c I'm guessing that this is now the canonical repository for Pidgin Gnome Keyring?

If so, please note that the PPA is no longer building correctly for most versions of Ubuntu, including Saucy:

https://launchpad.net/~pidgin-gnome-keyring/+archive/ppa/+packages

Add PPA support for Ubuntu 15.10 (wily)

The password do not retrive after reconnect to servers

Hi!
I use pidgin-gnome-keyring v2.0 from debian unstable. I see that its do not retrieve passwords from keyring after reconnect. I just see prompt is password widget. It is common problem for all protocols.

Plugin stops working after some time; Pidgin starts asking for passwords

After working for some time, Pidgin starts asking for passwords on every reconnection, like they were not ever present. I think that happens after Pidgin loses connection for the first time, e.g., when you put the computer into sleep. There are no debug messages related to keyring or passwords when I start pidgin -d. Your plugin is great, but this problem freaks me out. It works fine on another PC, by the way. What should I try to do and what additional info should I give to you?

Of course, I have restarted pidgin and tried again.