From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: James Vasile <james@hackervisions.org>
Cc: notmuch mailing list <notmuch@notmuchmail.org>
Subject: Re: a DoS vulnerability associated with conflated Message-IDs?
Date: Thu, 08 Mar 2012 12:16:18 -0500 [thread overview]
Message-ID: <4F58E962.1050403@fifthhorseman.net> (raw)
In-Reply-To: <87ipif2fdn.fsf@wyzanski.jamesvasile.com>
On 03/08/2012 12:04 PM, James Vasile wrote:
> On Thu, 08 Mar 2012 11:37:09 -0500, Daniel Kahn Gillmor<dkg@fifthhorseman.net> wrote:
>> Any ideas on how to approach this?
>
> Treat messages with the same ID but different hashes as different?
Given that a message hash would include all headers, including Received:
and other MTA-added stuff, i think that would remove all relevance of
the Message-ID field. in particular, it seems like we would just be
identifying messages by their digest.
If you're willing to ignore the headers and just look at a digest of the
body, that still doesn't provide any help for the common (legitimate)
case of a message jointly-delivered to a mailing list and to a specific
(already-subscribed) user.
That user will get two copies of the message, and since most mailing
lists modify the body of the message (usually by adding a footer section
with mailing list info) their bodies will also have different digests.
So i don't see how to make this suggestion work without giving up on
Message-IDs as the identifier entirely (and therefore accepting many
more spurious duplicates than users currently need to tolerate).
Any other suggestions or ideas?
--dkg
next prev parent reply other threads:[~2012-03-08 17:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 16:37 a DoS vulnerability associated with conflated Message-IDs? Daniel Kahn Gillmor
2012-03-08 17:04 ` James Vasile
2012-03-08 17:16 ` Daniel Kahn Gillmor [this message]
2012-03-08 17:38 ` Jeremy Nickurak
2012-03-10 17:38 ` Tom Prince
2012-10-29 11:15 ` Peter Wang
2017-08-04 20:42 ` David Bremner
2017-08-04 22:15 ` Daniel Kahn Gillmor
2022-07-30 12:41 ` David Bremner
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=4F58E962.1050403@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=james@hackervisions.org \
--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).