Skip to content

Instantly share code, notes, and snippets.

@paulmillr

paulmillr/guide.md

Last active November 4, 2023 15:22
Show Gist options
  • Save paulmillr/2be0416b4bc3b6d98b885122dbe967f9 to your computer and use it in GitHub Desktop.
Save paulmillr/2be0416b4bc3b6d98b885122dbe967f9 to your computer and use it in GitHub Desktop.
Download ZIP

Revisions

  1. paulmillr revised this gist May 30, 2022. 1 changed file with 3 additions and 1 deletion.
    4 changes: 3 additions & 1 deletion guide.md
    View file
    Original file line number Diff line number Diff line change
    @@ -18,4 +18,6 @@ git config --global user.signingkey 'ssh-ed25519 AAAAC3N...'
    echo '[email protected] valid-after="20220501",valid-before="20220601" ssh-ed25519 AAAAC3N...' > ~/.ssh/allowed_signers
    eval "$(ssh-agent -s)"
    ```
    ```

    - You need to have `~/.ssh/allowed_signers` file with **all keys**, otherwise, the `git log` will fail, which is a huge UX mess
  2. paulmillr created this gist May 30, 2022.
    21 changes: 21 additions & 0 deletions guide.md
    View file
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,21 @@
    # Sign git commits with ssh key

    - git version must be >= 2.34. Earlier versions don't support `gpg.format ssh` (signing commits with ssh keys).

    If you're printing signature keys in git log by using `%GK %GF %GP %GT` in `git.format.pretty`,
    earlier versions will **crash** when doing `git log` with following error:

    `BUG: gpg-interface.c:284: bad signature`

    - OpenSSH version must be >= 8.8. Earlier versions don't support `valid-after,valid-before` options.

    The setup is as following:

    ```
    git config --global gpg.format ssh
    git config --global gpg.ssh.allowedSignersFile ~/.ssh/allowed_signers
    git config --global user.signingkey 'ssh-ed25519 AAAAC3N...'
    echo '[email protected] valid-after="20220501",valid-before="20220601" ssh-ed25519 AAAAC3N...' > ~/.ssh/allowed_signers
    eval "$(ssh-agent -s)"
    ```