diff --git a/tool/bls12381_go_vectors.go b/tool/bls12381_go_vectors.go index 7209c60..9213693 100644 --- a/tool/bls12381_go_vectors.go +++ b/tool/bls12381_go_vectors.go @@ -36,14 +36,15 @@ // the scheme of Quicknet) under keys drawn from the seed, and the verdict // of its Verify on each and on edited copies. // -// The seed is fixed: the output is the same on every run. Run it from a -// scratch module that requires the reference implementation at spec-v0.11 -// (a module scratch whose go.mod has require g.activething.com/go/DateKeys -// v0.0.0 and replace g.activething.com/go/DateKeys => an export of that tag, -// with its go.sum, and GOFLAGS=-mod=mod), copied into it, passing the frozen -// file of datekeys-ts: +// The seed is fixed: the output is the same on every run. Run it in the +// module of the reference implementation, which it imports, without changing +// anything there, from the datekeys-go next to this repository: at the tag +// spec-v0.11 or at the draft v0.12, whose packages that it uses are the +// same, and so is the output. // -// go run bls12381_go_vectors.go path/to/bls12381-vectors.json > bls12381_vectors.json +// cd ../datekeys-go && go run ../datekeys-dart/tool/bls12381_go_vectors.go \ +// ../datekeys-ts/src/lib/dkc/testing/bls12381-vectors.json \ +// > ../datekeys-dart/test/vectors/bls12381_vectors.json package main import ( diff --git a/tool/ibe_go_vectors.go b/tool/ibe_go_vectors.go index b632cca..ebad19f 100644 --- a/tool/ibe_go_vectors.go +++ b/tool/ibe_go_vectors.go @@ -31,14 +31,15 @@ // kyber's exported tags, and checks them on every fixture against what // tlock.TimeUnlock unwraps and against U = r·G2. A mismatch panics. // -// Run it from a scratch module that requires the reference implementation at -// spec-v0.11 (a module scratch whose go.mod has require -// g.activething.com/go/DateKeys v0.0.0 and replace -// g.activething.com/go/DateKeys => an export of that tag, with its go.sum, -// and GOFLAGS=-mod=mod), copied into it, passing the directory of the -// official fixtures and the frozen file of datekeys-ts: +// Run it in the module of the reference implementation, which it imports, +// without changing anything there, from the datekeys-go next to this +// repository: at the tag spec-v0.11 or at the draft v0.12, whose packages +// that it uses are the same, and so is the output. // -// go run ibe_go_vectors.go path/to/testdata/fixtures path/to/ibe-vectors.json > ibe_vectors.json +// cd ../datekeys-go && go run ../datekeys-dart/tool/ibe_go_vectors.go \ +// ../datekeys-dart/testdata/fixtures \ +// ../datekeys-ts/src/lib/dkc/testing/ibe-vectors.json \ +// > ../datekeys-dart/test/vectors/ibe_vectors.json package main import ( diff --git a/tool/release_go_vectors.go b/tool/release_go_vectors.go index ffb2999..d98d894 100644 --- a/tool/release_go_vectors.go +++ b/tool/release_go_vectors.go @@ -19,13 +19,13 @@ // Each verdict is "ok", with the file key for an unwrap, or the normative // code and the text of the error of Go. // -// Run it from a scratch module that requires the reference implementation at -// spec-v0.11 (a module scratch whose go.mod has require -// g.activething.com/go/DateKeys v0.0.0 and replace -// g.activething.com/go/DateKeys => an export of that tag, with its go.sum, -// and GOFLAGS=-mod=mod), copied into it, passing the testdata directory: +// Run it in the module of the reference implementation, which it imports, +// without changing anything there, from the datekeys-go next to this +// repository: at the tag spec-v0.11 or at the draft v0.12, whose packages +// that it uses are the same, and so is the output. // -// go run release_go_vectors.go path/to/testdata > release_vectors.json +// cd ../datekeys-go && go run ../datekeys-dart/tool/release_go_vectors.go \ +// ../datekeys-dart/testdata > ../datekeys-dart/test/vectors/release_vectors.json package main import ( diff --git a/tool/tlock_go_vectors.go b/tool/tlock_go_vectors.go index 97d51fd..c90d810 100644 --- a/tool/tlock_go_vectors.go +++ b/tool/tlock_go_vectors.go @@ -21,14 +21,14 @@ // H2, H3 and H4 are unexported in kyber; they are restated with its tags, as // in tool/ibe_go_vectors.go, and the decryptions above check them. // -// Run it from a scratch module that requires the reference implementation at -// spec-v0.11 (a module scratch whose go.mod has require -// g.activething.com/go/DateKeys v0.0.0 and replace -// g.activething.com/go/DateKeys => an export of that tag, with its go.sum, -// and GOFLAGS=-mod=mod), copied into it, passing the frozen file of -// datekeys-ts: +// Run it in the module of the reference implementation, which it imports, +// without changing anything there, from the datekeys-go next to this +// repository: at the tag spec-v0.11 or at the draft v0.12, whose packages +// that it uses are the same, and so is the output. // -// go run tlock_go_vectors.go path/to/tlock-vectors.json > tlock_vectors.json +// cd ../datekeys-go && go run ../datekeys-dart/tool/tlock_go_vectors.go \ +// ../datekeys-ts/src/lib/dkc/testing/tlock-vectors.json \ +// > ../datekeys-dart/test/vectors/tlock_vectors.json package main import (