From: Kees Cook <keescook@chromium.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Kees Cook <keescook@chromium.org>, tools@linux.kernel.org
Subject: [PATCH] gnupg: Add gpg status output to debug logging
Date: Thu, 7 Oct 2021 09:58:01 -0700 [thread overview]
Message-ID: <20211007165801.2313136-1-keescook@chromium.org> (raw)
There wasn't an easy way to see how a failure was being determined by
GPG, so add the entire GPG status output to the debug log.
Signed-off-by: Kees Cook <keescook@chromium.org>
---
patatt/__init__.py | 1 +
1 file changed, 1 insertion(+)
diff --git a/patatt/__init__.py b/patatt/__init__.py
index 2e33bce209e2..6f4591973751 100644
--- a/patatt/__init__.py
+++ b/patatt/__init__.py
@@ -371,6 +371,7 @@ class DevsigHeader:
signtime = ''
signkey = ''
+ logger.debug('GNUPG status:\n\t%s' % ("\n\t".join(status.decode().strip().split('\n'))))
gs_matches = re.search(rb'^\[GNUPG:] GOODSIG ([0-9A-F]+)\s+(.*)$', status, flags=re.M)
if gs_matches:
good = True
--
2.30.2
next reply other threads:[~2021-10-07 16:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 16:58 Kees Cook [this message]
2021-10-07 18:10 ` [PATCH] gnupg: Add gpg status output to debug logging Konstantin Ryabitsev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211007165801.2313136-1-keescook@chromium.org \
--to=keescook@chromium.org \
--cc=konstantin@linuxfoundation.org \
--cc=tools@linux.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.