Opened 8 years ago

Closed 7 years ago

#5 closed defect (fixed)

Add extensions to STH

Reported by: eranm@… Owned by: rob.stradling@…
Priority: major Milestone: review
Component: rfc6962-bis Version:
Severity: - Keywords:
Cc: benl@…

Description

Migrated from https://code.google.com/p/certificate-transparency/issues/detail?id=28:

From benl: "Just as we allow for future expansion in SCTs, we should also allow for it in the STH."

Started addressing in https://codereview.appspot.com/68240043/

Change History (9)

comment:1 Changed 8 years ago by eranm@…

  • Resolution set to fixed
  • Status changed from new to closed

comment:2 Changed 8 years ago by eranm@…

  • Resolution fixed deleted
  • Status changed from closed to reopened

Check if we should increase STH version.

comment:3 Changed 8 years ago by benl@…

We (Rob and I) think the version should be increased.

comment:5 Changed 8 years ago by eranm@…

  • Resolution set to fixed
  • Status changed from reopened to closed

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

  • Resolution fixed deleted
  • Status changed from closed to reopened

We actually rolled this change back in https://github.com/google/certificate-transparency-rfcs/commit/c7fa413ae0bb04c233c3825e00578ae78ad371b3. IIRC, our thinking was that it wasn't worth bumping the STH version solely to add an extensions field for which we haven't yet thought of any uses.

However, since ticket #106 just bumped the STH version to v2 (again!), it makes sense to re-introduce the STH extensions field now.

comment:7 Changed 7 years ago by rob.stradling@…

  • Owner changed from eranm@… to rob.stradling@…
  • Status changed from reopened to new

comment:8 Changed 7 years ago by rob.stradling@…

  • Milestone set to review
  • Status changed from new to assigned

comment:9 Changed 7 years ago by melinda.shore@…

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