You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
If a tls::Session impl returns Poll::Pending "spuriously" (self-wake and return Pending), without calling context methods to update the crypto state, s2n-quic won't gracefully defer until the Session impl is ready, causing debug assertions to be hit and possibly other state expectation violations.
Solution:
s2n-quic's internal poll_crypto API(s) need to be modified to support Pending being returned from tls::Session even if a packet should otherwise be enough to move forward.
Does this change what s2n-quic sends over the wire? no
Does this change any public APIs? no
Requirements / Acceptance Criteria:
RFC links: n/a
Related Issues: n/a
Will the Usage Guide or other documentation need to be updated? n/a
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:
If a tls::Session impl returns Poll::Pending "spuriously" (self-wake and return Pending), without calling context methods to update the crypto state, s2n-quic won't gracefully defer until the Session impl is ready, causing debug assertions to be hit and possibly other state expectation violations.
Solution:
s2n-quic's internal poll_crypto API(s) need to be modified to support Pending being returned from tls::Session even if a packet should otherwise be enough to move forward.
Requirements / Acceptance Criteria:
This diff should not cause any test failures:
Out of scope:
The text was updated successfully, but these errors were encountered: