On Mon, Feb 12, 2018 at 02:57:06PM -0500, Jeffrey Walton wrote:
> On Mon, Feb 12, 2018 at 2:19 PM, Eric Biggers <ebigg...@google.com> wrote:
> > Hi all,
> > On Fri, Feb 09, 2018 at 07:07:01PM -0500, Jeffrey Walton wrote:
> >> > Hi Jeffrey,
> >> >
> >> > I see you wrote the SPECK implementation in Crypto++, and you are
> >> > treating the
> >> > words as big endian.
> >> >
> >> > Do you have a reference for this being the "correct" order?
> >> > Unfortunately the
> >> > authors of the cipher failed to mention the byte order in their paper.
> >> > And they
> >> > gave the test vectors as words, so the test vectors don't clarify it
> >> > either.
> >> >
> >> > I had assumed little endian words, but now I am having second
> >> > thoughts... And
> >> > to confuse things further, it seems that some implementations (including
> >> > the
> >> > authors own implementation for the SUPERCOP benchmark toolkit ) even
> >> > consider
> >> > the words themselves in the order (y, x) rather than the more intuitive
> >> > (x, y).
> >> >
> >> > 
> >> > https://github.com/iadgov/simon-speck-supercop/blob/master/crypto_stream/speck128128ctr/ref/stream.c
> >> >
> >> > In fact, even the reference code from the paper treats pt as y and
> >> > pt as
> >> > x, where 'pt' is a u64 array -- although that being said, it's not shown
> >> > how the
> >> > actual bytes should be translated to/from those u64 arrays.
> >> >
> >> > I'd really like to avoid people having to add additional versions of
> >> > SPECK later
> >> > for the different byte and word orders...
> >> Hi Eric,
> >> Yeah, this was a point of confusion for us as well. After the sidebar
> >> conversations I am wondering about the correctness of Crypto++
> >> implementation.
> > We've received another response from one of the Speck creators (Louis
> > Wingers)
> > that (to summarize) the intended byte order is little endian, and the
> > intended
> > word order is (y, x), i.e. 'y' is at a lower memory address than 'x'. Or
> > equivalently: the test vectors given in the original paper need to be read
> > as
> > byte arrays from *right-to-left*.
> > (y, x) is not the intuitive order, but it's not a huge deal. The more
> > important
> > thing is that we don't end up with multiple implementations with different
> > byte
> > and/or word orders.
> > So, barring any additional confusion, I'll send a revised version of this
> > patchset that flips the word order. Jeff would need to flip both the byte
> > and
> > word orders in his implementation in Crypto++ as well.
> Thanks Eric.
> Yeah, the (y,x) explains a lot of the confusion, and explains the
> modification I needed in my GitHub clone of the IAD Team's SUPERCOP to
> arrive at test vector results. My clone is available at
> So let me ask you... Given the Speck-128(128) test vector from Appendix C:
> Key: 0f0e0d0c0b0a0908 0706050403020100
> Plaintext: 6c61766975716520 7469206564616d20
> Ciphertext: a65d985179783265 7860fedf5c570d18
> Will the Linux implementation arrive at the published result, or will
> it arrive at a different result? I guess what I am asking, where is
> the presentation detail going to be handled?
> A related question is, will the kernel be parsing just the key as
> (y,x), or will all parameters be handled as (y,x)? At this point I
> believe it only needs to apply to the key but I did not investigate
> the word swapping in detail because I was chasing the test vector.
The kernel implementation has to operate on byte arrays. But the test vectors
in the original paper are given as *words* in the order (x, y) and likewise for
the key (i.e. the rightmost word shown becomes the first round key). But based
on the clarifications from the Speck team, the actual byte arrays that
correspond to the Speck-128/128 test vector would be:
const uint8_t key =
const uint8_t plaintext =
const uint8_t ciphertext =
So equivalently, if we consider the printed test vectors as just listing the
bytes (ignoring the whitespace between the words), then they are backwards.
That applies to all 3 parts (Key, Plaintext, and Ciphertext).
Note that my patch 1/5 adds the Speck test vectors to testmgr.h so that they are
hooked into the Linux kernel's crypto self-tests, so on appropriately-configured
kernels it will be automatically verified that the implementation matches the
test vectors. The ones in the current version of the patchset have the "wrong"
word order though, so I will need to send out a new version with the correct
implementation and test vectors.