IETF Logo Mail Archive

Re: [Dcrup] Hashed Key Records

Scott Kitterman <sklist@kitterman.com> Fri, 23 June 2017 01:40 UTC

Return-Path: <sklist@kitterman.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 4BB97129BEE for <dcrup@ietfa.amsl.com>; Thu, 22 Jun 2017 18:40:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, 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=kitterman.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 tbpiY1x1486S for <dcrup@ietfa.amsl.com>; Thu, 22 Jun 2017 18:39:59 -0700 (PDT)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [208.43.65.50]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 240EB129BEC for <dcrup@ietf.org>; Thu, 22 Jun 2017 18:39:59 -0700 (PDT)
Received: from android-df929938bd25e485.home.kitterman.com (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id DEE2FC40166; Thu, 22 Jun 2017 20:39:54 -0500 (CDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=201409; t=1498181995; bh=AKmVHsfmHwSuuEZb5Gi0/fCjfA7fN7ek4ThuDDdBW1A=; h=Date:In-Reply-To:References:Subject:To:From:From; b=bBAnS2rnD+rZrSRI5P2W3bMlVNrJD7zlxkUoyn7YJkJPdfpkDt47dVIssLfosqxRt VeARqU2feBr1h+MEaZH9Ipz7hHsxG8ToebMTIG9oG13SueNXbsxLqfS2sP2iBmSSWj blXJR8IzWHT1oZ7j8Wd5KxV6DFcvH63AoyNEUlfQ=
Date: Fri, 23 Jun 2017 01:39:53 +0000
In-Reply-To: <20170623011831.27734.qmail@ary.lan>
References: <20170623011831.27734.qmail@ary.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
To: dcrup@ietf.org
From: Scott Kitterman <sklist@kitterman.com>
Message-ID: <78E6014E-8D22-497F-9E54-1D5C348B4E0F@kitterman.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/dq0mCi5fXdMEKZ6w5hq3GDNrtoY>
Subject: Re: [Dcrup] Hashed Key Records
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: Fri, 23 Jun 2017 01:40:01 -0000


On June 22, 2017 9:18:31 PM EDT, John Levine <johnl@taugh.com> wrote:
>In article <2793611.63lxTaCm4r@kitterma-e6430> you write:
>>'Hello World'
>>
>>Then the the p tag in DNS would be:
>>
>>p=pZGm1Av0IEBKARczz7exkNYsZb8LzaMrV7J32a2fFG4=
>>
>>Am I understanding it correctly?
>
>Yes.
>
>For us oldthinkers who use shell scripts:
>
>$ echo -n 'Hello World'|openssl sha256 -binary|base64
>pZGm1Av0IEBKARczz7exkNYsZb8LzaMrV7J32a2fFG4=
>
>R's,
>John
>
>PS: In the interest of not inventing anything new, since every
>existing DKIM key record has a base64 version of the data, these do
>too.

Thanks.  I'm working my way through implementing the new options and that seemed like a reasonable place to start.  The dkimpy trunk version of dknewkey.py [1] can make rsafp records now.

It may take awhile as I'm short on available time.

Scott K


[1] http://bazaar.launchpad.net/~dkimpy-hackers/dkimpy/trunk/files

v2.40.4 | Report a Bug | By Email | System Status