Re: [Cfrg] KCipher-2

Joachim Strömbergson <> Fri, 25 January 2013 09:09 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CA71521F880E for <>; Fri, 25 Jan 2013 01:09:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0.084
X-Spam-Status: No, score=0.084 tagged_above=-999 required=5 tests=[BAYES_50=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1, SARE_URI_DIGITS4=0.415, URI_HEX=0.368]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Vr9ufhyrgaNF for <>; Fri, 25 Jan 2013 01:09:27 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id D835521F865D for <>; Fri, 25 Jan 2013 01:09:26 -0800 (PST)
Received: from ([]:38207 helo=tunnis.local) by with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from <>) id 1TyfHn-0009lo-Bi for; Fri, 25 Jan 2013 10:09:23 +0100
Message-ID: <>
Date: Fri, 25 Jan 2013 10:09:22 +0100
From: Joachim Strömbergson <>
Organization: Kryptologik
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
References: <015c01cdd43a$f18f3b60$d4adb220$> <>
In-Reply-To: <>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname -
X-AntiAbuse: Original Domain -
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain -
X-Get-Message-Sender-Via: authenticated_id:
Subject: Re: [Cfrg] KCipher-2
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Crypto Forum Research Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 25 Jan 2013 09:09:27 -0000


On 2012-12-07 20:00 , Jon Callas wrote:
> Yes, put the table in. It's a long-standing frustration of mine that
> crypto documents seem to think that part of the fun is to guess about
> implementation until you finally get it right. A sort of
> gameification, I suppose, that makes a spec a choose-your-own
> adventure. This gets boring, fast. The vast majority of us
> implementors want to get it done, fast and accurate. Anything that
> helps that is a Good Thing.

(Slight OT)


At the absolute minimum add test vectors. Adding a clean, well 
documented reference implementation that uses std types (stdint.h) is 
makes it even better and if you also include internal states during 
processing of at least one test vector you make the implementers life 
_much_ easier.

The siphash specification includes good test vectors and a great walk 
through that made the implementation pretty comfortable. The C reference 
code is, shall we say, terse. Also it really helps if one defines 
operation symbols before using them in the spec...

Med vänlig hälsning, Yours

Joachim Strömbergson - Alltid i harmonisk svängning.