Re: [dmarc-ietf] Fwd: New Version Notification for draft-srose-dkim-ecc-00.txt

"Murray S. Kucherawy" <superuser@gmail.com> Sat, 08 April 2017 03:04 UTC

Return-Path: <superuser@gmail.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFEAA126DFB for <dmarc@ietfa.amsl.com>; Fri, 7 Apr 2017 20:04:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 S5IiS4v4fz4L for <dmarc@ietfa.amsl.com>; Fri, 7 Apr 2017 20:04:14 -0700 (PDT)
Received: from mail-vk0-x22e.google.com (mail-vk0-x22e.google.com [IPv6:2607:f8b0:400c:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C5C6E1286CA for <dmarc@ietf.org>; Fri, 7 Apr 2017 20:04:13 -0700 (PDT)
Received: by mail-vk0-x22e.google.com with SMTP id d188so88144946vka.0 for <dmarc@ietf.org>; Fri, 07 Apr 2017 20:04:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=OWSQ4sphPtefNceROINJW0JPFtVEt86RSw9eZAtPgbI=; b=LFwSde0NEyZ1xW4s76I5jglwmiqYAf5w9AHmwNM8iK8Yb0v/QFGpQYV5LGbZ6H0K9j iFDE8Bt/IyyXQqtU//lRj44tPYi6SNs9K3MDcTnPzSSqIGXSqdALjDs8/NO7jGcqG8Nj QNxzTiKPPmwqaPb4aggfopQ9uJaaEjM36yDt3wT4Naf7VugP9A7h4xHpjSL2kBbhjKor PI95Itoyj7OCosEMGmvatBfC6yz+HW8AP2WdoYbXeLn1oTjsiEjY9KSt3OrlE1pJikeN fsiAcehWsd1h2ioawlK05btRFOBtnd5iEdmm1KpTXcqLVo7mcB1q2Wlxl7tBz772veQ+ g1tg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=OWSQ4sphPtefNceROINJW0JPFtVEt86RSw9eZAtPgbI=; b=XepuBiwYmpRXqWpmmPFuvhlXzvEMSpXIspKk+rpJ2AHfHhgoZQfRWSX3HyBBfEumRv c6cYpkwRCe8OKQOyim5riDbOVc97lTVHLKBPG1orG8DiFENJjWS0OsjwrrTg5kyPzqJK +CrQmclF8/+XXFDx84sPAna5rjvWRtbjmdUhiREYobNm5Ijmaoio4cetCYQl2dpOFzwo 2OdR3TX6z7IykC1Gw9RchjymQpokzk6UlvQTxOlPQpMWGHxUZSISxYdUCRzplcfAvape p8DK/gmyqZhZeTUug4wgBa4zU9k5BNfqoPuP6kjjo8dG36Sv1W9mWUI++cKZbTLMJl5M ADDw==
X-Gm-Message-State: AFeK/H0R+2KrqvZL0i5bA1Cx1bzkHiVJ9OVhoT7ZH7hMyg+9HbmQNYQYiL98AIpW+CapdfMePhAfXH+gAIL5ww==
X-Received: by 10.31.183.19 with SMTP id h19mr17072112vkf.110.1491620652819; Fri, 07 Apr 2017 20:04:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.130.70 with HTTP; Fri, 7 Apr 2017 20:04:12 -0700 (PDT)
In-Reply-To: <CAOj=BA2P5e1o-QsZGAxGCV6rM1D=sNiL_ciL4BDtMkbQU1tSXA@mail.gmail.com>
References: <d91de205-05b4-0b59-b3a3-568fc0f57375@corp.mail.ru> <20170406235815.47843.qmail@ary.lan> <CAOj=BA2P5e1o-QsZGAxGCV6rM1D=sNiL_ciL4BDtMkbQU1tSXA@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Fri, 07 Apr 2017 20:04:12 -0700
Message-ID: <CAL0qLwa=BScp_1eK6TCxQv2c_S9s93Nk0mc5WU-gG6UHb4Vk6Q@mail.gmail.com>
To: Peter Goldstein <peter@valimail.com>
Cc: John Levine <johnl@taugh.com>, dmarc <dmarc@ietf.org>, Vladimir Dubrovin <dubrovin@corp.mail.ru>
Content-Type: multipart/alternative; boundary="001a1143a44a26bcc6054c9efff1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/o0t-dlTSqGu2TJK6quFIoiJIr10>
Subject: Re: [dmarc-ietf] Fwd: New Version Notification for draft-srose-dkim-ecc-00.txt
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Apr 2017 03:04:16 -0000

On Fri, Apr 7, 2017 at 8:33 AM, Peter Goldstein <peter@valimail.com> wrote:

> Does this initiative include an intention to update the cryptographic
> guidance from RFC 6376 sections 3.3 and 3.3.3 ?  The proposed charter
> speaks of adding new algorithms, but doesn't discuss deprecating/removing
> old ones.
>

As John said, DCRUP could do this.


> Some specific concerns are:
>
> 1. Expressly forbidding RSA keys < 1024 bits in size - While the fact that
> some major receivers ignore such keys has made this a de facto standard, it
> would be good for the RFCs to reflect best practice here.  And as we saw
> with the ARC discussion, using the DKIM spec as a reference can
> inadvertently result in new standards supporting known insecure practices.
>

I'm not sure about forbidding, but expressly deprecating by removing
mandatory support would certainly be allowed.


> 2. Eliminating SHA-1 - Even at the time of publication RFC 6376
> recommended that signers avoid the use of SHA-1.  Despite this, a simple
> check of my inbox shows that quite a few senders - including a number of
> large, sophisticated ESPs - still use SHA-1 in preference to SHA-256.
> While the recent developed PDF collision attack against SHA-1 is not
> entirely on point, it seems to be further evidence that SHA-1 should not be
> used.  And given the widespread support for SHA-256, this seems like it's
> mostly a configuration issue for senders.
>

Same issue, because the installed base isn't going to update itself quickly
even if we really want it to.

-MSK