From: "Örjan Ekeberg" <ekeberg@kth.se>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
Ralph Seichter <abbot@monksofcool.net>,
notmuch@notmuchmail.org
Subject: Re: feature request: caching message arrival time
Date: Mon, 03 Jun 2019 18:02:53 +0200 [thread overview]
Message-ID: <87imtmpsgi.fsf@swing.csc.kth.se> (raw)
In-Reply-To: <87muiyhkpy.fsf@fifthhorseman.net>
Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:
> Sure, assuming that you trust the closest MTA in the chain of MTAs that
> handed the message off to you, since an adversarial proximal MTA could
> manipulate all the existing Received: headers as well.
>
> But I'm a bit uncomfortable with it: this sort of protection actually
> opens up a new attack vector that didn't exist before -- any MTA in the
> chain can now make the message seem like it was actually from the
> *past*, just by setting its own Received: header.
As far as I understand the autocrypt protocol (i.e. not much;-) ), the
vulnerability is that an incoming message with a later time-stamp than
the locally saved autocrypt status can update the stored state
(e.g. turn off encryption). Manipulating the time-stamp to make the
message appear to be *older* than it really is should only mean that it is
less likely to update the saved state?
If this is correct, using the oldest of all the time-stamps seen in the
Date-header and any of the Received-headers should be the most
defensive.
/Örjan
next prev parent reply other threads:[~2019-06-03 16:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-01 3:29 feature request: caching message arrival time Daniel Kahn Gillmor
2019-06-01 14:13 ` David Bremner
2019-06-01 14:19 ` Ralph Seichter
2019-06-01 15:30 ` Daniel Kahn Gillmor
2019-06-03 8:57 ` Örjan Ekeberg
2019-06-03 13:17 ` Daniel Kahn Gillmor
2019-06-03 14:02 ` Ralph Seichter
2019-06-03 22:16 ` Daniel Kahn Gillmor
2019-06-03 16:02 ` Örjan Ekeberg [this message]
2019-06-03 22:21 ` Daniel Kahn Gillmor
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=87imtmpsgi.fsf@swing.csc.kth.se \
--to=ekeberg@kth.se \
--cc=abbot@monksofcool.net \
--cc=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).