[08:43] <sakrecoer> zequence: excellent! i havn't been able to test the new release for logisitc reasons, and os i was a bit worried that scribus bug would have slipped in :)
[10:52] <sakrecoer> do you guys also have problems with gnome keyagent for ssh? i'm going crazy over it. over at #gnome, they find my problem intersting but have no sollution...
[10:53] <sakrecoer> i've deleted all my keys from the system, yet gnomekeyring finds it somewhere, stating it is in ~./ssh (where it is not) seahorse see no SSH keys, but my gpg keys are there... yet i can connect to my servers using the deleted keys (yes i have rebooted severeal times)
[10:54] <sakrecoer> sudo find / -iname '*rsa*' gives no return...
[10:56] <sakrecoer> btw, seahorse is not showing up in our menu...
[10:56] <sakrecoer> after install..
[11:08] <sakrecoer> ok... so gnome keyring is storing a copy of the secret ssh key in ~/.gnupg/private-keys-v1.d/
[11:09] <sakrecoer> but it seems to get coded as to claim that it is located in ~/.ssh/rsa_id
[12:30] <sakrecoer> ok... so it is gpg-agent that is sotring the key. seems we have 3 different agents: ssh-agent, gpg-agent, and  gnome-keyring-daemon
[17:37] <zequence> sakrecoer: I never bothered getting that to work. You might want to ask in #xubuntu how to get ssh paswords stored
[17:40] <sakrecoer> i asked all over freenode today, but i got an answer. its gpg-agent and it is stored in both ~/.gnupg/sshcontrol and in ~/.gnupg/private-keys-v1.d/<keygrip>.key
[17:41] <sakrecoer> i'm sure there is a good reason to have 3 different ssh agents... its just very confusing. When you add a key sith ssh-add, it gets copied by gpg-agent and encrypted behind a 2nd password...
[17:43] <sakrecoer> anyways, now that i understand howit works, i'm happy enough to let it go... :D
[21:43] <OvenWerks> sakrecoer: I don't use the keyring thing. I found it was asking me for a password in too many places it didn't need to.