Joe Birr-Pixton

Hey @Wonshtrum, we'd like to release 0.23 next week, and have this PR in that release. Would you be happy for us (that is, @cpu and I) to take over...

> A lot of things going on in the final commit, but looks good in substance. Sorry, going to change my mind on this after working through the issues. I...

> I expected there might be client changes needed here or in #1785 to track the notion of a prediction-safe supported group, but it looks like neither branch considers that....

Yes, unfortunately I think any change to the default feature list is a breaking change :(

There's been no work on this as yet.

Thanks for keeping this updated with the latest measurements. Do you have an idea of whether these results would be reproducible by me? I guess it would, and doesn't really...

Currently we only support SCTs delivered by the TLS extension (this option was, in the end, not widely deployed in the ecosystem), not those embedded in certificates.

rustls currently only advertises PSS with: ``` /* RSASSA-PSS algorithms with public key OID rsaEncryption */ rsa_pss_rsae_sha256(0x0804), rsa_pss_rsae_sha384(0x0805), rsa_pss_rsae_sha512(0x0806), ``` and _not_: ``` /* RSASSA-PSS algorithms with public key OID...

> @ctz Are you saying that certificates which specify RSASSA-PSS in their SPKI are not supported by rustls? Correct. > The issue I have with using the rsaEncryption OID in...

Going to close this. While there are no technical reasons rustls cannot use `async fn` or `core::future::*` nowadays, that does not extend to being able to do IO. There is...