|
|
|
|
module g.activething.com/go/DateKeys
|
Initial implementation of the DateKeys Protocol v0.8.1
Reference implementation in Go, built from the implementation plan
(milestones M0 to M5): datekey, profile, provider, codec, agewrap,
extension, capsule, accesskey, the datekeys CLI, official vectors and
fixtures, the mutation corpus, fuzz targets, interop and live tests,
CI workflows, traceability and policy documents.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2 weeks ago
|
|
|
|
|
|
|
|
go 1.26.8
|
Initial implementation of the DateKeys Protocol v0.8.1
Reference implementation in Go, built from the implementation plan
(milestones M0 to M5): datekey, profile, provider, codec, agewrap,
extension, capsule, accesskey, the datekeys CLI, official vectors and
fixtures, the mutation corpus, fuzz targets, interop and live tests,
CI workflows, traceability and policy documents.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2 weeks ago
|
|
|
|
|
|
|
|
require (
|
|
|
|
|
filippo.io/age v1.3.2
|
|
|
|
|
github.com/drand/drand/v2 v2.1.7
|
|
|
|
|
github.com/drand/kyber v1.3.2
|
Spec v0.8.2: corrections from the formal review
A formal review of the whole v0.8.2 text found it approvable after
these corrections, recorded in §76 ("Correcciones de la revisión
formal"):
- §27 no longer calls header_binding the authenticity of PUBLIC_HEADER:
it binds the header to the opened control, never authorship or date
(§55.1); the age MAC only protects against whoever lacks the file key.
- §63 steps 9 and 10: a network source (relay, Release API, cache) MUST
verify every response and gives ERR_RELEASE_UNAVAILABLE at step 9 when
none verifies; the step-10 codes are for a directly supplied release.
The reference already behaved so; TestReleaseFromANetworkSource pins
both paths.
- §54 and §72: registrations declare the objects and arrays where an
extension may appear, and a known extension out of place counts as
unknown there. The reference gains the optional extension.Placement
interface, used at steps 4, 9.a and 14.
- §63 step 11 fixes the GT serialization hashed by H2 (kilic/kyber order)
with the frozen vector H2(e(G1, G2))[:16] = cb87319f..., shared as
testdata/vectors/tlock_ibe.json; H2-H4 are cited to drand/kyber.
- Step 5 makes the SEALED_CONTROL read mandatory, step 15 names
ERR_HEADER_BINDING, §21 makes capsule_id 16 CSPRNG bytes a MUST, §76
is made accurate (four dk1.json vectors, the §36 time_only rule, two
cases rewritten against the texts that really existed), and editorial
fixes in §5, §36, §55.1, §69.1 and §77. §73 lists the three new
decisions.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2 weeks ago
|
|
|
github.com/drand/kyber-bls12381 v0.3.4
|
Initial implementation of the DateKeys Protocol v0.8.1
Reference implementation in Go, built from the implementation plan
(milestones M0 to M5): datekey, profile, provider, codec, agewrap,
extension, capsule, accesskey, the datekeys CLI, official vectors and
fixtures, the mutation corpus, fuzz targets, interop and live tests,
CI workflows, traceability and policy documents.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2 weeks ago
|
|
|
github.com/drand/tlock v1.2.0
|
|
|
|
|
golang.org/x/crypto v0.57.0
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
require (
|
|
|
|
|
filippo.io/hpke v0.4.0 // indirect
|
|
|
|
|
github.com/BurntSushi/toml v1.6.0 // indirect
|
|
|
|
|
github.com/kilic/bls12-381 v0.1.0 // indirect
|
|
|
|
|
github.com/nikkolasg/hexjson v0.1.0 // indirect
|
|
|
|
|
go.dedis.ch/fixbuf v1.0.3 // indirect
|
|
|
|
|
go.uber.org/multierr v1.11.0 // indirect
|
|
|
|
|
go.uber.org/zap v1.28.0 // indirect
|
|
|
|
|
golang.org/x/net v0.58.0 // indirect
|
|
|
|
|
golang.org/x/sys v0.48.0 // indirect
|
|
|
|
|
golang.org/x/text v0.42.0 // indirect
|
|
|
|
|
google.golang.org/genproto/googleapis/rpc v0.0.0-20260706201446-f0a921348800 // indirect
|
|
|
|
|
google.golang.org/grpc v1.84.0 // indirect
|
|
|
|
|
google.golang.org/protobuf v1.36.11 // indirect
|
|
|
|
|
gopkg.in/yaml.v3 v3.0.1 // indirect
|
|
|
|
|
)
|
