gpg_interface: use the status
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest5 patches 2 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | gpg-interface: check good signature in a reliable waygpg-interface.c | +11 | 2 replies | |
| 2/5 | log-tree: rely upon the check in the gpg_interfacelog-tree.c | +11 | 0 replies | |
| 3/5 | gpg_interface: allow to request status returnbuiltin/ builtin/ gpg-interface.c +3 more | +13 | 0 replies | |
| 4/5 | pretty: parse the gpg status lines rather than the outputpretty.c | +9 | 0 replies | |
| 5/5 | pretty: make %GK output the signing key for signed commitsDocumentation/ pretty.c | +9 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/5] gpg_interface: use the status
Currently, we look at the user facing output of gpg, which is LANG dependent as well as insecure.
After this series, we look at the status output (--status-fd) which is designed for that purpose. As an additional benefit, we can read off the key which was used for the signature, which is important for assigning trust.
All existing tests pass with this.
BTW: git branch --set-upstream-to= coredumps when on a detached head.
Michael J Gruber (5):
gpg-interface: check good signature in a reliable way
log-tree: rely upon the check in the gpg_interface
gpg_interface: allow to request status return
pretty: parse the gpg status lines rather than the output
pretty: make %GK output the signing key for signed commits
Documentation/pretty-formats.txt | 1 + builtin/fmt-merge-msg.c | 2 +- builtin/verify-tag.c | 2 +- gpg-interface.c | 18 +++++++++++++++--- gpg-interface.h | 2 +- log-tree.c | 27 ++++++++++++--------------- pretty.c | 19 +++++++++++++++---- 7 files changed, 46 insertions(+), 25 deletions(-)
Signature · 1 line
1.8.1.3.797.ge0260c7