Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Forum Discussion
froehr
2 months agoNew Contributor
SSH Agent vault renaming bug
I think I have a found a very strange but reproducible bug using the 1Password SSH Agent.
The trigger for me finding this bug was that i switched the system language of my Mac from English to German. Apparently this also triggers a renaming of the default vault from "Privat" to "Persönlich".
In my opinion this is is also a bit strange but probably understandable from a localization perspective. Maybe some immutable vault-id might make more sense here.
Based on this my config .toml for the SSH Agent did not work anymore. Strangely enough not only my SSH keys in the Private/Persönlich vault stopped working but also my other SSH Key that was stored in a work related vault.
My config.toml looks as follows:
[[ssh-keys]]
item = "Some Key Name"
vault = "Some Vault Name"[[ssh-keys]]
vault = "Private" # This was changed to "Persönlich"
While I was figuring out why I couldn't connect to git anymore I tried using
SSH_AUTH_SOCK=~/Library/Group\ Containers/2BUA8C4S2C.com.1password/t/agent.sock ssh-add -l
to check which SSH Keys were loaded into the agent. This showed the "Some Key Name" Key being present. Still using it did not work. Only after fixing this Private/Persönlich vault config also the other vault config worked again.
Can anybody reproduce this?
2 Replies
- 1P_Phil
Moderator
Hi froehr ,
I have reported this as a bug to be looked into. Thanks for reporting this. If you find yourself going between languages, in the short term, please consider using Vault ID's (instead of the human readable version).
You can see the Vault ID by turning on the Developer Experience in the UI and then right-clicking on a Vault to copy the Vault ID.
Let me know if you have any further questions.
Regards,
Phil