From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933540Ab1JDTsS (ORCPT ); Tue, 4 Oct 2011 15:48:18 -0400 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.123]:53283 "EHLO hrndva-omtalb.mail.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933451Ab1JDTsR (ORCPT ); Tue, 4 Oct 2011 15:48:17 -0400 X-Authority-Analysis: v=1.1 cv=lfM0d0QHaVz67dfwwr9cyIw6NbaGR/pZhMD6XWNi0kk= c=1 sm=0 a=ccdOYuaMiZkA:10 a=5SG0PmZfjMsA:10 a=Q9fys5e9bTEA:10 a=17wjrS5wAhQaEczCPkpxpQ==:17 a=meVymXHHAAAA:8 a=2hFTEjvRU0UQRHL_E6kA:9 a=PUjeQqilurYA:10 a=jeBq3FmKZ4MA:10 a=XU36a56C3Wn7RWI9:21 a=4jhNM3m3N5tYgk-a:21 a=17wjrS5wAhQaEczCPkpxpQ==:117 X-Cloudmark-Score: 0 X-Originating-IP: 74.67.83.30 Subject: Re: [RFC][PATCH v2][QUILT] Add gpg signing to quilt mail From: Steven Rostedt To: "H. Peter Anvin" Cc: Greg KH , quilt-dev , LKML , Peter Zijlstra , Andrew Morton , John Kacur , Andreas Gruenbacher Date: Tue, 04 Oct 2011 15:48:15 -0400 In-Reply-To: <4E8B6172.2050006@zytor.com> References: <1317750395.18063.11.camel@gandalf.stny.rr.com> <20111004180237.GA15087@suse.de> <4E8B4BEC.5030708@zytor.com> <1317757101.18063.24.camel@gandalf.stny.rr.com> <4E8B6172.2050006@zytor.com> Content-Type: text/plain; charset="ISO-8859-15" X-Mailer: Evolution 3.0.3- Content-Transfer-Encoding: 7bit Message-ID: <1317757696.18063.28.camel@gandalf.stny.rr.com> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2011-10-04 at 12:41 -0700, H. Peter Anvin wrote: > On 10/04/2011 12:38 PM, Steven Rostedt wrote: > > > > Hmm, gpgv is not quite equivalent to gpg --verify. With gpgv I get the > > following error: > > > > $ gpgv /tmp/gpgvmail-s.x /tmp/gpgvmail-d.x > > gpgv: keyblock resource `/home/rostedt/.gnupg/trustedkeys.gpg': file open error > > gpgv: Signature made Tue 04 Oct 2011 02:35:50 PM EDT using RSA key ID C66DAA00 > > gpgv: Can't check signature: public key not found > > > > > > I don't have a "trustedkeys.gpg" file. Do I need to generate one? > > > > Using gpg --verify, it doesn't complain: > > > > $ gpg --verify /tmp/gpgvmail-s.x /tmp/gpgvmail-d.x > > gpg: Signature made Tue 04 Oct 2011 02:35:50 PM EDT using RSA key ID C66DAA00 > > gpg: Good signature from "Steven Rostedt (Der Hacker) " > > > > gpgv looks at trustedkeys.gpg by default; it's just a different public > keyring. The *big* difference between gpgv and gpg is that the former > doesn't consult the trustdb *at all*. But I'm using this to test what it generated. Not what it received. If you don't trust your own keys than what should you trust ;) I'm going to use gpg to generate your own key, then run this to test if it worked. I guess I could add an option to verify before you send if you are paranoid. quilt mail --send --sign --verify ... Without --verify, it can use gpg to still make sure the key works, with --verify it would use gpgv. Oh this reminds me. I need to change --pass to --sign. -- Steve