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] first round of SCSI updates for the 6.7+ merge window
Date: Thu, 11 Jan 2024 17:47:02 -0500 [thread overview]
Message-ID: <3b5b650fa3c6ed6dc7f296eb7258c722a699147d.camel@HansenPartnership.com> (raw)
In-Reply-To: <CAHk-=whKVgb27o3+jhSRzuZdpjWJiAvxeO8faMjHpb-asONE1g@mail.gmail.com>
On Thu, 2024-01-11 at 14:36 -0800, Linus Torvalds wrote:
> On Wed, 10 Jan 2024 at 12:48, James Bottomley
> <James.Bottomley@hansenpartnership.com> wrote:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git scsi-
> > misc
>
> Ok, I note that this has been signed with ECDSA key
> E76040DB76CA3D176708F9AAE742C94CEE98AC85, and while it is currently
> available and up-to-date at kernel.org, it shows as
>
> sub nistp256 2018-01-23 [S] [expires: 2024-01-16]
> E76040DB76CA3D176708F9AAE742C94CEE98AC85
>
> note that expiration date: it's three days in the future.
>
> Can I please ask you for the umpteenth time to STOP DICKING AROUND
> WITH SHORT EXPIRATION DATES!
>
> The pgp keyservers work *so* badly these days that refreshing keys is
> a joke. The whole expiration date thing has always been a bad joke,
> and only makes pgp an even worse UX than it already is (and damn,
> that's saying a lot - pgp is some nasty stuff).
Well, I did already tell you that I bypass the pgp keyservers because I
use a DNSSEC based DANE entry instead:
https://lore.kernel.org/all/1564171685.9950.14.camel@HansenPartnership.com/
And I'm sure there was an earlier one where you confirmed this worked,
but lore seems to be missing it.
> When you make a new key, or when you extend the expiration date, do
> it properly. Give ita lifetime that is a big fraction of a decade. Or
> two.
>
> Because your keys constantly end up being expired, and they are
> making the experience of pulling from you a pain - because I actually
> *check* the keys.
>
> Stop making a bad pgp experience even worse - for no reason and
> absolutely zero upside.
I can concede that if I'm the only person with a DANE updateable key
then it is a pain to remember because gpg doesn't automatically do it
(although it can be configured to), so I can certainly set a longer
expiry date.
James
next prev parent reply other threads:[~2024-01-11 22:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 20:48 [GIT PULL] first round of SCSI updates for the 6.7+ merge window James Bottomley
2024-01-11 22:36 ` Linus Torvalds
2024-01-11 22:47 ` James Bottomley [this message]
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
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=3b5b650fa3c6ed6dc7f296eb7258c722a699147d.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).