Git and Azure DevOPS: agent refused operation

Yes, this is because Azure DevOps only supports legacy ssh-rsa SHA-1 signatures. We're working on adding support for those as well.

Hi,

I think i've created a ssh-rsa key for azure devops now, however i'm getting the same error. Is this issue fixed yet?

AFAIK there is no support for Azure DevOPS (or the other way around: Azure DevOPS doesn't support the better algorithms) yet. My workaround: I added the following to my .ssh/config file:

Host ssh.dev.azure.com
IdentityFile ~/.ssh/id_rsa
IdentitiesOnly yes
IdentityAgent /private/tmp/com.apple.launchd.znyst9AFDG/Listeners

Anyone know what the workaround would be on Linux?
I have the identity file in ~/.ssh, but it seems no matter what I do, the 1password SSH agent is taking over.

SSH_AUTH_SOCK="" git fetch
sign_and_send_pubkey: signing failed for RSA "/home/user/.ssh/id_rsa" from agent: agent refused operation

I figured out I can just define this ssh config above the Host * IdentityAgent in ~/.ssh/config to workaround

Glad you found a solution, @zigford. And thanks for sharing it!

Update. Don't know why, but my workaround stopped working.
New workaround that is working currently:

Define the following above the IdentityAgent definition, so the ~/.ssh/config should look like this:

Host ssh.dev.azure.com
HostName ssh.dev.azure.com
User git
IdentityFile ~/.ssh/id_rsa
PubkeyAcceptedAlgorithms +ssh-rsa
HostkeyAlgorithms +ssh-rsa
IdentitiesOnly yes
IdentityAgent /dev/null
Host *
IdentityAgent ~/.1password/agent.sock
AddKeysToAgent yes


Hi @zigford!

As of the latest nightly release, 1Password supports ssh-rsa (SHA-1). So if you update to the latest nightly you can also store your Azure DevOPS SSH key in 1Password.

Excellent news. Thank you!

Thanks @MartonS1P, can you point me in the direction of the nightly releases? I've googled around and cannot find it. I'm on Linux.