From: "Rupa Schomaker (list)" <rupa-list@rupa.com>
Subject: attachments and signing
Date: 22 Aug 1999 22:20:44 -0700 [thread overview]
Message-ID: <m3u2prhy37.fsf@gw.rupa.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I just sent an email with an attachment and signed the message. I
CCed the message to myself and then "verified" the signature. PGP
gave a bad signature.
Is this a known problem? Is there a fix? I'm using MailCrypt.
Looks like the attachment is done after the signing not before. This
message is signed since the Sig block has all the version info
necessary...
- --
Rupa (rupa@rupa.com for normal email)
Please don't email duplicate replies.
-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Comment: Processed by Mailcrypt 3.5.3, an Emacs/PGP interface
Charset: noconv
iQA/AwUBN8DaDT8v6x42dn3hEQKg9QCg92DCZjsXq0HqUiynv4obLYRXa3cAniZj
hLGiU+x8h97p5PnJTvwIJwtm
=gkna
-----END PGP SIGNATURE-----
next reply other threads:[~1999-08-23 5:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-23 5:20 Rupa Schomaker (list) [this message]
1999-08-23 10:23 ` Robert Bihlmeyer
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=m3u2prhy37.fsf@gw.rupa.com \
--to=rupa-list@rupa.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).