Re: [Dcrup] Hashed Key Records
Scott Kitterman <sklist@kitterman.com> Fri, 23 June 2017 00:07 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 2E9B7126B72 for <dcrup@ietfa.amsl.com>; Thu, 22 Jun 2017 17:07:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 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] 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 g2z8rViAPMDM for <dcrup@ietfa.amsl.com>; Thu, 22 Jun 2017 17:07:21 -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 784D3129413 for <dcrup@ietf.org>; Thu, 22 Jun 2017 17:07:20 -0700 (PDT)
Received: from kitterma-e6430.localnet (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id 683BDC400E6 for <dcrup@ietf.org>; Thu, 22 Jun 2017 19:07:19 -0500 (CDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=201409; t=1498176439; bh=mwtwRvqIfH2lQ7OL5MMFcNzod+AyFPgNdF6t8/Gchp8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=lxgT7cOhOfBlpMF6+joh9I0XFLNwJMO6b9QfiTWlJDnLhmRZK0K4URoWTrMmqzUhX V82Qvwymm0E+QRx0oZx7RrLFDokD26uh7PoT4KeJezuHR1ATHr+C1+Ly9JdJ7rjRMt HTARFaSKqJSIDj/PDOT/JMfEeh32OddsKF3TrqhM=
From: Scott Kitterman <sklist@kitterman.com>
To: dcrup@ietf.org
Date: Thu, 22 Jun 2017 20:07:18 -0400
Message-ID: <2322507.4QhTyLSsXE@kitterma-e6430>
User-Agent: KMail/4.13.3 (Linux/3.13.0-119-generic; KDE/4.13.3; x86_64; ; )
In-Reply-To: <CAMm+LwgcVbOxmd_BZXY=V0H3w5zZnsWYxvyZ1mM6H9vQL24Z9g@mail.gmail.com>
References: <2793611.63lxTaCm4r@kitterma-e6430> <29347FB0-BFF6-42C4-B489-302342F6F2C0@blighty.com> <CAMm+LwgcVbOxmd_BZXY=V0H3w5zZnsWYxvyZ1mM6H9vQL24Z9g@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/aYTPn494PqJk2nwsftwbixYDIXk>
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 00:07:23 -0000
On Thursday, June 22, 2017 08:01:28 PM Phillip Hallam-Baker wrote: > On Thu, Jun 22, 2017 at 7:51 PM, Steve Atkins <steve@blighty.com> wrote: > > (and maybe be specific about what embedded whitespace means) > > > > These all seem good features.. > > > > I'm reminded of the $1$... style password hashes. Immediately recognizable > > in > > general, but including enough embedded information that you know which > > spec to follow. > > The other thing I would like is the ability to truncate fingerprints to > arbitrary lengths by truncating the string specifying the fingerprint. In > all but a few applications, a fingerprint with a workfactor of 2^118 is > sufficient to prevent most attacks. That is 25 characters in my proposal > (since there is a one byte algorithm identifier prefix). > > There are also some hacks that can be used for compressing the fingerprint > but I don't think these would be relevant here. I'm probably just grumpy because it's been a long day in a long week, but if you are going to not answer my question and go off in a completely different direction (in case you missed it, my question was about what's in the draft now, not an invitation to imagine what should be in the draft), would you please at least start your own thread so others are less likely to assume I already got my answer somewhere in what seems likely to be a long thread spiraling off into some new ocean that wants boiling? Thanks, Scott K
- [Dcrup] Hashed Key Records Scott Kitterman
- Re: [Dcrup] Hashed Key Records Phillip Hallam-Baker
- Re: [Dcrup] Hashed Key Records Steve Atkins
- Re: [Dcrup] Hashed Key Records Phillip Hallam-Baker
- Re: [Dcrup] Hashed Key Records Scott Kitterman
- Re: [Dcrup] Hashed Key Records Phillip Hallam-Baker
- Re: [Dcrup] Hashed Key Records John Levine
- Re: [Dcrup] Hashed Key Records Scott Kitterman
- Re: [Dcrup] Hashed Key Records denis bider
- Re: [Dcrup] Hashed Key Records Salz, Rich
- Re: [Dcrup] Hashed Key Records in draft-ietf-dcru… John Levine
- Re: [Dcrup] Hashed Key Records in draft-ietf-dcru… Salz, Rich
- Re: [Dcrup] Hashed Key Records in draft-ietf-dcru… denis bider