Richard Nixon

I have another customer with this issue...

## Root cause Ruby `Net::SSH::Authentication::Agent` seems to be sending a questionable message when it initialises its connection to the ssh-agent. The message is of type 1 which it describes as...

**Note:** Running OpenSSH client with `strace` reveals that it doesn't bother with the `negotiate` step when connecting to an agent socket. It immediately sends a SSH_AGENTC_REQUEST_IDENTITIES message (11), so it...

My customer has confirmed that disabling `negotiate!` has allowed Inspec to use the keys supplied by Rundeck's JSCH agent. Next step is to figure out who will be responsible for...

Extra info... looks like OpenSSH supports message type 1 (and responds to it), but it's not anything to do with version negotiation. According to https://github.com/openssh/openssh-portable/blob/95eca1e195a3b41baa1a725c2c5af8a09d885e4b/authfd.h#L47 it's actually the old message...

Adding a comment to stop `stale` bot from closing this issue (which is still a problem for my customer)

@sukchomb , sorry this took a while... could you go ahead and test please.

@tas50 , yes,this is still a problem. I just ran into it while investigating another problem for a customer. ``` > chef version Chef Workstation version: 21.11.679 Chef Infra Client...

This would actually be a useful feature when messages are used in conditional skips. They can be confusing because the text may imply a negative, but the text is not...