boulder/crl
Aaron Gable 63319d8cd0
crl-updater: duplicate shard 0 as shard NumShards (#7008)
When crl-updater produces a CRL with shard index 0, have it also produce
an identical CRL with shard index NumShards (e.g. 128). This is the
first step towards having it only produce shards numbered 1 through
NumShards, i.e. transition from using 0-indexing to 1-indexing.

We want to do this because various aspects of Golang and gRPC cannot
tell the difference between "this struct/message has no shard index set"
and "this struct/message has shard index 0 set".

Part of https://github.com/letsencrypt/boulder/issues/7007
2023-07-26 15:32:20 -07:00
..
checker Use zlint to check our CRLs (#6972) 2023-07-11 15:39:05 -07:00
crl_x509 Remove comment regarding upstreamed portion of crl_x509 (#6725) 2023-03-07 14:58:43 -08:00
storer Add grpc implementation tests to all services (#6782) 2023-03-31 09:52:26 -07:00
updater crl-updater: duplicate shard 0 as shard NumShards (#7008) 2023-07-26 15:32:20 -07:00
crl.go Streamline and test crl-updater errors and audit logs (#6382) 2022-09-14 16:41:28 -07:00
crl_test.go Streamline and test crl-updater errors and audit logs (#6382) 2022-09-14 16:41:28 -07:00