IETF Logo Mail Archive

Re: [Dcrup] draft-ietf-dcrup-dkim-crypto-00

"John R. Levine" <johnl@iecc.com> Sat, 20 May 2017 01:03 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: dcrup@ietfa.amsl.com
Delivered-To: dcrup@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF65F12942F for <dcrup@ietfa.amsl.com>; Fri, 19 May 2017 18:03:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.479
X-Spam-Level: *
X-Spam-Status: No, score=1.479 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.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 nDMwjViI4QnX for <dcrup@ietfa.amsl.com>; Fri, 19 May 2017 18:03:13 -0700 (PDT)
Received: from miucha.iecc.com (www.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93880126BF6 for <dcrup@ietf.org>; Fri, 19 May 2017 18:03:13 -0700 (PDT)
Received: (qmail 41327 invoked from network); 20 May 2017 01:03:12 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:mime-version:content-type:user-agent; s=a16d.591f95d0.k1705; bh=dJ/jXW76Rzz0ZmMgPu05ZG8wb6yaXwzKk7kBOQdebVA=; b=WI25X9V02ISyZpQ8I8Lel1oafJxlZ4vVWFLjNIPVyawg8XrNX3EwHZN3b2HZLw/Dn3SRMm9XBm+7kM5jtNBYeLwMwNZifupoW6QsxSM/EDYAPfwmpbMIDHinEaV6UfA1MJz8tsEPC+RfncNflhCtlWsCJ8IozdEpxfSx0XlG+Abk1roQyFI7BgIu5luc9ri3PZsy4JeSPJKywIcscqcYNyi86z/RWK4cZyi5YupDWp4YHYQXYBMyLmpU3ahpnIM5
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 20 May 2017 01:03:12 -0000
Date: Fri, 19 May 2017 21:03:11 -0400
Message-ID: <alpine.OSX.2.21.1705192102340.7697@ary.qy>
From: "John R. Levine" <johnl@iecc.com>
To: dcrup@ietf.org
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/qywX6ys2QKubFsM4zfcZ2gZ4_0Y>
Subject: Re: [Dcrup] draft-ietf-dcrup-dkim-crypto-00
X-BeenThere: dcrup@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: DKIM Crypto Update <dcrup.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dcrup>, <mailto:dcrup-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dcrup/>
List-Post: <mailto:dcrup@ietf.org>
List-Help: <mailto:dcrup-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dcrup>, <mailto:dcrup-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 May 2017 01:03:15 -0000

In article <CAOj=BA0gKP9x5jgkZEUJD-EJvRSwC0dgmijwbDirsCQT4z0E4Q@mail.gmail.com>,
Peter Goldstein  <peter@valimail.com> wrote:
>The challenges with 2048 bit RSA are largely an issue of the limitations of
>the DNS infrastructure in use by the sending domain.  In some DNS managers,
>the Web UIs (and occasionally the underlying infrastructure) don't allow
>domain owners to enter records that are larger than 512 octets.  Users of
>these DNS managers generally cannot provision 2048 bit key DKIM TXT
>records. ...

The problem isn't the 512 byte limit, since a 2K key is under 400
bytes.  The problem is provisioning crudware that can't create TXT
records with two strings.  But until the crudware is updated, which
will likely be never, it's a problem.

R's,
John

v2.23.0 | Report a Bug | By Email