From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: [git patches] libata updates, GPG signed (but see admin notes) Date: Mon, 31 Oct 2011 14:46:25 -0700 Message-ID: <4EAF1731.2070908@zytor.com> References: <20111026202235.GA20928@havoc.gtf.org> <1319969101.5215.20.camel@dabdike> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: Received: from terminus.zytor.com ([198.137.202.10]:39869 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932356Ab1JaVqo (ORCPT ); Mon, 31 Oct 2011 17:46:44 -0400 In-Reply-To: Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Linus Torvalds Cc: James Bottomley , Jeff Garzik , Andrew Morton , linux-ide@vger.kernel.org, LKML On 10/30/2011 10:12 AM, Linus Torvalds wrote: > > Actually, I have been running "gpg --verify" on the email that use the > standard PGP encapsulation (ie the kind that Jeff used, that has > "-----BEGIN PGP SIGNED MESSAGE-----" in it. > > It's the rfc3516-type email (aka protocol="application/pgp-encrypted") > type that I can't even verify, because that's not something that gpg > knows inherently how to check: you have to decode the message the > right way and know what the rules are, and I have no intention of > trying to figure it out. I have yet to find any usable tool that is > able to check it, and I'm certainly not going to waste time trying to > parse the rfc and write my own. > What client are you using (or are you using the gmail web interface?) -hpa