On Wed, Apr 27, 2011 at 13:53, jh <email address hidden> wrote:
> Don't think it's that simple. The new agent is overriding the gnome
> authentication agent, and you've now lost any keys that were
> automagically loaded from the gnome keyring.
>
> Ah, now I understand:
So, maybe it means that polkit isn't capable of handling ECDSA keys, and it
makes sense because when using seahorse to show the key properties, my ECDSA
key is recognized as a 320 bit DSA key (see attachment).
On Wed, Apr 27, 2011 at 13:53, jh <email address hidden> wrote:
> Don't think it's that simple. The new agent is overriding the gnome
> authentication agent, and you've now lost any keys that were
> automagically loaded from the gnome keyring.
>
> Ah, now I understand:
claudio@Chuck:~$ echo $SSH_AUTH_SOCK ZK6XAP/ ssh SOCK=/tmp/ ssh-iRQvNKEv222 5/agent. 2225; export SSH_AUTH_SOCK;
/tmp/keyring-
claudio@Chuck:~$ echo $SSH_AGENT_PID
1640
claudio@Chuck:~$ ssh-agent
SSH_AUTH_
SSH_AGENT_PID=2226; export SSH_AGENT_PID;
echo Agent pid 2226;
So, maybe it means that polkit isn't capable of handling ECDSA keys, and it
makes sense because when using seahorse to show the key properties, my ECDSA
key is recognized as a 320 bit DSA key (see attachment).