aws/s2n-quic

Session resumption improvements

Opened this issue · 3 comments

maddeleine commented

Security issue notifications

If you discover a potential security issue in s2n-quic we ask that you notify
AWS Security via our vulnerability reporting page. Please do not create a public github issue.

Problem:

There are a few ways that we can improve the initial session resumption feature to make it more user-friendly:

  • Enabling resumption when s2n-quic is using rustls
  • Adding an event that indicates
    • when session tickets are received post-handshake on the client, as this varies per quic implementation.
    • when a session ticket is sent for a handshake on the client
    • when a session ticket is accepted/rejected on the client
    • when a session ticket is sent by the server
    • when a session ticket is accepted/rejected on the server
stranzhay commented

hi @maddeleine just wondering about timeline for s2n-quic rustls resumption, days/weeks/months. we are currently trying to reconfigure our setup to use s2n-tls instead of the rustls its currently using but with ed25519 keys. s2n-tls does not support ed25519 atm so trying to judge where our efforts should be at this time.

maddeleine commented

We don't have a timeline for resumption with rustls in s2n-quic yet. It's definitely something we want to add, but not something we have on our roadmap right now.

stranzhay commented

ok thank you for quick response