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

Vladimir Dubrovin <dubrovin@corp.mail.ru> Thu, 06 April 2017 21:28 UTC

Return-Path: <dubrovin@corp.mail.ru>
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 E8B2C12945E for <dmarc@ietfa.amsl.com>; Thu, 6 Apr 2017 14:28:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=corp.mail.ru
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 Tb153yCue34j for <dmarc@ietfa.amsl.com>; Thu, 6 Apr 2017 14:28:18 -0700 (PDT)
Received: from smtp21.mail.ru (smtp21.mail.ru [94.100.179.250]) (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 6E3DD1294A4 for <dmarc@ietf.org>; Thu, 6 Apr 2017 14:28:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=corp.mail.ru; s=mail; h=Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:References:To:Subject; bh=3FFQLqmQeROScXeYrlB4TbCH7+n63V6Hqpdo/nNOKuA=; b=Xwxsbk12lq68FiHkmFd5QTR20+uMVRUPLnyIoLnUcDxIf7yHMvkuHMtJdZob3Z6t4P9FQlHu3vBKJyonOYAQp6rrVV3dEeJS8QO9X+jmK195lZ5I0RfXlf0v+Yb3GQDL6+/YuyfuoOLZP/sqwaTkqMxo/+U9F093s4XHYjjnzXQ=;
Received: from gate.3proxy.ru ([95.79.31.239]:62350 helo=[127.0.0.1]) by smtp21.mail.ru with esmtpa (envelope-from <dubrovin@corp.mail.ru>) id 1cwEwu-0000TA-MD; Fri, 07 Apr 2017 00:28:13 +0300
To: Scott Rose <scott.rose@nist.gov>, "dmarc@ietf.org" <dmarc@ietf.org>
References: <149149960391.22024.11499305209108527807.idtracker@ietfa.amsl.com> <ac345fcc-ae8e-a92a-0ec3-4792529c865d@nist.gov>
From: Vladimir Dubrovin <dubrovin@corp.mail.ru>
Message-ID: <d91de205-05b4-0b59-b3a3-568fc0f57375@corp.mail.ru>
Date: Fri, 07 Apr 2017 00:28:10 +0300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <ac345fcc-ae8e-a92a-0ec3-4792529c865d@nist.gov>
Content-Type: multipart/alternative; boundary="------------B5ECBF7DD255ACCFC55C5140"
Authentication-Results: smtp21.mail.ru; auth=pass smtp.auth=dubrovin@corp.mail.ru smtp.mailfrom=dubrovin@corp.mail.ru
X-7FA49CB5: 0D63561A33F958A555A373A2EF246E09C7C48DA462C775D3C51E545D75AB57429F18ECD7E95F35E929AFE063DF4C541C70BF3F6ACA3A28AFFBDEBB5FAF816B060BF2EBBBDD9D6B0F2AF914666EE41260
X-Mailru-Sender: C5364AD02485212FBEAE30F3FA322883228C178CD7CAB48FC8D4356BD0D6A11B0E8F58CB380BC13FCDCEB298E575E7B2C77752E0C033A69EDAAA56350C7513E7ACB45E4F000D93863453F38A29522196
X-Mras: OK
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/BY8j9nfK5CLn0fxXARvORQPQ7tE>
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: Thu, 06 Apr 2017 21:28:22 -0000

Hello Scott,

it may be good to cover compatibility issues, because otherwise there
are little chances to succeed the older but more compatible protocols in
nearest future.  The possible (but probably not the best one) solution is:

1. produce 2 different DKIM-Signatures with 2 different selectors:
slector1  with SHA-1 + RSA and selector2 one with  SHA-512 + ECDSA
2. add an additional field to either selector1 DKIM DNS record (need to
consult RFC if it's allowed) or to DKIM-Signature with selector1 (it's
allowed but probably is not enough to protect against downgrade) to
indicate the selector is legacy-only, e.g. o=sha512/eccp256 to indicate
this selector should be ignored if verifier supports sha-512 and eccp256.

Legacy verifier has valid DKIM-Signature with sha1+rsa
Compatible verifier ignores sha1+rsa and choose sha-512+ECDSA

I can imagine few more ways to resolve compatibility issues, but this
one seems to be a simplest.


06.04.2017 20:32, Scott Rose пишет:
> This may be of interest to this group, as there isn't an active DKIM
> WG anymore.  This is my first attempt to produce a draft about
> defining new digital algorithms for DKIM.  I'm trying to keep this
> short i.e. only define a few IANA registry entries and that's it.
>
> I'm trying to head off a potential issue for organizations that are
> told to migrate to ECDSA or looking for algorithm agility that doesn't
> involve using SHA-1.
>
> Comments welcome and needed. Including being told this isn't needed
> (though I think it might be).
>
> Scott Rose
>
> NIST
>
>
>
> -------- Forwarded Message --------
> Subject:     New Version Notification for draft-srose-dkim-ecc-00.txt
> Date:     Thu, 6 Apr 2017 10:26:43 -0700
> From:     internet-drafts@ietf.org
> To:     Scott Rose <scott.rose@nist.gov>
>
>
>
> A new version of I-D, draft-srose-dkim-ecc-00.txt
> has been successfully submitted by Scott Rose and posted to the
> IETF repository.
>
> Name:        draft-srose-dkim-ecc
> Revision:    00
> Title:        Defining Elliptic Curve Cryptography Algorithms for use
> with DKIM
> Document date:    2017-04-06
> Group:        Individual Submission
> Pages:        6
> URL:           
> https://www.ietf.org/internet-drafts/draft-srose-dkim-ecc-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-srose-dkim-ecc/
> Htmlized:       https://tools.ietf.org/html/draft-srose-dkim-ecc-00
> Htmlized:      
> https://datatracker.ietf.org/doc/html/draft-srose-dkim-ecc-00
>
>
> Abstract:
>    DomainKeys Identified Mail (DKIM) uses digital signature to associate
>    a message with a given sending domain.  Currently, there is only one
>    cryptography algorithm defined for use with DKIM (RSA).  This
>    document defines four new elliptic curve cryptography algorithms for
>    use with DKIM.  This will allow for algorithm agility if a weakness
>    is found in RSA, and allows for smaller key length to provide the
>    same digital signature strength.
>
>                                                                                  
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc


-- 
Vladimir Dubrovin
@Mail.Ru