letsencrypt
/
boulder
mirror of https://github.com/letsencrypt/boulder.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
boulder/wfe2
History
orangepizza 5cc8a77ce3
wfe: Separately handle badSignature at JWS parse time (#8091) 
solve https://github.com/letsencrypt/boulder/issues/8088

RFC8555 6.2 requires badSignatureAlgorithm on unacceptable JWS signing
algorithm, but current boulder return malform:failed to parse jws error
instead

Its because this only checks about JWS protected header's signature
algorithm, current checkAlgorithm is while too late to catch parse time
error but not redundant, as it checks against a key and signed message

---------

Co-authored-by: Samantha Frank <hello@entropy.cat>
 		2025-04-08 15:45:06 -07: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
stats.go WFE: Count NewOrders which indicate replacement (#7416) 2024-04-08 12:32:45 -04:00
verify.go wfe: Separately handle badSignature at JWS parse time (#8091) 2025-04-08 15:45:06 -07:00
verify_test.go wfe: Separately handle badSignature at JWS parse time (#8091) 2025-04-08 15:45:06 -07:00
wfe.go core: Remove DnsNames from Order (#8108) 2025-04-08 15:17:18 -07:00
wfe_test.go core: Remove DnsNames from Order (#8108) 2025-04-08 15:17:18 -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.