| Age | Commit message (Collapse) | Author |
|---|
|
|
|
cert-spec: specify unit for EXPIRATION_DATE
See merge request tpo/core/torspec!147
|
|
The unit for the EXPIRATION_DATE field in the Rsa->Ed25519
cross-certificates is HOURS after the epoch.
This however, is not mentioned in the specification so far, thereby
fixing it.
|
|
I personally had a hard time implementing the signature validation in Ed25519
certificates, as I have misinterpreted it as signing only the first 64 bytes.
I hope that this patch puts more clearance into the material.
|
|
|
|
There were extraneous entries in the lists of signed key types:
these values describe the type of the key being signed (eg, ed25519
or RSA), not the type of the certificate.
Further, clarify Tor bug 40124, so that people know to expect
incorrect cert key types on older signing->link certs.
|
|
I believe it was an error to use "4" for this value, but the error
has been enshrined in implementation.
|
|
The clear standard is trailing "." after each numeric section. This fixes
the small handful of outliers. This makes it easy to convert these headers
to common markup formats, for example:
http://hyperpolyglot.org/lightweight-markup
|
|
This is one small step towards making these a standard, parsable format.
|
|
|
|
Pointed out by inkylatenoth in:
https://lists.torproject.org/pipermail/tor-dev/2017-October/012527.html
Fixes ticket #24544.
|
|
|
|
|
|
Signed-off-by: David Goulet <dgoulet@torproject.org>
|
|
|
|
|
