Re: [dmarc-ietf] ARC Crypto Algorithm Selection
Hector Santos <hsantos@isdg.net> Tue, 23 October 2018 16:23 UTC
Return-Path: <hsantos@isdg.net>
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 997E0130ECF for <dmarc@ietfa.amsl.com>; Tue, 23 Oct 2018 09:23:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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=isdg.net header.b=kXkqqSFh; dkim=pass (1024-bit key) header.d=beta.winserver.com header.b=ARp2hQY3
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 xwuzXXjKkWXK for <dmarc@ietfa.amsl.com>; Tue, 23 Oct 2018 09:23:49 -0700 (PDT)
Received: from ftp.catinthebox.net (ntbbs.winserver.com [76.245.57.69]) by ietfa.amsl.com (Postfix) with ESMTP id E1BC1130EB0 for <dmarc@ietf.org>; Tue, 23 Oct 2018 09:23:48 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2617; t=1540311825; atps=ietf.org; atpsh=sha1; h=Received:Received:Received:Received:Message-ID:Date:From: Organization:To:Subject:List-ID; bh=z+7sbPSS+TP5L1dV6wolNzPeAUo=; b=kXkqqSFhf14HS6d5D2jrkFXarqNXc5stw/gXeq7KrLMwZtc3crhiHQ/jJ8RhCH MCgcVWsCTkIKAvC1btfPkN4lLDiYn5qjQW/GrQ44pI3MkKpzMAYLqa5zATa/CXfp foR7zhDqUKGDmzPdUVvWnv4ggo3HEvecvQ3XntiUBSi0Q=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.6) for dmarc@ietf.org; Tue, 23 Oct 2018 12:23:45 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com; adsp=none author.d=isdg.net signer.d=beta.winserver.com; dmarc=pass policy=reject author.d=isdg.net signer.d=beta.winserver.com (atps signer);
Received: from beta.winserver.com ([76.245.57.74]) by winserver.com (Wildcat! SMTP v7.0.454.6) with ESMTP id 115457959.155996.8924; Tue, 23 Oct 2018 12:23:44 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=2617; t=1540311762; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=5VSicWC jLDpQgqyIedkZEc/4xG6jIsN7Li9cHKnbM4k=; b=ARp2hQY3ZZN2LLmKputOpaq LfmQrOaUd12AbnGM4sZNURvUvCTF4F1oB0Rfl5Nalh/3ZJUQ/JPHoZnpB1ouCyUS YjsV3M1qEEW1QW0s1jFGi9ENtC0k8ZBKQAx1UevzSj+N6lzBLAt9ANVhm0L2uvMD UqcIRQ2cRGDcibeYho3A=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.6) for dmarc@ietf.org; Tue, 23 Oct 2018 12:22:42 -0400
Received: from [192.168.1.68] ([99.121.5.8]) by beta.winserver.com (Wildcat! SMTP v7.0.454.6) with ESMTP id 4151774875.9.213576; Tue, 23 Oct 2018 12:22:41 -0400
Message-ID: <5BCF4B0E.7080909@isdg.net>
Date: Tue, 23 Oct 2018 12:23:42 -0400
From: Hector Santos <hsantos@isdg.net>
Reply-To: hsantos@isdg.net
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.8.1
MIME-Version: 1.0
To: dmarc@ietf.org
References: <57062925.Z3iaeiTUnW@kitterma-e6430> <CABuGu1r9AcgT==u_HtqZMGHmWFP1wpbizFsuUhBFJKeKFePUyA@mail.gmail.com>
In-Reply-To: <CABuGu1r9AcgT==u_HtqZMGHmWFP1wpbizFsuUhBFJKeKFePUyA@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/V_IgB8OBocxKQyzaNLQfUlWLptM>
Subject: Re: [dmarc-ietf] ARC Crypto Algorithm Selection
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 23 Oct 2018 16:23:52 -0000
In my view, ARC, as an "Experimental Status" (and still in design) proposal *should* include support for all valid DKIM STD hashing methods, including rsa-hash1, and I agree, should not be the impetus for removing sha1 support in DKIM implementations. Until a DKIM implementation is "ready" to a) consider DCRUP and b) add support for ed25119-sha256 (which comes with a considerable technical barrier), rsa-sha1 is still going to be available and used by pure DKIM STD implementations for the foreseeable future (a long time). I haven't been seeing many messages in my logs showing rsa-ed25119 DKIM signings, in today's logs so far, not one. -- HLS On 10/23/2018 11:24 AM, Kurt Andersen (b) wrote: > On Tue, Oct 23, 2018 at 3:58 AM Scott Kitterman <sklist@kitterman.com > <mailto:sklist@kitterman.com>> wrote: > > Last time I looked at this particular issue, ARC could use any > algorithm that > DKIM uses. > > > Still correct. > > As I recall, that was once of the stimuli for the DCRUP working > group (to avoid having rsa-sha1 be valid for ARC by obsoleting it > in DKIM). > > > I don't think that ARC drove the DCRUP work as much as the desire to > get badness officially obsoleted :-) > > It looks like this discussion has been moved to a new draft, > https://tools.ietf.org/html/draft-ietf-dmarc-arc-multi-01 > (although the > reference is wrong, > https://tools.ietf.org/html/draft-ietf-dmarc-arc-multi-02 > is current. > > > Yes that's correct. > > Unfortunately, I don't find any actual guidance on what algorithms > are > currently used. > > > Any that are valid for DKIM - see first sentence above. > > Secion 6, Phases of Algorithm Evolution, gives some process > (which seriously needs revision - I thought we all knew flag days > don't work > at Internet scale), but no actual guidance. > > > Correct - we've deferred any real attention on this until we got the > ARC protocol document nailed down. With the request to publish being a > few hours old now from Barry, this might be an excellent topic to > pursue next :-) > > DKIM, as updated by the DCRUP work, has two valid crypto algorithms: > > rsa-sha256 > ed25119-sha256 > > One has been obsoleted: > > rsa-sha1 > > Which among those is valid for ARC and how do I know? > > > The same ones that are valid for DKIM (as updated by DCRUP). What we > haven't worked out is how to handle mixed algorithm chains. > > --Kurt > > > _______________________________________________ > dmarc mailing list > dmarc@ietf.org > https://www.ietf.org/mailman/listinfo/dmarc >
- [dmarc-ietf] ARC Crypto Algorithm Selection Scott Kitterman
- Re: [dmarc-ietf] ARC Crypto Algorithm Selection Kurt Andersen (b)
- Re: [dmarc-ietf] ARC Crypto Algorithm Selection Seth Blank
- Re: [dmarc-ietf] ARC Crypto Algorithm Selection Hector Santos
- Re: [dmarc-ietf] ARC Crypto Algorithm Selection John Levine