From: Jani Nikula <jani@nikula.org>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
	Andrei POPESCU <andreimpopescu@gmail.com>
Subject: Re: notmuch-mutt: support for duplicate message removal
In-Reply-To: <50196548.3030504@fifthhorseman.net>
References: <1343808582-9519-1-git-send-email-zack@upsilon.cc>
	<87pq7aam8n.fsf@nikula.org> <20120801162605.GA6012@sid.nuvreauspam>
	<50196548.3030504@fifthhorseman.net>
User-Agent: Notmuch/0.13.2+104~gaee3080 (http://notmuchmail.org) Emacs/23.3.1
	(i686-pc-linux-gnu)
Date: Wed, 01 Aug 2012 22:18:55 +0300
Message-ID: <87d33av2sg.fsf@nikula.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: notmuch@notmuchmail.org, "Kevin J. McCarthy" <kevin@8t8.us>,
	Stefano Zacchiroli <zack@upsilon.cc>
Precedence: list

On Wed, 01 Aug 2012, Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote:
> On 08/01/2012 12:26 PM, Andrei POPESCU wrote:
>> I'm at least one user that cares enough about the distinction to have 
>> all list mails received via a different address, just to avoid Gmail's 
>> "feature" of silently dropping my own messages received via a list. 
>> IMVHO it should at least be configurable...
>
> The proposed feature could also exacerbate the previously-discussed
> attack vector [0] whereby a malicious Message-ID collision can be used
> to hide messages from the victim's mailstore.

Just to clarify, the feature proposed in this patch series does not make
the problem worse (as it would hide only fully identical messages, which
is not useful for the malicious purpose).

What I suggested [1] could indeed make notmuch-mutt as vulnerable to the
attack vector as notmuch show, and the emacs ui, currently are (but not
worse than that).

BR,
Jani.

[1] id:"87pq7aam8n.fsf@nikula.org"

>
> 	--dkg
>
> [0] id:87k42vrqve.fsf@pip.fifthhorseman.net