Re: [ietf-dkim] [dmarc-ietf] a slightly less kludge alternative to draft-kucherawy-dmarc-rcpts

Brandon Long <blong@google.com> Tue, 22 November 2016 02:17 UTC

Return-Path: <ietf-dkim-bounces@mipassoc.org>
X-Original-To: ietfarch-ietf-dkim-archive@ietfa.amsl.com
Delivered-To: ietfarch-ietf-dkim-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DDC712958D for <ietfarch-ietf-dkim-archive@ietfa.amsl.com>; Mon, 21 Nov 2016 18:17:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.289
X-Spam-Level:
X-Spam-Status: No, score=-1.289 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_SORBS_SPAM=0.5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yBvjqdSPDR8C for <ietfarch-ietf-dkim-archive@ietfa.amsl.com>; Mon, 21 Nov 2016 18:17:02 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1832E129569 for <ietf-dkim-archive@ietf.org>; Mon, 21 Nov 2016 18:17:02 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [127.0.0.1]) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id uAM2H4VW013369; Mon, 21 Nov 2016 18:17:06 -0800
Authentication-Results: simon.songbird.com; dkim=fail reason="verification failed; unprotected key" header.d=google.com header.i=@google.com header.b=IZHJ0LQf; dkim-adsp=none (unprotected policy); dkim-atps=neutral
Received: from mail-oi0-f54.google.com (mail-oi0-f54.google.com [209.85.218.54]) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id uAM2H1u7013349 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT) for <ietf-dkim@mipassoc.org>; Mon, 21 Nov 2016 18:17:03 -0800
Received: by mail-oi0-f54.google.com with SMTP id w63so4464880oiw.0 for <ietf-dkim@mipassoc.org>; Mon, 21 Nov 2016 18:16:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ToUpEv1UkXQxahV3jWxSjVxfzsDgpWvN8dcr38IrH1A=; b=IZHJ0LQf4dfmTYPvtGBXF2k53tiGTr7Mxxc/BbUhM6B12Q49bbRTM8k8t8TfykhMsu V22/tEXJezlxIqFvGFO7FGVgORTmpYWBMd6+CqU7wIu+LIt1QVFtUaGtqFxsAl8GqBOU 4xAO5a5KP3cVMb4qReZ/Oazbg08oLq6PLPZiWJdAWh/CzGKNPIn6LcnISv2JRMAFBiIP WSzKJOAj1peH34l4dGvgVKGW9ZbZKHg0bfrU2CPSFlviuVVYcOH3L5CfiHN699ZSqGRj RTsVDe30Ou4dGXf21KJr7CyZQCxIQQxi74aNPPGI+2iwOm+F7L1P2UL324AFUSn+ROQi zl5w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ToUpEv1UkXQxahV3jWxSjVxfzsDgpWvN8dcr38IrH1A=; b=T5yF5FIJpoFdsALKbnVb6vIjVB5odFIf2OXQgiQ3JpgrOK/pxAjq+idg17TOEQErRR MwKrwQCJYUv1JX+A29L+7aKAhp7Utj0k1sms4J0NcYC6ZyxEcTKuzWUH7K26jj9sWzzQ YBZXC6+5LDDRZrzmRanh2jmZtdi6DJFKvaqzv/AlZmVJLOWAv5ixmgXWV7dTjDiefh9K XbgrD8At9VEmufDNQmo8DJVZDs2H6svjp2TUKB17YzrClmKSTPsPAxQT+3EP+vRbNZ7R 5m+IZCO/mxFsXmhOlnPqoVULt5MrasDoY+u23KFO9GkSOY2Rx8+CcgufEW/+g9zU7cD2 fzNA==
X-Gm-Message-State: AKaTC01u0rmetFCRWXh6pl9uGAA2LDLqSlrzk6/thJS8f2sCP+y7e7tCmlCrrcBVySz4rW1DWBCfMlHilOKVLO3U
X-Received: by 10.157.4.170 with SMTP id 39mr11923875otm.111.1479780957710; Mon, 21 Nov 2016 18:15:57 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.42.43 with HTTP; Mon, 21 Nov 2016 18:15:55 -0800 (PST)
Received: by 10.157.42.43 with HTTP; Mon, 21 Nov 2016 18:15:55 -0800 (PST)
In-Reply-To: <CAL0qLwZ42=GFDRm7H0qQ_7bczY8CPQaEuSUfgFEbO_Y5+5YvqA@mail.gmail.com>
References: <alpine.OSX.2.11.1611142158000.21738@ary.local> <01Q7ASDZFS6C011WUX@mauve.mrochek.com> <CAL0qLwazAg2UJvGAr+nx8R_xEbc4xV0ttPEWFKUD69u6xXaMhA@mail.gmail.com> <CAL0qLwaMzy=qeW5XYZ_txPaiYE27Oof+C5V1uRANvv-_cayOcQ@mail.gmail.com> <CY1PR00MB0107389F8FE73F140849A19996BE0@CY1PR00MB0107.namprd00.prod.outlook.com> <2736ea21-69e6-83b1-3b59-377c032290b5@dcrocker.net> <CY1PR00MB01072F4EB32969888104C45196BE0@CY1PR00MB0107.namprd00.prod.outlook.com> <CAL0qLwbdNVwT-xiCmxyhSqKcp4-hCA1COHKh0wdYrYEekzZ=XA@mail.gmail.com> <3009defcc6dc9043823618dbc338460d@xmail.mwn.de> <CAL0qLwbvqABZGsm2Hp20y8wgvQTKvPn+EBKiS37eMrp+9NemjA@mail.gmail.com> <da2e49df90980fe460d1effd7734ef42@xmail.mwn.de> <CAL0qLwbA6Vjqpi5hGOtbpLV9FwgDO3VVA=Q5GgAU9F0qOsQCNQ@mail.gmail.com> <63a2bfc52a81eb569a0af5e1699390d9@xmail.mwn.de> <CAL0qLwZ42=GFDRm7H0qQ_7bczY8CPQaEuSUfgFEbO_Y5+5YvqA@mail.gmail.com>
From: Brandon Long <blong@google.com>
Date: Mon, 21 Nov 2016 18:15:55 -0800
Message-ID: <CABa8R6ut_+PNm3xhSu7wQF4bEv_fN3EZESZZYWLaj=A7RECruQ@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: ietf-dkim <ietf-dkim@mipassoc.org>
Subject: Re: [ietf-dkim] [dmarc-ietf] a slightly less kludge alternative to draft-kucherawy-dmarc-rcpts
X-BeenThere: ietf-dkim@mipassoc.org
X-Mailman-Version: 2.1.16
Precedence: list
List-Id: IETF DKIM Discussion List <ietf-dkim.mipassoc.org>
List-Unsubscribe: <http://mipassoc.org/mailman/options/ietf-dkim>, <mailto:ietf-dkim-request@mipassoc.org?subject=unsubscribe>
List-Archive: <http://mipassoc.org/pipermail/ietf-dkim/>
List-Post: <mailto:ietf-dkim@mipassoc.org>
List-Help: <mailto:ietf-dkim-request@mipassoc.org?subject=help>
List-Subscribe: <http://mipassoc.org/mailman/listinfo/ietf-dkim>, <mailto:ietf-dkim-request@mipassoc.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============6652043183712284648=="
Errors-To: ietf-dkim-bounces@mipassoc.org
Sender: ietf-dkim <ietf-dkim-bounces@mipassoc.org>

