boulder/wfe2
Aaron Gable 74e914e8e7
Disallow affiliationChanged revocation reason (#6217)
The `affiliationChanged` revocation reason is only relevant
to certificates which contain Subject Identity Information.
As we only issue DV certificates, which cannot contain such
information, our certificates should not be able to be revoked
for this reason.

See https://groups.google.com/a/mozilla.org/g/dev-security-policy/c/m3-XPcVcJ9M
2022-07-07 10:45:36 -07:00
..
test Fix various WFE2 bugs. (#3292) 2017-12-19 13:13:29 -08:00
README.md Duplicate WFE to WFE2. (#2839) 2017-07-05 13:32:45 -07:00
cache.go Add account cache to WFE (#5855) 2021-12-15 11:10:23 -08:00
cache_test.go Add account cache to WFE (#5855) 2021-12-15 11:10:23 -08:00
prod_aia.go Fixup staticcheck and stylecheck, and violations thereof (#5897) 2022-01-20 16:22:30 -08:00
stale.go Unwrap SA Get[Pre]Certificate methods (#5588) 2021-08-19 15:43:48 -07:00
stale_test.go GRPC: Unwrap ra.DeactivateAuthorization (#5567) 2021-08-12 11:30:57 -07:00
stats.go Switch away from old style statsd metrics wrappers (#4606) 2019-12-18 11:08:25 -05:00
test_aia.go Remove wfe1 integration tests (#5840) 2021-12-10 12:40:22 -08:00
verify.go Remove special-casing of EC padding parse error (#6186) 2022-06-23 13:27:15 -07:00
verify_test.go Remove special-casing of EC padding parse error (#6186) 2022-06-23 13:27:15 -07:00
wfe.go Reduce redundant audit logging of CSR (#6113) 2022-05-16 14:33:33 -07:00
wfe_test.go Disallow affiliationChanged revocation reason (#6217) 2022-07-07 10:45:36 -07:00

README.md

WFE v2

The wfe2 package is copied from the wfe package in order to implement the "ACME v2" API. This design choice was made to facilitate a clean separation between v1 and v2 code and to support running a separate API process on a different port alongside the v1 API process.