Gnus development mailing list
 help / color / mirror / Atom feed
From: Josh Huber <huber@alum.wpi.edu>
Subject: Re: Force Oort to verify sigs?
Date: 26 Mar 2001 12:56:16 -0500	[thread overview]
Message-ID: <878zlswh1b.fsf@mclinux.com> (raw)
In-Reply-To: <76k85ctpjs.fsf@newjersey.ppllc.com>

Jake Colman <colman@ppllc.com> writes:

> OK, we're getting places.
> 
> I now get the following errors:
> 
> [[PGP Signed Part:Failed]
> gpg: Warning: using insecure memory!
> gpg: armor header: Hash: SHA1
> gpg: armor header: Version: GnuPG v1.0.1 (GNU/Linux)
> gpg: armor header: Comment: For info see http://www.gnupg.org
> gpg: original file name=''
> gpg: Signature made Sat Mar 24 08:53:01 2001 EST using DSA key ID 806C804B
> gpg: Can't check signature: public key not found
> 
> Command exit status: 2
> ]
> 
> Any idea where I go from here?

Either you need to download the public key yourself, or set the
keyserver option in ~/.gnupg/options:

keyserver <server>

-- 
Josh Huber


  reply	other threads:[~2001-03-26 17:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-17 16:44 Alan Shutko
2001-03-17 16:52 ` ShengHuo ZHU
2001-03-17 19:23   ` Shigeki Uno
2001-03-17 19:53     ` Shigeki Uno
2001-03-18  1:28     ` Daniel Pittman
2001-03-21 22:21       ` Jake Colman
2001-03-22  2:10         ` Colin Marquardt
2001-03-22  3:01         ` Daniel Pittman
2001-03-22 18:19           ` Jake Colman
2001-03-22 20:34             ` Paul Jarc
2001-03-22 21:47               ` Jake Colman
2001-03-22 22:47                 ` Paul Jarc
2001-03-23  1:39               ` Russ Allbery
2001-03-23 15:54                 ` Paul Jarc
2001-03-26 17:20                   ` Jake Colman
2001-03-26 17:56                     ` Josh Huber [this message]
2001-03-26 18:58                       ` Jake Colman
2001-03-18  2:07     ` Jack Twilley
2001-03-17 16:52 ` Karl Kleinpaste

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=878zlswh1b.fsf@mclinux.com \
    --to=huber@alum.wpi.edu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).