Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Allow both v1 and v2 SCTs to be included in Expect-CT reports #358

Closed
estark37 opened this issue Jun 19, 2017 · 0 comments
Closed

Allow both v1 and v2 SCTs to be included in Expect-CT reports #358

estark37 opened this issue Jun 19, 2017 · 0 comments
Assignees
@estark37
Labels
expect-ct

Comments

@estark37
Copy link
Contributor

To support both 6962 and 6962-bis clients, we should allow Expect-CT reports to contain both v1 and v2 SCTs. One way to do that is include SCTs as a JSON object:

version: 1 / 2,
serialized_sct: <base64-encoded serialized SignedCertificateTimestamp from 6962> / <base64-encoded serialized TransItem struct from 6962-bis>
@estark37 estark37 self-assigned this Jun 19, 2017
estark37 added a commit that referenced this issue Jun 19, 2017
@estark37
Expect-CT: Support both RFC6962 and 6962-bis for serialized SCTs
20c5cfd 
The Expect-CT report format now allows either v1 or v2 SCTs to be included in
the report. A "version" key for each SCT indicates how the report server should
interpret them.

See issue #358
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@estark37 estark37

Labels
expect-ct
Milestone
No milestone
Development

No branches or pull requests
1 participant
@estark37