Forum Discussion

lczerepuk's avatar
lczerepuk
New Contributor
1 month ago

SSH Agent does not respect ssh-keys order

Hey!

After latest Production 1Password update (1Password for Mac 8.12.0 (81200013)) something is off with SSH Agent.

SSH agent does not respect ssh-keys order set in TOML file anymore. It doesn't matter if you set any keys in TOML file or you leave this file empty, command ssh-agent -l prints ssh-keys in random order.

Example, my TOML file:

[[ssh-keys]]
item = "SSH Private Key"
vault = "Personal"
[[ssh-keys]]
item = "Magento Cloud GDPR"
vault = "Employee"
[[ssh-keys]]
item = "AWS EKS Node"
vault = "Employee"
[[ssh-keys]]
item = "AWS Key"
vault = "DevOps"


And two results of ssh-add -l command:

SSH_AUTH_SOCK=~/Library/Group\ Containers/2BUA8C4S2C.com.1password/t/agent.sock ssh-add -l
4096 SHA256:N4XGsjxtiMBWRpHvwh16fTciJL1aaTc0wuGXMlePQuY Magento Cloud GDPR (RSA)
4096 SHA256:2LqQtMd7YdPMGXg4W+zODedaHi1oz4CxC0k/hl0V+PQ AWS EKS Node (RSA)
2048 SHA256:4uE+nbs+twoNih01hiveiXFjy3bIh+NPkVyBNyqRyYg AWS Key (RSA)
256 SHA256:QKMLArxXXvAcYzmSCqV766DsOAyxnkuA28TwneIsvTI SSH Private Key (ED25519)

SSH_AUTH_SOCK=~/Library/Group\ Containers/2BUA8C4S2C.com.1password/t/agent.sock ssh-add -l
256 SHA256:QKMLArxXXvAcYzmSCqV766DsOAyxnkuA28TwneIsvTI SSH Private Key (ED25519)
4096 SHA256:N4XGsjxtiMBWRpHvwh16fTciJL1aaTc0wuGXMlePQuY Magento Cloud GDPR (RSA)
4096 SHA256:2LqQtMd7YdPMGXg4W+zODedaHi1oz4CxC0k/hl0V+PQ AWS EKS Node (RSA)
2048 SHA256:4uE+nbs+twoNih01hiveiXFjy3bIh+NPkVyBNyqRyYg AWS Key (RSA)



3 Replies

  • lczerepuk's avatar
    lczerepuk
    New Contributor

    I can confirm that in version: 1Password for Mac 8.12.2 (81202037) it works fine now. :) 

  • lczerepuk's avatar
    lczerepuk
    New Contributor

    I have update from 1P Support:

    Thank you very much for checking in. Our developers have been working hard to ensure everything functions as expected without introducing any additional issues. I’m happy to share that a fix is now available in the latest 1Password beta, version 8.12.2.

  • wa's avatar
    wa
    New Contributor

    We have the same problem: Since the last update the order of the toml file is no longer used. Therefore we are experiencing issues authenticating using git.

    Currently, we are not specifying keys directly in the toml file. We just specify the vaults in a specific order.