boulder/wfe2
Daniel McCarney fde145ab96
RA: implement stricter email validation. (#4574)
Prev. we weren't checking the domain portion of an email contact address
very strictly in the RA. This updates the PA to export a function that
can be used to validate the domain the same way we validate domain
portions of DNS type identifiers for issuance.

This also changes the RA to use the `invalidEmail` error type in more
places.

A new Go integration test is added that checks these errors end-to-end
for both account creation and account update.
2019-11-22 13:39:31 -05: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
stats.go Check EC field lengths in WFE2 (#4195) 2019-05-07 17:27:45 -07:00
verify.go wfe/wfe2: make JWS signature alg error msgs match reality (#4519) 2019-10-31 09:55:11 -04:00
verify_test.go wfe/wfe2: make JWS signature alg error msgs match reality (#4519) 2019-10-31 09:55:11 -04:00
wfe.go WFE/WFE2: Remove old authz/challenge support (#4486) 2019-10-17 10:19:04 -04:00
wfe_test.go RA: implement stricter email validation. (#4574) 2019-11-22 13:39:31 -05: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.