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.

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

go: partial implementation of CTv2 #1

Closed
wants to merge 5 commits into from

Conversation

daviddrysdale
Copy link
Contributor

(cloned from google/certificate-transparency#1346)

The first 2 commits (in go/tls, go/asn1) are some encoding library fixes/tests that turned up along the way.

The final 3 commits are the CTv2 work:

all the types from the draft RFC
those parts of CMS that are needed for precerts
the beginnings of a Log client (still incomplete and lacking in tests).

daviddrysdale and others added 5 commits December 12, 2016 09:33
Some TLS types have size fields like:

  opaque nonEmptyType<2..4>
  nonEmptyType values<0..8>

where the outer holder can explicitly be empty, but the
element type is always >0 in size.  Add a test case to
check that this is processed correctly.
To allow for SET OF ANY / SEQUENCE OF ANY, don't check the
element type tags for []asn1.RawValue.
 - Go types for all TLS types
 - Go types for all JSON request/response structures
 - JSON encoding methods for TransItem type
@daviddrysdale
Copy link
Contributor Author

This is based on draft-19 and so is now quite out-of-date.

@daviddrysdale daviddrysdale deleted the ct-v2 branch March 14, 2019 13:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant