Add a new "LintConfig" item to the CA's config, which can point to a zlint configuration toml file. This allows lints to be configured, e.g. to control the number of rounds of factorization performed by the Fermat factorization lint. Leverage this new config to create a new custom zlint which calls out to a configured pkilint API endpoint. In config-next integration tests, configure the lint to point at a new pkilint docker container. This approach has three nice forward-looking features: we now have the ability to configure any of our lints; it's easy to expand this mechanism to lint CRLs when the pkilint API has support for that; and it's easy to enable this new lint if we decide to stand up a pkilint container in our production environment. No production configuration changes are necessary at this time. Fixes https://github.com/letsencrypt/boulder/issues/7430 |
||
---|---|---|
.. | ||
main.go |