All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Greg KH <gregkh@suse.de>, quilt-dev <quilt-dev@nongnu.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Andrew Morton <akpm@linux-foundation.org>,
	John Kacur <jkacur@redhat.com>,
	Andreas Gruenbacher <agruen@suse.de>
Subject: Re: [RFC][PATCH v2][QUILT] Add gpg signing to quilt mail
Date: Tue, 04 Oct 2011 15:38:20 -0400	[thread overview]
Message-ID: <1317757101.18063.24.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <4E8B4BEC.5030708@zytor.com>

On Tue, 2011-10-04 at 11:09 -0700, H. Peter Anvin wrote:

> gpgv is only usable to verify contents (equivalent to gpg --verify).
> For other things you need to use gpg's --status-fd feature, *or*
> (perhaps better) run gpgv on the output to verify that you actually got
> a good signature.

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) <rostedt@goodmis.org>"

-- Steve



  parent reply	other threads:[~2011-10-04 19:38 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-04 17:46 [RFC][PATCH v2][QUILT] Add gpg signing to quilt mail Steven Rostedt
2011-10-04 18:02 ` Greg KH
2011-10-04 18:09   ` H. Peter Anvin
2011-10-04 18:18     ` Steven Rostedt
2011-10-04 18:18     ` Greg KH
2011-10-04 19:38     ` Steven Rostedt [this message]
2011-10-04 19:41       ` H. Peter Anvin
2011-10-04 19:48         ` Steven Rostedt
     [not found]           ` <1317769149.1662.28.camel@schurl.linbit>
2011-10-10 15:35             ` Steven Rostedt
2011-10-10 15:37               ` [Quilt-dev] " Josh Boyer
2011-10-11  2:39               ` Andreas Gruenbacher
2011-10-04 18:15   ` Steven Rostedt
2011-10-04 18:26     ` Greg KH
2011-10-04 18:37       ` Steven Rostedt
2011-10-05  1:48         ` [Quilt-dev] " Andreas Gruenbacher
2011-10-05  6:53           ` Greg KH
2011-10-05  8:23             ` Andreas Gruenbacher
2011-10-05 11:21             ` Andreas Gruenbacher
2011-10-05 20:12               ` Greg KH
2011-10-05 20:18                 ` Josh Boyer
2011-10-04 18:59 ` Peter Zijlstra
2011-10-04 19:11   ` Steven Rostedt
2011-10-04 19:20   ` Valdis.Kletnieks
2011-10-04 19:35     ` Steven Rostedt
2011-10-06 10:27 ` [RFC][PATCH v2][QUILT] Add Peter Zijlstra
2011-10-06 17:26   ` Andrew Morton
2011-10-06 17:57     ` Steven Rostedt

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=1317757101.18063.24.camel@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=agruen@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@suse.de \
    --cc=hpa@zytor.com \
    --cc=jkacur@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quilt-dev@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.