From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: notmuch@notmuchmail.org
Subject: Re: Inline-encryption, encryption failure when storing sent mails
Date: Tue, 18 Feb 2014 13:31:58 -0500 [thread overview]
Message-ID: <87lhx8w9up.fsf@alice.fifthhorseman.net> (raw)
In-Reply-To: <5213A15F.30109@fifthhorseman.net>
[-- Attachment #1: Type: text/plain, Size: 824 bytes --]
On Tue 2013-08-20 13:03:27 -0400, Daniel Kahn Gillmor wrote:
> I've been meaning to write this up more cleanly, but a summary here will
> have to do for now:
>
> The MIME Content-Type header for an inline-PGP-signed e-mail message is
> not signed. This means that an attacker can replay a signed message
> while undetectably changing the Content-Type. One example of such an
> attack is to leave the base Content-Type as text/plain but to switch
> charsets -- the same bytestream can then be interpreted differently.
I've finally written this up, with a demonstration. I'm hosting it here
for now:
https://dkg.fifthhorseman.net/notes/pgp-inline-harmful/
i hope this is useful for future discussions about inline PGP.
Please let me know if you see any problems with the text or if you have
any questions.
--dkg
[-- Attachment #2: Type: application/pgp-signature, Size: 948 bytes --]
prev parent reply other threads:[~2014-02-18 18:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 16:57 Inline-encryption, encryption failure when storing sent mails Simon Hirscher
2013-08-16 8:02 ` David Bremner
2013-08-16 11:32 ` Simon Hirscher
2013-08-20 17:03 ` Daniel Kahn Gillmor
2014-02-18 18:31 ` Daniel Kahn Gillmor [this message]
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lhx8w9up.fsf@alice.fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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 read-only IMAP folder(s) and NNTP newsgroup(s).