microsoft / msquic

Cross-platform, C implementation of the IETF QUIC protocol, exposed to C, C++, C# and Rust.
MIT License
4.02k stars 530 forks source link

More Comprehensive Certificate Testing #1172

Open nibanks opened 3 years ago

nibanks commented 3 years ago

Describe the feature you'd like supported

We support a number of scenarios related to certificates (and will have more coming with client certs in the queue) but we have minimal testing for these. We should add more positive and negative test cases in these areas.

How do different error codes get exposed to the app? Might need core work around exposing individual error codes (might be worth a separate task).

anrossi commented 2 years ago

Since the above are not in any particular priority, I'm going to list the top-level bullets in priority order

  1. Specific look-up mechanisms (hash, principal name, different stores, etc.)
  2. More coverage of the cert callback mechanism (at QUIC layer)
  3. Specific invalid certificate failures (expired, wrong EKU, etc.)
  4. Revocation checking