From e398c4d1ec05c9aa91aa196a489682968f6318f1 Mon Sep 17 00:00:00 2001 From: Aaron Gable Date: Tue, 6 Aug 2024 09:23:06 -0700 Subject: [PATCH] Clearer error message when goodkey fails unexpectedly (#7642) This will prevent users from believing their key is at fault when the actual error is between Boulder and the database. Fixes https://github.com/letsencrypt/boulder/issues/7624 --- wfe2/verify.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/wfe2/verify.go b/wfe2/verify.go index 665048f15..cb948e486 100644 --- a/wfe2/verify.go +++ b/wfe2/verify.go @@ -722,7 +722,7 @@ func (wfe *WebFrontEndImpl) validSelfAuthenticatedPOST( wfe.stats.joseErrorCount.With(prometheus.Labels{"type": "JWKRejectedByGoodKey"}).Inc() return nil, nil, probs.BadPublicKey(err.Error()) } - return nil, nil, probs.ServerInternal("error checking key quality") + return nil, nil, probs.ServerInternal("internal error while checking JWK") } return payload, pubKey, nil