linux-kernel - Re: [GIT PULL] first round of SCSI updates for the 6.7+ merge window

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20240112-steadfast-eager-porcupine-2c9b3a@lemur>
Date: Fri, 12 Jan 2024 09:27:27 -0500
From: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: James Bottomley <James.Bottomley@...senpartnership.com>, 
	Andrew Morton <akpm@...ux-foundation.org>, linux-scsi <linux-scsi@...r.kernel.org>, 
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] first round of SCSI updates for the 6.7+ merge window

On Thu, Jan 11, 2024 at 03:50:32PM -0800, Linus Torvalds wrote:
> > jejb@...grow:~> gpg --list-key E76040DB76CA3D176708F9AAE742C94CEE98AC85
> > pub   rsa2048 2011-09-23 [SC] [expires: 2026-03-11]
> >       D5606E73C8B46271BEAD9ADF814AE47C214854D6
> > uid           [ultimate] James Bottomley
> > <James.Bottomley@...senPartnership.com>
> > uid           [ultimate] James Bottomley <jejb@...ux.vnet.ibm.com>
> > uid           [ultimate] James Bottomley <jejb@...nel.org>
> > uid           [ultimate] [jpeg image of size 5254]
> > uid           [ultimate] James Bottomley <jejb@...ux.ibm.com>
> > uid           [ultimate] James Bottomley <jejb@...senpartnership.com>
> > sub   nistp256 2018-01-23 [S] [expires: 2024-01-16]
> > sub   nistp256 2018-01-23 [E] [expires: 2024-01-16]
> > sub   nistp256 2023-07-20 [A] [expires: 2024-01-16]
> 
> Look closer.
> 
> NOWHERE there does it mention E76040D.. Nowhere.

I'm piping up just because I know how to get the output you want, not because
I hold any opinions on GnuPG (I do, but they aren't relevant here). :)

Add the following to your ~/.gnupg/gpg.conf:

    keyid-format long

After that the output should look like this:

    $ gpg --list-key E76040DB76CA3D176708F9AAE742C94CEE98AC85
    pub   rsa2048/814AE47C214854D6 2011-09-23 [SC] [expires: 2026-03-11]
          D5606E73C8B46271BEAD9ADF814AE47C214854D6
    uid                 [  full  ] James Bottomley <James.Bottomley@...senPartnership.com>
    uid                 [  full  ] James Bottomley <jejb@...nel.org>
    uid                 [  full  ] James Bottomley <jejb@...ux.vnet.ibm.com>
    uid                 [  never ] [jpeg image of size 5254]
    uid                 [  full  ] James Bottomley <jejb@...ux.ibm.com>
    sub   nistp256/E742C94CEE98AC85 2018-01-23 [S] [expires: 2024-01-16]
    sub   nistp256/3E01E40786F26FB8 2018-01-23 [E] [expires: 2024-01-16]
    sub   nistp256/920E9CA6AA3F170D 2023-07-20 [A] [expires: 2024-01-16]

Note, that keyids are truncated from the right, as opposed to git commits.

> And the above is actually being *generous* to gpg. The reality is even
> worse. Try this:
> 
>    gpg --list-key 37AAA9562C5CBD0C
> 
> and notice how it doesn't even list the subkey I asked about. Not even
> with '--with-subkey-fingerprint'.

Again, just because I happen to know the right incantation and it may come up
in a search for someone:

    $ gpg --list-options show-unusable-subkeys --list-key 37AAA9562C5CBD0C

You can add it to your .gnupg/gpg.conf as well:

    list-options show-unusable-subkeys

-K