IETF Logo Mail Archive

Re: [dispatch] Updating DKIM for stronger crypto

Martin Thomson <martin.thomson@gmail.com> Wed, 22 March 2017 02:38 UTC

Return-Path: <martin.thomson@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D74AA12702E for <dispatch@ietfa.amsl.com>; Tue, 21 Mar 2017 19:38:09 -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, FREEMAIL_FROM=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 jVwm2wUYKk0A for <dispatch@ietfa.amsl.com>; Tue, 21 Mar 2017 19:38:08 -0700 (PDT)
Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::233]) (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 309C912942F for <dispatch@ietf.org>; Tue, 21 Mar 2017 19:38:08 -0700 (PDT)
Received: by mail-qk0-x233.google.com with SMTP id p22so9404549qka.3 for <dispatch@ietf.org>; Tue, 21 Mar 2017 19:38:08 -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=vcgbvrjNE+adt++XuMwyT+KzCTnmO/NAQk8f5VqN/y4=; b=Fs2/jNOCIF3SYh47E9xtJFwtMD20lMexo71SsmkJMdVaxm2drVlJ58drRMVrOIixC3 DF99VvGaP+CJsK/2aP3a1bn1qnqDsADzNUN5qf0dfdxal0PFzg/lU9VSs6ABrFfjo42e 6VzEEHWphx5iN3hgDROT6sHMbg9s+SqqAkuNtj/nIxyvhfwjKvMWO7Gh16tuW9PN3GF6 q7xqT60kdX/P8LlKXoP4TmBQ+XbgHYkkFKHZxkxTfds/fhXOoltqujCyFF2xFRcUS/MD awPj82JgEAmU8jRL1nheCmtueL9neVa9cmV+N08NTZYcX3aX4nahawSv3AZfcahYsso7 hA1Q==
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=vcgbvrjNE+adt++XuMwyT+KzCTnmO/NAQk8f5VqN/y4=; b=gwx4ypcWbpDYPGujkwMV2RE3o3T9yWDvdq0iwwxRncBR3M3kuK7tRvMwBMGZt9eLqo zBDguLm6IOh/UichBoGjpOuzxnO+14ImhVO++0NNr7ZNjYMBBqUekfwQSV2zqqrJJHhn MlPol9shK/lDGGhdcn1zbtvNHT5sU4pYEzcxmGDjGZ1bBQ4ku+aW5IJzkLLZUVr12g27 XrYrJ7mPAIDIBe3cVVY0zBoqLCiSnLkro+Y9tbMOjpXfiTTXdWfccCjbvJaVizXexVdY +BWKguOd+20/sRCpan+XhOgEkZXg7TnN622lYdYenZys0txuHgwvC5BGUprRbriG8ghe iqXg==
X-Gm-Message-State: AFeK/H2Qs4+0HNrC6VvweWOSnihzV5f5ZhC8fCoFK2jUkkPVOHAxeuZw2YsS7S4Yls3fkk0nd9DlHZprNS/WTA==
X-Received: by 10.233.237.130 with SMTP id c124mr118273qkg.144.1490150287398; Tue, 21 Mar 2017 19:38:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.27.194 with HTTP; Tue, 21 Mar 2017 19:38:06 -0700 (PDT)
In-Reply-To: <20170322023133.72699.qmail@ary.lan>
References: <CABkgnnVB3ztkaN3YuQbaVG4znh_3XNu_SWN+9KNmZ66zVF-R+g@mail.gmail.com> <20170322023133.72699.qmail@ary.lan>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Wed, 22 Mar 2017 13:38:06 +1100
Message-ID: <CABkgnnXMtSOzxm1YX7f32iFDXq7gEeznt2Gnm1ni8GRYGmR1jA@mail.gmail.com>
To: John Levine <johnl@taugh.com>
Cc: DISPATCH <dispatch@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/kyhkKCrCSm1kFoMrgxkj8Vycu6c>
Subject: Re: [dispatch] Updating DKIM for stronger crypto
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Mar 2017 02:38:10 -0000

On 22 March 2017 at 13:31, John Levine <johnl@taugh.com> wrote:
> We designed DKIM so we can add
> new hashes and signing algorithms.

Precisely my point.  If that was successful (and it seems like it is
at least on face value), then a new signing algorithm could be done by
basically anyone.

v2.23.0 | Report a Bug | By Email