linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] final round of SCSI updates for the 6.7+ merge window
Date: Sat, 20 Jan 2024 14:38:39 -0500	[thread overview]
Message-ID: <b7da1112d9adc36722b8509314a7746f6f05764e.camel@HansenPartnership.com> (raw)
In-Reply-To: <CAHk-=wi03SZ4Yn9FRRsxnMv1ED5Qw25Bk9-+ofZVMYEDarHtHQ@mail.gmail.com>

On Sat, 2024-01-20 at 11:35 -0800, Linus Torvalds wrote:
> On Sat, 20 Jan 2024 at 11:09, James Bottomley
> <James.Bottomley@hansenpartnership.com> wrote:
> > 
> > It also seems that this magic option combination works better (just
> > tried it on an old laptop that had my expired keys)
> > 
> > gpg --auto-key-locate clear,dane --locate-external-key
> > james.bottomley@hansenpartnership.com
> 
> So now I have a new subkey.
> 
> However, I note that you really do not seem to have gotten the
> message:
> 
>   sub   nistp256 2018-01-23 [S] [expires: 2026-01-16]
>         E76040DB76CA3D176708F9AAE742C94CEE98AC85
> 
> WTF? What happened to "stop doing these idiotic short expirations"?

I can't extend the expiration longer than that of my main key
(apparently I created it in 2011 with a 25 year expiration ... that
seemed like infinity at the time, right).   I think I can also extend
it but that's more of a virtuoso gpg manoeuvre, so I thought I wouldn't
try that in case it failed spectacularly and you were less than patient
...

James


  reply	other threads:[~2024-01-20 19:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-20 15:26 [GIT PULL] final round of SCSI updates for the 6.7+ merge window James Bottomley
2024-01-20 17:52 ` Linus Torvalds
2024-01-20 19:09   ` James Bottomley
2024-01-20 19:35     ` Linus Torvalds
2024-01-20 19:38       ` James Bottomley [this message]
2024-01-21  6:30       ` Theodore Ts'o
2024-01-21 15:58         ` James Bottomley
2024-01-21 18:48         ` Linus Torvalds
2024-01-24  5:36           ` Theodore Ts'o
2024-01-25 17:56             ` Linus Torvalds
2024-01-20 17:54 ` 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=b7da1112d9adc36722b8509314a7746f6f05764e.camel@HansenPartnership.com \
    --to=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;
as well as URLs for NNTP newsgroup(s).