Latest update aggressively takes over ~/.ssh/1Password directory

nigelm

Just updated to 1Password for Mac 8.10.56 (81056028) and found ssh stopped working.

ssh verbose output showed:-

debug1: Will attempt key: /Users/nigel/.ssh/1password/id_ed25519_main.pub  explicit
debug1: Trying private key: /Users/nigel/.ssh/1password/id_ed25519_main.pub
no such identity: /Users/nigel/.ssh/1password/id_ed25519_main.pub: No such file or directory

I had the public keys for my ssh keys stored in ~/.ssh/1password - that directory had now gone, and been replaced by ~/.ssh/1Password (muted boo for MacOS case folding filesystem) which had a autogenerated config file in it

Solution was to edit ~/.ssh/config and update all the IdentityFile declarations with a new path - and create that new path with the ssh pub keys.

However it was not an expected result of an update.

Nigel.

---

1Password Version: 8.10.56
Extension Version: Not Provided
OS Version: MacOS 15.2
Browser: Not Provided

EarthAura

Same here. I was not very happy to run into this. Thankfully recovery was easy since I have Time Machine enabled, otherwise it would've been a pain to re-export all the 20 public keys I currently have exported.

Searching for this new magic config file whose purpose remains a mystery, I found that this change also breaks the following project which I haven't used: https://github.com/Software-Design/1password-ssh-key-importer

The .ssh folder is something I'm very protective of and have a personal organization system, please don't clutter it with your files. Please place them somewhere else, like ~/.config/1Password, they can still be Included from there.

floris_1P

Apologies, this should not have happened. Especially not as an unexpected side effect of an app upgrade. This was supposed to be gated by a feature flag for new functionality that will be released in a few weeks, where 1Password can automatically manage .pub files and IdentityFile configuration for you.

We'll make sure to put it behind an explicit opt-in and avoid unexpected changes like this in the future.

EarthAura

@floris_1P thanks for acknowledging and explaining what went wrong. The new functionality does sound like a welcome change and one I’ve secretly been hoping for for a long time.

I really do hope you give some consideration to storing the keys and configuration under ~/.config/1Password, though. This incident is a good example of why this would be a good idea. I’m a fan of apps that keep themselves contained and don’t spread all across my disk. Cheers!