[noise] Test vector format update

Jake McGinty me at jake.su
Thu Jun 15 10:05:59 PDT 2017


Currently, this format doesn’t allow for testing of multiple PSKs which is
allowed in the spec. Instead of

{ …
  “protocol_name”: “Noise_XXpsk0_25519_AESGCM_SHA256”,
  “init_psk”: “hex string”
 … }

It might be more flexible to use either

{ … 
  “protocol_name”: “Noise_XXpsk0+psk1_25519_AESGCM_SHA256”,
  “init_psks”: [“hex string”, “hex string”]
… }

if you clarify what the order means, or 

{ … 
  “protocol_name”: “Noise_XXpsk0+psk1_25519_AESGCM_SHA256”,
  “init_psks”: [{ position: 0, key: “hex string” }, { position: 1, key: “hex string” }]
… }


> On Jun 14, 2017, at 10:43 AM, Alex <alex at centromere.net> wrote:
> 
> In consultation with Rhys, the test vector format[0] has been updated.
> 
> Changes include:
> 
> * Removed semiephemerals
> * Removed SSKs
> * Removed the cipher/dh/hash keys
> * Added a "protocol_name" field
> * Re-purposed the "name" field so that it is a free-form description of
>  the test
> * Added introduction and other minor changes
> 
> I've generated fresh vectors[1] that take advantage of these formatting
> changes as well as the changes introduced in rev32.
> 
> -- 
> Alex
> 
> [0] https://github.com/noiseprotocol/noise_wiki/wiki/Test-vectors
> [1] https://raw.githubusercontent.com/centromere/cacophony/master/vectors/cacophony.txt
> _______________________________________________
> Noise mailing list
> Noise at moderncrypto.org
> https://moderncrypto.org/mailman/listinfo/noise



More information about the Noise mailing list