pidgin-gnome-keyring
pidgin-gnome-keyring copied to clipboard
aebrahim
Plugin cannot store new passwords in given keyring
It seems pidgin-gnome-keyring does not support creating new keyring, even though there is an option in the configuration window for this.
I've tried to make this plugin use a keyring called "pidgin", and it still uses the previously created keyring.
Of course, I have restarted pidgin and tried again.
If you create a new keyring separately, then does that work?
On Sun, Sep 13, 2015 at 6:29 PM, moebiuseye [email protected] wrote:
It seems pidgin-gnome-keyring does not support creating new keyring, even though there is an option in the configuration windows for this.
— Reply to this email directly or view it on GitHub https://github.com/aebrahim/pidgin-gnome-keyring/issues/7.
No, it doesn't.
I'll create a new user and come up with non-sensitive data to share.
I'm forking this project, creating a dev branch, and testing a few changes.
I hope I can come up with a fix. Until then: testing time.
thanks :)
BTW I may not merge a pull request because i have a major refactor in the works (want to share a lot of code with pidgin-wincred, and also make it super easy to write a similar one for kde), but finding the source of the bug would be super helpful to getting it fixed.
also, what os are you using? and are you using gnome or unity?
On Sun, Sep 13, 2015 at 6:46 PM, moebiuseye [email protected] wrote:
No, it doesn't.
I'll create a new user and come up with non-sensitive data to share.
I'm forking this project, creating a dev branch, and testing a few changes.
I hope I can come up with a fix. Until then: testing time.
— Reply to this email directly or view it on GitHub https://github.com/aebrahim/pidgin-gnome-keyring/issues/7#issuecomment-139893773 .
I can confirm this bug. I am using i3wm on arch linux without gnome and unity etc. The plain key does neither appear in the account.xml nor in the gnome keyring. Any suggestions?
I too am using archlinux with i3wm. I've attempted to patch by using the secret_collection_create function, to no avail.
I'll try something else this weekend.
The issue seems to be lying here:
(19:31:25) g_log: Remote error from secret service: org.freedesktop.Secret.Error.NoSuchObject: The '/org/freedesktop/secrets/aliases/debugkeyringname' object does not exist
store_finish error in store_cb: The '/org/freedesktop/secrets/aliases/debugkeyringname' object does not exist
Does that happen even if you create it ahead of time? On Sep 17, 2015 20:02, "moebiuseye" [email protected] wrote:
The issue seems to be lying here:
(19:31:25) g_log: Remote error from secret service: org.freedesktop.Secret.Error.NoSuchObject: The '/org/freedesktop/secrets/aliases/debugkeyringname' object does not exist store_finish error in store_cb: The '/org/freedesktop/secrets/aliases/debugkeyringname' object does not exist
— Reply to this email directly or view it on GitHub https://github.com/aebrahim/pidgin-gnome-keyring/issues/7#issuecomment-141167994 .
Ok.
An I correct in classifying this as a documentation issue? That the keyring must already exist? On Sep 17, 2015 21:23, "moebiuseye" [email protected] wrote:
No, it doesn't.
— Reply to this email directly or view it on GitHub https://github.com/aebrahim/pidgin-gnome-keyring/issues/7#issuecomment-141195012 .
In addition to that, the plugin prompts for opening every collection. (aka password keyring)
I think the secret_password_lookup_sync function call is responsible for this.
Responsible for what exactly?
The prompt to unlock the keyring? That needs to happen to read out of it because it's encrypted. On Sep 17, 2015 23:18, "moebiuseye" [email protected] wrote:
I think the secret_password_lookup_sync function call is responsible for this.
— Reply to this email directly or view it on GitHub https://github.com/aebrahim/pidgin-gnome-keyring/issues/7#issuecomment-141230706 .
This function unlocks all the keyrings. The expected behavior is to unlock only the user-defined (or default) keyring.