[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1337701776.2932.15.camel@dabdike.int.hansenpartnership.com>
Date: Tue, 22 May 2012 16:49:36 +0100
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] First round of SCSI updates for the 3.4+ merge window
On Tue, 2012-05-22 at 08:44 -0700, Linus Torvalds wrote:
> On Tue, May 22, 2012 at 12:21 AM, James Bottomley
> <James.Bottomley@...senpartnership.com> wrote:
> >
> > You probably need to do a gpg --refresh
> >
> > I use the subkeys method for signing, so I have my master key (which
> > expires in 2016) in one of Greg's GPG devices, but I have signing and an
> > encryption subkeys which are short lived (currently expire in Oct 2012).
> > If you do a gpg --list-keys 'James Bottomley' you'll see this:
>
> Ayup, that fixed it. Really confusing how it doesn't even show the
> signing key expiry date if you just look at the key ID..
If you find *that* the only confusing thing about gpg, we'll award you
the gold star grand master of expertise in it. When my subkeys expired,
it took me a day to figure out from the error message I got trying to
sign something what the problem actually was.
James
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists