tools.linux.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Barker <paul@pbarker.dev>
To: tools@linux.kernel.org,
	Konstantin Ryabitsev <konstantin.ryabitsev@linux.dev>
Cc: Paul Barker <paul@pbarker.dev>
Subject: [b4][PATCH 0/2] Improvements to DKIM signature verification
Date: Mon,  7 Jun 2021 11:02:50 +0100	[thread overview]
Message-ID: <20210607100252.8253-1-paul@pbarker.dev> (raw)

Testing 'b4 am' with patches sent via Office 365 to lists.sr.ht showed
the same issues I found with patatt in handling re-encoded headers. So
there's a patch here to fix this and a patch to improve the ability to
investigate DKIM verification failures with debug output.

NOTE: The attestation key on these patch emails is different to the one
I used on previous patches - I've generated a new key so I've got
separate identities for 'work' and 'personal' hats. You may need to
referesh keys from keys.openpgp.org.

Paul Barker (2):
  Handle MIME encoded-word in DKIM-Signature headers
  Include dkim log output when -d/--debug argument is passed

 b4/__init__.py | 17 ++++++++++++++++-
 1 file changed, 16 insertions(+), 1 deletion(-)

-- 
2.31.1


             reply	other threads:[~2021-06-07 10:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07 10:02 Paul Barker [this message]
2021-06-07 10:02 ` [b4][PATCH 1/2] Handle MIME encoded-word in DKIM-Signature headers Paul Barker
2021-06-07 10:02 ` [b4][PATCH 2/2] Include dkim log output when -d/--debug argument is passed Paul Barker
2021-06-07 12:51 ` [b4][PATCH 0/2] Improvements to DKIM signature verification 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=20210607100252.8253-1-paul@pbarker.dev \
    --to=paul@pbarker.dev \
    --cc=konstantin.ryabitsev@linux.dev \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).