Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Comments on PGP sign emails sent with git-send-email(1)
Post
The following users marked this post as Works for me:
| User | Comment | Date |
|---|---|---|
| alx | (no comment) | Jun 17, 2022 at 14:33 |
It can't be done with git-send-email(1), but there's a tool that integrates with it, and is very simple to use: patatt(1).
Install the tool:
$ sudo apt-get install patatt
And then for each repo in which you want to sign patches, run:
$ cd /some/git/repo/
$ patatt install-hook
If you have a gpg(1) keyring, and .gitconfig knows about it:
[user]
name = Alejandro Colomar
email = alx.manpages@gmail.com
signingKey = A9348594CE31283A826FBDD8D57633D441E25BB5
Then you're done. Just use git-format-patch(1) and git-send-email(1) as always, and patches will be signed.
To validate a patch before appying it:
$ patatt validate /path/to/incoming.patch
If the patch contains a signature, it will print a human-readable message telling if the signautre is good (and also return 0) or bad (and also return non-zero), according to your keyring and the patch contents. If there's no signature it will print nothing (and return 0).
Then you can git-am(1) as always, with confidence.
See also: https://lore.kernel.org/git/81caab7d-777e-13fe-89ea-820b7b2f0314@gmail.com/T/
Source code: https://git.kernel.org/pub/scm/utils/patatt/patatt.git
0 comment threads