> On May 22, 2020, at 11:45 AM, Stuart Henderson <[email protected]> wrote: > > Ahh I just realised that you might be wanting to use agent-forwarded > keys to connect to bitbucket. What I described should work if you have > local keys on the server where you run the git commands but it's not > using them because it's using a key from the agent that you don't > want it to use - but if you're trying to use one of several agent > keys then I'm not sure if it will be possible.
Also, I noticed something which I think is working as intended, but seems odd. When I ssh to the intermediate server, I can do an ssh-add on there to load up a key that is only on the intermediate server. That key then is held in the ssh-agent on my workstation. After I disconnect from the intermediate server, the ssh-agent on my workstation retains the key and can use it for authentication to other hosts. I get why this happens, but it seems a little paradoxical. There also doesn’t seem to be a way to delete the key from the ssh-agent on the workstation after I disconnect (other than using ssh-add -D to blow away all of the keys.) —Paul
smime.p7s
Description: S/MIME cryptographic signature
