mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
	 Andrew Morton <akpm@linux-foundation.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	 linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] first round of SCSI updates for the 6.7+ merge window
Date: Fri, 12 Jan 2024 09:27:27 -0500	[thread overview]
Message-ID: <20240112-steadfast-eager-porcupine-2c9b3a@lemur> (raw)
In-Reply-To: <CAHk-=wi6PenRqDCuumMK_5+_gU+JdUqrBEDS-XwFiaNdVRZAHA@mail.gmail.com>

On Thu, Jan 11, 2024 at 03:50:32PM -0800, Linus Torvalds wrote:
> > jejb@lingrow:~> gpg --list-key E76040DB76CA3D176708F9AAE742C94CEE98AC85
> > pub   rsa2048 2011-09-23 [SC] [expires: 2026-03-11]
> >       D5606E73C8B46271BEAD9ADF814AE47C214854D6
> > uid           [ultimate] James Bottomley
> > <James.Bottomley@HansenPartnership.com>
> > uid           [ultimate] James Bottomley <jejb@linux.vnet.ibm.com>
> > uid           [ultimate] James Bottomley <jejb@kernel.org>
> > uid           [ultimate] [jpeg image of size 5254]
> > uid           [ultimate] James Bottomley <jejb@linux.ibm.com>
> > uid           [ultimate] James Bottomley <jejb@hansenpartnership.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@HansenPartnership.com>
    uid                 [  full  ] James Bottomley <jejb@kernel.org>
    uid                 [  full  ] James Bottomley <jejb@linux.vnet.ibm.com>
    uid                 [  never ] [jpeg image of size 5254]
    uid                 [  full  ] James Bottomley <jejb@linux.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

  reply	other threads:[~2024-01-12 14:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-10 20:48 James Bottomley
2024-01-11 22:36 ` Linus Torvalds
2024-01-11 22:47   ` James Bottomley
2024-01-11 22:53     ` Linus Torvalds
2024-01-11 22:47   ` Linus Torvalds
2024-01-11 23:28     ` James Bottomley
2024-01-11 23:50       ` Linus Torvalds
2024-01-12 14:27         ` Konstantin Ryabitsev [this message]
2024-01-12 18:34           ` Linus Torvalds
2024-01-11 22:57 ` pr-tracker-bot

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=20240112-steadfast-eager-porcupine-2c9b3a@lemur \
    --to=konstantin@linuxfoundation.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®