letsencrypt / pebble / 14888055256

6%

master: 8%

Build Type

push

github

Committed by web-flow

Commit Message

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>

Run Details

0 of 30 new or added lines in 3 files covered. (0.0%)

52 existing lines in 2 files now uncovered.

270 of 4402 relevant lines covered (6.13%)

0.29 hits per line