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:
We've chosen to merge the existing dc-quic offloading integration and get real performance data at a faster pace, rather than doing a larger refactor right now. See this comment for where this feature currently stands. Therefore, we will need to improve the integration code so that offloaded and non-offloaded dc-quic share the same codepath.
Need By Date:
N/A
Solution:
Requirements / Acceptance Criteria:
Solution will be complete when offloaded and non-offloaded dc-quic share the same codepath. Dc-quic should be able to get the exporter secret, certificates, ciphersuite and other tls information from the connection through the s2n-quic events subscriber.
Out of scope:
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:
We've chosen to merge the existing dc-quic offloading integration and get real performance data at a faster pace, rather than doing a larger refactor right now. See this comment for where this feature currently stands. Therefore, we will need to improve the integration code so that offloaded and non-offloaded dc-quic share the same codepath.
Need By Date:
N/A
Solution:
Requirements / Acceptance Criteria:
Solution will be complete when offloaded and non-offloaded dc-quic share the same codepath. Dc-quic should be able to get the exporter secret, certificates, ciphersuite and other tls information from the connection through the s2n-quic events subscriber.
Out of scope: