David Benjamin
d4864a6c40
Since libpki's serial number parser is itself sometimes permissive, it would be prudent for us to ensure all accepted serial numbers are representable in OCSP and CRL. This isn't critical because the real factor is whether the caller treats revocation as hardfail or not. This also fixes a bug where OCSPParseCertificate forgot to pass parse_options anywhere. In reality, this is all just just downstream of libpki handling serial numbers badly. https://crbug.com/533048005 tracks fixing this. Fixed: 518241439 Change-Id: Id73102bfc56d8c27ec08b1f76c411bdee3ab0551 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/98647 Presubmit-BoringSSL-Verified: boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Matt Mueller <mattm@google.com> Commit-Queue: Matt Mueller <mattm@google.com> Auto-Submit: David Benjamin <davidben@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.