[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b7da1112d9adc36722b8509314a7746f6f05764e.camel@HansenPartnership.com>
Date: Sat, 20 Jan 2024 14:38:39 -0500
From: James Bottomley <James.Bottomley@...senPartnership.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>, linux-scsi
<linux-scsi@...r.kernel.org>, linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] final round of SCSI updates for the 6.7+ merge window
On Sat, 2024-01-20 at 11:35 -0800, Linus Torvalds wrote:
> On Sat, 20 Jan 2024 at 11:09, James Bottomley
> <James.Bottomley@...senpartnership.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@...senpartnership.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
Powered by blists - more mailing lists