From 28afee650c6a2e945861030e47882b08a83dbe15 Mon Sep 17 00:00:00 2001 From: Aminda Suomalainen Date: Sun, 9 Jan 2022 21:11:30 +0200 Subject: [PATCH] README.md: ramble a quick howto --- README.md | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/README.md b/README.md index 7a7e490..93f036c 100644 --- a/README.md +++ b/README.md @@ -10,6 +10,28 @@ which does about the same for PGP. * GitHub, Giteas and GitLabs expose user public keys when you append a .keys after their profile page * Good ideas are made to be copied, so maybe there will be more repositories like this ;) +## Quick howto + +I don't mean this to be used directly, only to be took inspiration from. See the first +link in further reading. + +```bash +mkdir -p ~/src/gitea.blesmrt.net/Mikaela +cd ~/src/gitea.blesmrt.net/Mikaela +git clone https://gitea.blesmrt.net/Mikaela/ssh-allowed_signers.git +git config --global gpg.ssh.allowedSignersFile ~/src/gitea.blesmrt.net/Mikaela/ssh-allowed_signers/allowed_signers +``` + +Git commands should now recognised commits signed with keys I have allowed. +In the last command it's fine to remove `--global` to only affect the single +repository you are on (while I haven't tested this), should that repository +be something only I am signing in or something I need to verify otherwise +enough to list it here. + +On the last command, `git config` turns it into absolute path, while manually +edited `.gitconfig` can literally have the above. I wonder if the command +would understand `--` before the file, but not enough to actually try it :smiley: + ## Further reading * [Caleb Hearth: Signing Git Commits with Your SSH Key](https://calebhearth.com/sign-git-with-ssh), [web.archive.org](https://web.archive.org/web/20211117182628/https://calebhearth.com/sign-git-with-ssh), inspired me to try this