From 0b52f555fa06e9c4098caf76933ec8f923182982 Mon Sep 17 00:00:00 2001 From: Rasmus Dahlberg Date: Mon, 2 Nov 2020 16:59:20 +0100 Subject: rephrased signature algorithm to signature scheme --- markup/api.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/markup/api.md b/markup/api.md index d21649f..45c6deb 100644 --- a/markup/api.md +++ b/markup/api.md @@ -21,12 +21,12 @@ A log is defined by the following immutable parameters: - Log identifier: `SHA256(public key)`, see RFC 6962 [§3.2](https://tools.ietf.org/html/rfc6962#section-3.2) - Public key: DER encoding of the key represented as `SubjectPublicKeyInfo` -- Supported signature algorithms: a list of signature algorithms that the +- Supported signature schemes: a list of signature schemes that the log recognizes. Possible values are defined in RFC 8446, [§4.2.3](https://tools.ietf.org/html/rfc8446#section-4.2.3). Submitters must use a signature algorithm that the log supports. -- Signature algorithm: the signature algorithm that the log uses to sign -tree heads and debug info statements. +- Signature scheme: the signature scheme that the log uses to sign tree heads +and debug info statements. - Maximum chain length: e.g., three means that we would reject submissions that were signed by a certificate chain of length four. - Base URL: where can this log be reached? E.g., example.com:1234/log -- cgit v1.2.3