Mikaela/ssh-allowed_signers
1
0
Fork 0
mirror of https://gitea.blesmrt.net/mikaela/ssh-allowed_signers.git synced 2024-11-22 02:59:28 +01:00
Code Projects Releases Activity

README.md: ramble a quick howto

Browse Source
This commit is contained in:
Aminda Suomalainen 2022-01-09 21:11:30 +02:00
parent 3340137613
commit 28afee650c
Signed by: Mikaela
SSH Key Fingerprint: SHA256:CXLULpqNBdUKB6E6fLA1b/4SzG0HvKD19PbIePU175Q
1 changed files with 22 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
README.md
View File

@ -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