Daniel McCarney

> I feel like we had a more specific discussion about this issue but cannot find it now I think you're thinking of https://github.com/rustls/rustls/pull/1921, which did propose adding a `rustls`...

> is there still anything from this PR that we should consider for merging? I don't think so, it seems to me that https://github.com/rustls/rustls-platform-verifier/pull/136 picked up everything we want. I...

> I'm not sure what's happening on the Windows side yet. Interestingly regenerating the expired root/intermediate _also_ fixed the Windows build task. I notice all the failures are related to...

> I'm slightly concerned about the root cause of seeing Ok(()) in the test output 😓. Agreed - my thought process here was that we should investigate this deeper but...

> Did you want to discuss that in this PR WFM! I think there's two topics: 1. whether it's worth maintaining `Cargo.lock` updates for compatible updates. We do it in...

> Should we also disable this for github-actions? These seem infrequent enough that I was OK leaving it on, but happy to revisit.

:wave: I haven't gone deep on the MS-WCCE spec or the required PKCS#10 attribute changes, but here are some initial thoughts. At one point I had ambitions of reworking the...

> Yeah, how do you feel about this revised plan, then? This sounds great to me. @est31 Do you have any reservations here? > taking ideas and code, where applicable,...

Thanks! Sorry I didn't get a chance to take a look at this before it merged. I reviewed the diff that landed and it looks good to me.

Let me start by sketching out the workflow I'd expect to see here. Client side: * Client generates key pair w/ `KeyPair::generate()` or another fn as appropriate. * Client generates...