From: jam@jamux.com (John A. Martin)
Subject: Re: Problems with PGG and method=pgp mode=sign
Date: Fri, 04 Oct 2002 16:49:21 -0400 [thread overview]
Message-ID: <874rc29bfy.fsf@athene.jamux.com> (raw)
In-Reply-To: <86n0puq88p.fsf@duchess.twilley.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>>>>> "Jack" == Jack Twilley
>>>>> "Re: Problems with PGG and method=pgp mode=sign"
>>>>> Fri, 04 Oct 2002 13:06:30 -0700
Jack> How does mine look?
W s (gnus-summary-force-verify-and-decrypt) shows me
[[PGP Signed Part:Failed]
Signature made Fri Oct 4 16:06:36 2002 EDT using DSA key ID 007F7B38
BAD signature from "Jack M Twilley <jmt@twilley.org>"
]
but C-c / v (mc-verify) says "Good signature..."
Perhaps the W s verify removes the quoted printible encoding while
C-c / v works on the raw file.
On the command line 'gpg --verify' verifies the raw file.
HTH
jam
C-c / s
-----BEGIN PGP SIGNATURE-----
iD8DBQE9nf7FUEvv1b/iXy8RAn7qAJ4xC5z7xCNfNn7FrqGAuFIgPKUIpQCbBZoM
tYlzXyz2oY346/6F6EBn464=
=DNoR
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2002-10-04 20:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-04 19:50 Raymond Scholz
2002-10-04 20:06 ` Jack Twilley
2002-10-04 20:18 ` Jack Twilley
2002-10-04 20:35 ` Graham Murray
2002-10-05 4:46 ` Simon Josefsson
2002-10-05 8:19 ` Graham Murray
2002-10-04 20:49 ` John A. Martin [this message]
2002-10-04 21:05 ` Jack Twilley
2002-10-05 4:43 ` Simon Josefsson
2002-10-05 7:43 ` Jack Twilley
2002-10-05 11:14 ` Simon Josefsson
2002-10-10 20:56 ` Jack Twilley
2002-10-10 21:23 ` Simon Josefsson
2002-10-05 13:32 ` Raymond Scholz
2002-10-09 21:53 ` Simon Josefsson
2002-10-16 13:44 ` Raymond Scholz
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=874rc29bfy.fsf@athene.jamux.com \
--to=jam@jamux.com \
/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).