New issue
Advanced search Search tips

Issue 634570 link

Starred by 5 users
Status: Untriaged
Owner: ----
Cc:
eranm@chromium.org
davidben@chromium.org
asymmetric@chromium.org
rsleevi@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug



Sign in to add a comment

Replace custom CT parsing with those of BoringSSL's CBB

Project Member Reported by rsleevi@chromium.org, Aug 5 2016 
Currently, the CT Structure Parsing (see https://cs.chromium.org/chromium/src/net/cert/ct_serialization.h?rcl=0&l=1 ) uses a series of internal helpers to read TLS encoded structures. We should just switch all this to use BoringSSL's ByteString/CBB

Comment 1 by davidben@chromium.org, Aug 5 2016 

Documentation here:
https://commondatastorage.googleapis.com/chromium-boringssl-docs/bytestring.h.html

Although I still need to write better docs on CBB as it's not entirely obvious. The last person who was recommended to use it found it confusing. //crypto/auto_cbb.h will likely also be helpful. (Eventually to be provided by some BoringSSL header.)
►

Sign in to add a comment