Hello,
(please CC me as i am subscribed)
I have upgraded to 0.34 and read the NEWS' pragraph about ssh-agent
integration. I though i wouldn't notice it because i'm using a hook with
my passphrases hardcoded in it.
Then i commit something and the gnome-keyring dialog pops asking for a
password for my main ssh key "address@hidden". I click cancel. The commit
succeeds.
Gnome-keyring shows a unknow cached key (see the attached screenshot)
"Unknown Key: 94327E4BE814F08E"
ssh-add -l shows it
1024 e0:47:b5:c8:e6:c7:80:b2:df:da:81:b6:68:9a:20:e1 address@hidden
(RSA)
This doesn't match what gnome-keyring shows. (Maybe gnome-keyring is
wrong).
- Why is it using ssh-agent if it doesn't really need to ? I mean it
used to work without by using the hook. On windows where i don't run any
ssh-agent, it works as it used to be.
- Who is asking for unlocking my main real ssh key ?
- Do i have control over the ssh key monotone is using ?
- Is it always the same key ? Is it random or computed from my monotone
key ?
- Can i create a SSH key for monotone only so i would be able to
statically import it in my keyring ? Can i associate my monotone key
with my main SSH key ?
- How can i see the link between SSH keys and monotone keys ?
- Why about using SSH keys for monotone and dropping its custom key
format ?