Have the crl-storer download the previous CRL from S3, parse it, and compare its number against the about-to-be-uploaded CRL. This is not an atomic operation, so it is not a 100% guarantee, but it is still a useful safety check to prevent accidentally uploading CRL shards whose CRL Numbers are not strictly increasing. Part of https://github.com/letsencrypt/boulder/issues/6456 |
||
|---|---|---|
| .. | ||
| main.go | ||