From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753568Ab2EVHWm (ORCPT ); Tue, 22 May 2012 03:22:42 -0400 Received: from bedivere.hansenpartnership.com ([66.63.167.143]:47612 "EHLO bedivere.hansenpartnership.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752971Ab2EVHV4 (ORCPT ); Tue, 22 May 2012 03:21:56 -0400 Message-ID: <1337671311.16400.12.camel@dabdike.int.hansenpartnership.com> Subject: Re: [GIT PULL] First round of SCSI updates for the 3.4+ merge window From: James Bottomley To: Linus Torvalds Cc: Andrew Morton , linux-scsi , linux-kernel Date: Tue, 22 May 2012 08:21:51 +0100 In-Reply-To: References: <1337599819.3042.7.camel@dabdike.int.hansenpartnership.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.2.3 Content-Transfer-Encoding: 7bit Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2012-05-21 at 17:52 -0700, Linus Torvalds wrote: > On Mon, May 21, 2012 at 4:30 AM, James Bottomley > wrote: > > The patch contains the usual assortment of driver updates (be2iscsi, > > bfa, bnx2i, fcoe, hpsa, isci, lpfc, megaraid, mpt2sas, pm8001, sg) plus > > an assortment of other changes and fixes. Also new is the fact that the > > isci update is delivered as a git merge (with signed tag). > > Interesting. For some reason the 'gpg --verify' phase says that your > key has expired. Yet when I look at the key itself, it says it is > valid until 2016. I don't quite know why gpg thinks the thing is > expired when verifying the message. 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: pub 2048R/214854D6 2011-09-23 [expires: 2016-09-27] uid James Bottomley uid James Bottomley uid James Bottomley uid [jpeg image of size 5254] sub 2048R/0D77E313 2011-09-23 [expires: 2012-10-25] sub 2048R/2C5CBD0C 2011-10-27 [expires: 2012-10-25] The 2048R/2C5CBD0C is my signature one. I have to update the expiry of them every six months, so you probably haven't done a refresh since I did the update. I do it this way so that I don't have to carry my master key with me when travelling (or if I do, I don't have to use it except for signing other keys, since the GPG devices are a bit cumbersome), so if something goes wrong, I can revoke my subkey and just generate a new one (without having to get everyone's signature again). > But everything else looks fine. Somebody with more gpg-fu than me > might be able to clarify what is going on.. Hope the above helps (would rather not have had to become a gpg advanced user, but there you go ...) James