SSH keys and MacOs Tahoe 26.3

gitssh

After updating to newest Tahoe I got this messages while connecting to Bitbucket. The message looked like this:

* WARNING: connection is not using a post-quantum key exchange algorithm.
** This session may be vulnerable to "store now, decrypt later" attacks.
** The server may need to be upgraded. See https://openssh.com/pq.html

At first I thought, I need to make new SSH key; Updating sometimes is good practice. However this message was purely created because MacOs has a newer ssh thingy. https://apple.stackexchange.com/questions/485851/how-to-deal-with-a-warning-connection-is-not-using-a-post-quantum-key-exchange

So now I ignore it untill Bitbucket will update their server side ssh stuff and it will probably go away.

However I did update my SSH key... And then this message came while I tried committing:

git commit -m "test"
error: 1Password: No SSH private key found for the specified public key:
ssh-ed25519 xxxxx/xxxxxx

Make sure the SSH key is saved in your Personal or Private vault (default)
or added to your SSH agent config file (custom).

See https://developer.1password.com/docs/ssh/agent/config/ for more information.

And I was like whut? But apparently I have setup that key as 'git commit signing'. And I removed that 'older' key...

So I followed steps explained https://developer.1password.com/docs/ssh/git-commit-signing/#configure-commit-signing-in-a-single-repository

And I now understand it a bit more...