mirror of
https://github.com/mauriceboe/TREK.git
synced 2026-11-13 07:40:59 +00:00
3ca73d432b
Registration now goes through a registration dialect module: the paths of the challenge and the registration, the bytes scrypt runs over and the body and headers of the request. Each stable release will carry the dialect the TREK services issuer writes for it; until the first such release the module speaks the original registration, so nothing changes on the wire. An issuer that no longer takes the release's dialect answers 410. TREK then says so once per process, waits a day (or what Retry-After asks) and keeps searching through the shared pool. The issuer client only lets a dialect register at the issuer's own paths, with X-TREK-* headers that are not the gate's and a body of registration size. Renewal needs no dialect, and an expired key may now be renewed for a year instead of 30 days, the same period the issuer allows, so an installation that was offline for long comes back without an update. The key format ignores the new optional dialect claim; the shared vectors gain one key that carries it.