Generation of test vectors

[armfazh]

It is re-based on top of #189 and #201 .

JSON test vectors for matching compatible implementations.

Example:

{
  "ciphersuite": "P256-SHA256-SSWU-RO-",
  "curve": "P256",
  "dst": "QUUX-V01-CS02",
  "field": {
    "m": "0x1",
    "p": "0xffffffff00000001000000000000000000000000ffffffffffffffffffffffff"
  },
  "hash": "sha256",
  "map": {
    "name": "SSWU",
    "sgn0": "sgn0_le"
  },
  "randomOracle": true,
  "vectors": [
    {
      "P": {
        "x": "0x8beb73a82ebeb6b400456f4da126aacbfa9b8049b71b250d2b7e4885b6b466bd",
        "y": "0x15826dc578f4fbc1ac5fc3f9e15da3ece18be914f332bce8ce5bf1371805d149"
      },
      "msg": ""
    },
 ]
}

[kwantam]

Nice! I will take a more careful look in the next few days.

To be clear: the JSON wouldn't go into the document, right? (Of course, we can provide test vector files to be downloaded and mechanically processed.)

So probably we will also want a script to turn the JSON structures into whatever format will actually go into the appendix of the document. (Or have I missed it, and that's already here?)

[armfazh]

To be clear: the JSON wouldn't go into the document, right?

No, only ascii. JSON files are intended to be available at an external repo.

So probably we will also want a script to turn the JSON structures into whatever format will actually go into the appendix of the document.

Now it supports both ascii and json formats.

[armfazh]

This branch has been rebased including the Python3 updates.
Should I also include in this PR the test vector (json/ascii) files?

[kwantam]

I know that I still need to review this. I'm sorry for the very long delay. I should have time this week.

Just to double check: The Sage9/Python3 version generates the same test vectors as the Sage8/Python2 version, right?

[armfazh]

The SHA512 suites for {curve/edwards}25519 are now included in Sage scripts.

[kwantam]

I rebased this on top of master because the diff interface was very confused :)

[kwantam]

Looks good to me. I re-ran test vector generation on my machine (sage9/python3) and got the same files back out. Just a few very small things.

I assume once #212 lands and we update the code to the new suites we'll generate new test vectors, but it doesn't hurt to have these in the repo history anyway, IMO.

[chris-wood]

I did a quick cursory scan -- looks good! (Riad having run them gives me confidence it's good to go.)