feat: Adds note about signing key not working on code commits afterwards, and how to fix.

This commit is contained in:
2025-03-28 11:03:47 -04:00
parent 8406d32f6d
commit 35d5a340bb

View File

@@ -206,6 +206,11 @@ cat /tmp/test.txt.asc
Remove the yubikey and try again, it shouldn't be possible without the yubikey being inserted.
> Note: I was having trouble afterwards on `Gitea` that was saying signatures were suspicious, I had
> to update my git config file to include `signingkey = 14A20BF5!`, which is my signing key, the `!`
> being the important part
> [stack-overflow-link](https://stackoverflow.com/questions/78554135/unverified-github-commits-using-gpg-keys-on-yubikey).
## Setting up macOS to use gpg-agent for ssh
The following lines need added to `~/.gnupg/gpg-agent.conf`, `enable-ssh-support`.
@@ -228,5 +233,3 @@ When setting up I could only use my phone it wouldn't allow me on my computer. O
device to the phone it prompts for a PIN, this is referring to the FIDO PIN that needs setup prior.
This took me a while to figure out and had to factory reset the FIDO application on the yubikey
after too many failed attempts where I used the primary PIN to try and unlock the yubikey.
Test.