From: Chris Green <cmg@uab.edu>
Subject: pgpmime "gotcha"
Date: Mon, 04 Feb 2002 11:55:14 -0600 [thread overview]
Message-ID: <m2elk1rv25.fsf@phosphorus.tucc.uab.edu> (raw)
I was bitten by this today so I figured I'd aleast document the fact
that things may not work the way you expect them to work.
I was forwarding an email to somone that I know and the data was
sensitive enough that I decided to use pgpmime.
Did a pgp/mime sign and didn't even notice that it was a "pgpmime sign
attachment".
Short story:
pgpmime part
"hi this is the email"
mimeattachment
[ this is what I'm sending you ]
C-c C-c and the msg part gets encrypted but the forwarded part
didn't. Now I understand the pgpmime part treats each part as a
separate attachment but once I decided that part of the mail was
important enough to protect, it'd be nice to atleast have a warning on
the rest or apply it globablly to each mime part.
I take it pgpmime requires each part individually done rather than
make the message and encrypt the whole thing like the old days.
Hope this helps someone avoid getting burned badly.
--
Chris Green <cmg@uab.edu>
A good pun is its own reword.
next reply other threads:[~2002-02-04 17:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-04 17:55 Chris Green [this message]
2002-02-04 20:25 ` Simon Josefsson
2002-02-04 20:42 ` Chris Green
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=m2elk1rv25.fsf@phosphorus.tucc.uab.edu \
--to=cmg@uab.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).