Sam Clark

Hi @fy2462, Looking into this is still something we'd like to do, but we haven't gotten to it yet. After we investigate this further we'll let you know. Thanks!

Just a comment in general: currently, I'm not sure if there's a way to force s2n-tls to allocate additional memory after the handshake. I just wanted to bring up a...

Resolved by https://github.com/aws/s2n-tls/pull/3552

Hi @mxinden, it appears that even after the https://github.com/mozilla/neqo/pull/1837 fix, the neqo client and s2n-quic server still fail the resumption test. From https://github.com/mozilla/neqo/pull/1857#issuecomment-2077536804: ``` Failed Interop Tests neqo-latest vs. s2n-quic:...

We agree that adding an integration test for schannel would be beneficial. However, I think we can only run schannel on windows. This is an issue because our integration tests...

Thanks @bkmgit. As @dougch mentioned, we currently aren't testing s390x in our CI, so we can't guarantee support for this platform. We're happy to accept PRs that add support, though.

Unfortunately this change impacts the sidetrail proofs. When I attempted this it increased sidetrail's runtime by a lot. It might be difficult to implement this and work around all of...

To resolve this it might make sense for us to just update the default certificate chain to one that doesn't use SHA1.

High and medium priority labels before 2022 have been purged with the following script: https://gist.github.com/goatgoose/05ae12b51a4739869323a5b61e54c1c7 ``` ❯ ./purge_old_labels.sh Removing priority/high, labels: Removing priority/medium labels: https://github.com/aws/s2n-tls/issues/1634 1634: Protocol version helper functions...

We should also remove low priority from old issues.