{"id":37216,"date":"2022-10-04T14:59:39","date_gmt":"2022-10-04T18:59:39","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=37216"},"modified":"2022-10-04T14:59:39","modified_gmt":"2022-10-04T18:59:39","slug":"1password-meets-git","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2022\/10\/04\/1password-meets-git\/","title":{"rendered":"1Password Meets Git"},"content":{"rendered":"

Simon Sickle<\/a>:<\/p>\n

\n

Enable the SSH Agent and optionally biometrics if you wish. Now, we must add a snippet of code to our SSH configuration file to tell the SSH command we wish to delegate key management to 1Password.<\/p>\n

[…]<\/p>\n

At work, we have some complex configurations and security rules that wouldn't allow me to store my SSH key in this manor... I do, however, work on some open source software from time to time which requires that I have an SSH key to authenticate with GitHub. To accomplish this, I modified the pasted snippet from 1Password to only use the SSH agent for github connections using the git user.<\/p>\n

[…]<\/p>\n

GitHub now supports code signed by an SSH key! This means you can use 1Password's SSH agent functionality to sign your commits instead of relying on GPG (which has been troublesome in the past on macOS).<\/p>\n<\/blockquote>\n

This is cool, although the feature I really want is to sync 1Password via Git.<\/p>\n

Previously:<\/p>\n