Also realize that this isn't "Gmail shouldn't sign spam", it's everyone who
normally has a good reputation needs to not sign spam, this is a way to
steal reputation from any service allowing you to choose your own message,
and can be used against any mail receiver.

That said, I think this proposal mostly duplicates spf with some small
benefit, but one can combine the spf and dkim signals to try to combat this
issue without introducing a new standard.  Forwarding will take the worst
hit in false positives, but things like arc may help with that issue
separately.

Brandon

On Nov 17, 2016 12:57 PM, "Murray S. Kucherawy" <superuser@gmail.com> wrote:

> On Thu, Nov 17, 2016 at 9:51 PM, Michael Storz <Michael.Storz@lrz.de>
> wrote:
>
>>
>> Thanks, I see. That means the recipient is bound to the message and an
>> attacker cannot delete or change the new tags. Great solution, I like it,
>> though I do not like the consequences when this extension will go into
>> production.
>>
>>
> You may not need to worry about that.  We've reached a point where I think
> we can legitimately say, "We took a serious look, and this is the best we
> could come up with.  It has some pretty ugly side effects.  Are you sure
> you can't just stop signing spam?"  And absent a compelling answer to that
> question, there's no need to roll this out even as an experiment.
>
> -MSK
>
> _______________________________________________
> NOTE WELL: This list operates according to
> http://mipassoc.org/dkim/ietf-list-rules.html
>
>
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html