Reject empty signatures in ProofVerifierChromium::VerifyProof
QuicCryptoClientHandshaker checks that signatures aren't empty, so we should never hit this case in production. In case something goes wrong at the upper layer, it's nice to have a belt-and-suspenders approach and since an empty signature is obviously wrong, it should be rejected. Change-Id: Id704bb9b469b6bc831f0a629be1824461617d883 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2243835Reviewed-by:David Schinazi <dschinazi@chromium.org> Commit-Queue: David Schinazi <dschinazi@chromium.org> Auto-Submit: Nick Harper <nharper@chromium.org> Cr-Commit-Position: refs/heads/master@{#778043}
Showing
Please register or sign in to comment