Opened 6 years ago

Closed 5 years ago

#174 closed defect (fixed)

Remove use of `digitally-signed`?

Reported by: rlb@… Owned by: eranm@…
Priority: major Milestone: review
Component: rfc6962-bis Version:
Severity: - Keywords:
Cc:

Description

TLS 1.3 removes the digitally-signed construct in favor of just describing the
encoding of the signature directly, and describing what is signed in prose. For
example:

`
RFC 5246

struct {

digitally-signed struct {

opaque handshake_messages[handshake_messages_length];

}

} CertificateVerify?;

draft-ietf-tls-tls13

struct {

SignatureScheme? algorithm;
opaque signature<0..216-1>;

} CertificateVerify?;

`

If we were to follow suit here, it could simplify the description and
implementation of SCT and STH structs, as well as avoiding any appearance of
backward references.

Change History (5)

comment:1 Changed 6 years ago by rlb@…

Actually, since the signature scheme for the log is fixed, we can save 2 octets here by omitting the SignatureScheme that would otherwise be included in the digitally-signed -- as long as we're willing to require clients to remember which signature scheme goes with a given log_id. But we're already requiring them to remember the log's public key, so this doesn't seem like a huge burden.

comment:2 Changed 6 years ago by rob.stradling@…

  • Component changed from client-behavior to to-be-decided

comment:3 Changed 5 years ago by eranm@…

  • Component changed from to-be-decided to rfc6962-bis
  • Owner changed from draft-ietf-trans-rfc6962-bis@… to eranm@…
  • Status changed from new to assigned

comment:5 Changed 5 years ago by melinda.shore@…

  • Resolution set to fixed
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.