Lily Chen
9b684de239
Add the missing check that the MTCProof's extensions field is a well-formed list of MTCLogEntryExtension structures in strictly ascending order by type, as required by section 5.2.1. Previously the field was hashed wholesale as opaque bytes without being parsed. No extension types are defined, so well-formed extensions are otherwise still ignored. Bug: 571178555 Change-Id: Ib25e7318ad9c27a4af5c972f34f93f3f6a6a6964 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/104509 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: Lily Chen <chlily@google.com>
Pre-generated files
This directory contains a number of pre-generated build artifacts. To simplify downstream builds, they are checked into the repository, rather than dynamically generated as part of the build.
When developing on BoringSSL, if any inputs to these files are modified, callers must run the following command to update the generated files:
go run ./util/pregenerate
To check that files are up-to-date without updating files, run:
go run ./util/pregenerate -check
This is run on CI to ensure the generated files remain up-to-date.
To speed up local iteration, the tool accepts additional arguments to filter the
files generated. For example, if editing aesni-x86_64.pl, this
command will only update files with "aesni-x86_64" as a substring.
go run ./util/pregenerate aesni-x86_64
For convenience, all files in this directory, including this README, are managed by the tool. This means the whole directory may be deleted and regenerated from scratch at any time.