linux-kernel - Re: [PATCH v2 0/3] w1: gpio: Some cleanup and simplifiction

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 7 Dec 2023 16:58:29 +0100
From:   Uwe Kleine-König <u.kleine-koenig@...gutronix.de>
To:     Krzysztof Kozlowski <krzk@...nel.org>
Cc:     Rob Herring <robh@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
        linux-kernel@...r.kernel.org, kernel@...gutronix.de,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH v2 0/3] w1: gpio: Some cleanup and simplifiction

Hello Krzysztof,

On Thu, Dec 07, 2023 at 03:27:57PM +0100, Krzysztof Kozlowski wrote:
> On 07/12/2023 15:24, Uwe Kleine-König wrote:
> > Hello Krzysztof,
> > 
> > On Thu, Dec 07, 2023 at 02:29:34PM +0100, Krzysztof Kozlowski wrote:
> >> On 04/12/2023 23:05, Uwe Kleine-König wrote:
> >>> Hello,
> >>>
> >>> v1 is available at
> >>> https://lore.kernel.org/r/20230525095624.615350-1-u.kleine-koenig@pengutronix.de.
> >>>
> >>> The changes in this v2 since then are:
> >>>
> >>>  - Fix a build problem in patch #3
> >>>  - Rebase to today's next
> >>
> >>   ✗ No key: openpgp/u.kleine-koenig@...gutronix.de

I think "openpgp" isn't about the keys.openpgp.org keyserver, but just
the signature algorithm.

> >> Are you sure you exported your key to openpgp and verified addresses?
> > 
> > Works for me:
> > 
> > $ gpg --locate-keys u.kleine-koenig@...gutronix.de

FTR: This lookup used WKD, but my key is also on keys.openpgp.org.

> > gpg: directory '/home/test/.gnupg' created
> > gpg: keybox '/home/test/.gnupg/pubring.kbx' created
> > gpg: /home/test/.gnupg/trustdb.gpg: trustdb created
> > gpg: key E2DCDD9132669BD6: public key "Uwe Kleine-König <u.kleine-koenig@...gutronix.de>" imported
> > gpg: Total number processed: 1
> > gpg:               imported: 1
> > gpg: no ultimately trusted keys found
> > pub   rsa4096 2010-06-15 [SC] [expires: 2024-06-21]
> >       0D2511F322BFAB1C1580266BE2DCDD9132669BD6
> > uid           [ unknown] Uwe Kleine-König <u.kleine-koenig@...gutronix.de>
> > sub   rsa2048 2023-03-17 [A] [expires: 2025-03-16]
> > sub   rsa2048 2023-03-17 [S] [expires: 2025-03-16]
> > sub   rsa2048 2023-03-17 [E] [expires: 2025-03-16]
> > 
> > also https://git.kernel.org/pub/scm/docs/kernel/pgpkeys.git seems to
> > have the current key since commit 5151fbdbeb53 "Update E2DCDD9132669BD6
> > (Uwe Kleine-König)".
> 
> Huh, I think I misunderstood the message from b4. I thought it is trying
> to get your key from keys.openpgp.org and your key is just not there.
> Are you saying that it was looking only in my local keyring?

I didn't check how the keyhandling is implemented in b4, but I guess it
just calls gpg and leaves it to you to get my key into your keyring.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | https://www.pengutronix.de/ |

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)