4 ms·

Git commits can be signed with SSH keys now: https://twitter.com/damienmiller/status/1531502392457723905 https://twitter.com/damienmiller/status/15315023924577

Git commits can be signed with SSH keys now: https://twitter.com/damienmiller/status/1531502392457723905 https://twitter.com/damienmiller/status/1531502392457723905 (thread)

nikolay 4y ago
Unfortunately, this doesn't work with 1Pasword for SSH.
- fstelzer 4y ago
  Afaik 1Password simply provides an ssh-agent. So I don‘t see why this should not work. If you set gits user.signingKey to your public key and have SSH_AUTH_SOCk point to 1password agent this should work. Do you have any details on why not?
  - deleted 4y ago
    [deleted]
- halostatue 4y ago
  Fortunately, it does work with 1Password for SSH. Good "git" signature for [REDACTED] with ED25519 key SHA256:VqH020xxJ+XyDLBh99HuBjkdXye4xakUqE05dyDnZC8 fac93bd4295e 2022-06-08 | Some further updates (HEAD -> main) [Austin Ziegler]
  - nikolay 4y ago
    Thank you!
  - deleted 4y ago
    [deleted]
  - nikolay 4y ago
    I can't make it work as it complains about the format of the signing key. Can you please share your setup? Thanks!
    - halostatue 4y ago
      Sorry, I had missed this. The format is [gpg] format = ssh [user] signingKey = key::SSH-PUBKEY In my case, since I have an ssh-ed25519 key, it is [user] signingKey = key::ssh-ed25519 AAAAC… You can pretty much copy the `.pub` key and paste it after `key::` (instructions like the ones at https://calebhearth.com/sign-git-with-ssh https://calebhearth.com/sign-git-with-ssh will show this without the `key::` prefix; according to the latest git documentation, the non-prefixed SSH key format is not preferred, as the `signingKey` value can be either a raw SSH public key, a GPG key ID, or a path to the signing key). One thing of note that I haven’t checked to see if it matters. I have the matching `.pub` key in `~/.ssh`, but I don’t think that is making a difference. I do remember having some struggles getting it sorted out at the very beginning, but I didn’t take very good notes of what different things I tried.

Git commits can be signed with SSH keys now: https://twitter.com/damienmiller/status/1531502392457723905 https://twitter.com/damienmiller/status/1531502392457723905 (thread)

nikolay 4y ago

Unfortunately, this doesn't work with 1Pasword for SSH.

fstelzer 4y ago
Afaik 1Password simply provides an ssh-agent. So I don‘t see why this should not work. If you set gits user.signingKey to your public key and have SSH_AUTH_SOCk point to 1password agent this should work. Do you have any details on why not?
- deleted 4y ago
  [deleted]
halostatue 4y ago
Fortunately, it does work with 1Password for SSH. Good "git" signature for [REDACTED] with ED25519 key SHA256:VqH020xxJ+XyDLBh99HuBjkdXye4xakUqE05dyDnZC8 fac93bd4295e 2022-06-08 | Some further updates (HEAD -> main) [Austin Ziegler]
- nikolay 4y ago
  Thank you!
- deleted 4y ago
  [deleted]
- nikolay 4y ago
  I can't make it work as it complains about the format of the signing key. Can you please share your setup? Thanks!
  - halostatue 4y ago
    Sorry, I had missed this. The format is [gpg] format = ssh [user] signingKey = key::SSH-PUBKEY In my case, since I have an ssh-ed25519 key, it is [user] signingKey = key::ssh-ed25519 AAAAC… You can pretty much copy the `.pub` key and paste it after `key::` (instructions like the ones at https://calebhearth.com/sign-git-with-ssh https://calebhearth.com/sign-git-with-ssh will show this without the `key::` prefix; according to the latest git documentation, the non-prefixed SSH key format is not preferred, as the `signingKey` value can be either a raw SSH public key, a GPG key ID, or a path to the signing key). One thing of note that I haven’t checked to see if it matters. I have the matching `.pub` key in `~/.ssh`, but I don’t think that is making a difference. I do remember having some struggles getting it sorted out at the very beginning, but I didn’t take very good notes of what different things I tried.