Linux maintainer tooling and workflows
 help / color / mirror / Atom feed
* Most of my "b4 am" runs fail the DKIM test
@ 2023-08-02 13:53 Chuck Lever
  2023-08-02 14:11 ` Konstantin Ryabitsev
  0 siblings, 1 reply; 5+ messages in thread
From: Chuck Lever @ 2023-08-02 13:53 UTC (permalink / raw)
  To: users, tools

I recently started seeing this quite a bit:

  ✗ [PATCH v4 1/2] SUNRPC: add verbose parameter to __svc_print_addr()
  ✗ [PATCH v4 2/2] NFSD: add rpc_status entry in nfsd debug filesystem
  ---
  ✗ BADSIG: DKIM/kernel.org

In fact, even my own patches (sent via the kernel.org SMTP relay) fail
this check.

What am I doing wrong?


-- 
"We cannot take our next breath without the exhale."
 -- Ellen Scott Grable

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Most of my "b4 am" runs fail the DKIM test
  2023-08-02 13:53 Most of my "b4 am" runs fail the DKIM test Chuck Lever
@ 2023-08-02 14:11 ` Konstantin Ryabitsev
  2023-08-02 14:57   ` Chuck Lever
  0 siblings, 1 reply; 5+ messages in thread
From: Konstantin Ryabitsev @ 2023-08-02 14:11 UTC (permalink / raw)
  To: Chuck Lever; +Cc: users, tools

On Wed, Aug 02, 2023 at 09:53:10AM -0400, Chuck Lever wrote:
> I recently started seeing this quite a bit:
> 
>   ✗ [PATCH v4 1/2] SUNRPC: add verbose parameter to __svc_print_addr()
>   ✗ [PATCH v4 2/2] NFSD: add rpc_status entry in nfsd debug filesystem
>   ---
>   ✗ BADSIG: DKIM/kernel.org
> 
> In fact, even my own patches (sent via the kernel.org SMTP relay) fail
> this check.
> 
> What am I doing wrong?

It's really hard to troubleshoot, but you can try the following:

    $ curl -s https://lore.kernel.org/linux-nfs/5b0eff4e3ef9bf9621f5095189933f60def40f0d.1690569488.git.lorenzo@kernel.org/raw | dkimverify
    signature ok

If you don't get "signature ok", then my guess would be that there's some
problem performing DNS lookups for public keys.

-K

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Most of my "b4 am" runs fail the DKIM test
  2023-08-02 14:11 ` Konstantin Ryabitsev
@ 2023-08-02 14:57   ` Chuck Lever
  2023-08-02 15:54     ` Konstantin Ryabitsev
  0 siblings, 1 reply; 5+ messages in thread
From: Chuck Lever @ 2023-08-02 14:57 UTC (permalink / raw)
  To: Konstantin Ryabitsev; +Cc: users, tools

On Wed, Aug 2, 2023 at 10:11 AM Konstantin Ryabitsev
<konstantin@linuxfoundation.org> wrote:
>
> On Wed, Aug 02, 2023 at 09:53:10AM -0400, Chuck Lever wrote:
> > I recently started seeing this quite a bit:
> >
> >   ✗ [PATCH v4 1/2] SUNRPC: add verbose parameter to __svc_print_addr()
> >   ✗ [PATCH v4 2/2] NFSD: add rpc_status entry in nfsd debug filesystem
> >   ---
> >   ✗ BADSIG: DKIM/kernel.org
> >
> > In fact, even my own patches (sent via the kernel.org SMTP relay) fail
> > this check.
> >
> > What am I doing wrong?
>
> It's really hard to troubleshoot, but you can try the following:
>
>     $ curl -s https://lore.kernel.org/linux-nfs/5b0eff4e3ef9bf9621f5095189933f60def40f0d.1690569488.git.lorenzo@kernel.org/raw | dkimverify
>     signature ok
>
> If you don't get "signature ok", then my guess would be that there's some
> problem performing DNS lookups for public keys.

curl -s https://lore.kernel.org/linux-nfs/5b0eff4e3ef9bf9621f5095189933f60def40f0d.1690569488.git.lorenzo@kernel.org/raw
| dkimverify
signature verification failed

A DNS issue makes some sense; I've made some DNS/firewall changes here recently.


-- 
"We cannot take our next breath without the exhale."
 -- Ellen Scott Grable

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Most of my "b4 am" runs fail the DKIM test
  2023-08-02 14:57   ` Chuck Lever
@ 2023-08-02 15:54     ` Konstantin Ryabitsev
  2023-08-02 18:46       ` Chuck Lever
  0 siblings, 1 reply; 5+ messages in thread
From: Konstantin Ryabitsev @ 2023-08-02 15:54 UTC (permalink / raw)
  To: Chuck Lever; +Cc: users, tools

On Wed, Aug 02, 2023 at 10:57:35AM -0400, Chuck Lever wrote:
> curl -s https://lore.kernel.org/linux-nfs/5b0eff4e3ef9bf9621f5095189933f60def40f0d.1690569488.git.lorenzo@kernel.org/raw
> | dkimverify
> signature verification failed
> 
> A DNS issue makes some sense; I've made some DNS/firewall changes here recently.

The following should succeed for you for DKIM to work:

    dig -t txt k20201202._domainkey.kernel.org

-K

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Most of my "b4 am" runs fail the DKIM test
  2023-08-02 15:54     ` Konstantin Ryabitsev
@ 2023-08-02 18:46       ` Chuck Lever
  0 siblings, 0 replies; 5+ messages in thread
From: Chuck Lever @ 2023-08-02 18:46 UTC (permalink / raw)
  To: Konstantin Ryabitsev; +Cc: users, tools

On Wed, Aug 2, 2023 at 11:54 AM Konstantin Ryabitsev
<konstantin@linuxfoundation.org> wrote:
>
> On Wed, Aug 02, 2023 at 10:57:35AM -0400, Chuck Lever wrote:
> > curl -s https://lore.kernel.org/linux-nfs/5b0eff4e3ef9bf9621f5095189933f60def40f0d.1690569488.git.lorenzo@kernel.org/raw
> > | dkimverify
> > signature verification failed
> >
> > A DNS issue makes some sense; I've made some DNS/firewall changes here recently.
>
> The following should succeed for you for DKIM to work:
>
>     dig -t txt k20201202._domainkey.kernel.org

My DNS server is on a different system than the firewall. The firewall
assumed that by default, the DNS service will be provided on the
firewall/gateway system.

I added a firewall rule to pass DNS requests from any host on my LAN.
That enabled the "dig" and the "dkimverify" commands to succeed.


-- 
"We cannot take our next breath without the exhale."
 -- Ellen Scott Grable

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2023-08-02 18:46 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-08-02 13:53 Most of my "b4 am" runs fail the DKIM test Chuck Lever
2023-08-02 14:11 ` Konstantin Ryabitsev
2023-08-02 14:57   ` Chuck Lever
2023-08-02 15:54     ` Konstantin Ryabitsev
2023-08-02 18:46       ` Chuck Lever

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox