orangepizza 5678a62fe0 currectly triggers BadSignatureAlgorithmProblem at JWS parse time (#492) ... Pebble didn't have badSignatureAlgorithm error, while RFC8555 section 6.2 mandates it. jws parse time check for bad algorithm is needed because same as jose.parsesigned refuese to parse without algolist(which is good thing) so error already thrown at that time and we need to catch this type of error there. see related boulder PR https://github.com/letsencrypt/boulder/pull/8091 --------- Co-authored-by: Aaron Gable <aaron@aarongable.com>		2025-05-07 12:08:05 -04:00
..
common.go	Add support for ACME Profiles (#473)	2024-08-22 08:57:20 -07:00
problems.go	currectly triggers BadSignatureAlgorithmProblem at JWS parse time (#492)	2025-05-07 12:08:05 -04:00