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
A short description of what the problem is and why we need to fix it. Add reproduction steps if necessary.
Solution:
A description of the possible solution in terms of S2N architecture. Highlight and explain any potentially controversial design decisions taken.
Does this change what S2N sends over the wire? If yes, explain.
Does this change any public APIs? If yes, explain.
Which versions of TLS will this impact?
Requirements / Acceptance Criteria:
What must a solution address in order to solve the problem? How do we know the solution is complete?
RFC links: Links to relevant RFC(s)
Related Issues: Link any relevant issues
Will the Usage Guide or other documentation need to be updated?
Testing: How will this change be tested? Call out new integration tests, functional tests, or particularly interesting/important unit tests.
CMakeLists.txt LICENSE Makefile NOTICE README.md api bam-bam-boogieman bin cmake codebuild codecov.yml coverage coverage.info crypto docker-images docs error issues_page lib libcrypto-build libcrypto-root pq-crypto rename_default_branch.sh rename_github_links.sh run.sh s2n.mk scram stuffer test-deps test.sh tests tls tmp tmp2 trun.sh utils Will this change trigger SAW changes? Changes to the state machine, the s2n_handshake_io code that controls state transitions, the DRBG, or the corking/uncorking logic could trigger SAW failures.
CMakeLists.txt LICENSE Makefile NOTICE README.md api bam-bam-boogieman bin cmake codebuild codecov.yml coverage coverage.info crypto docker-images docs error issues_page lib libcrypto-build libcrypto-root pq-crypto rename_default_branch.sh rename_github_links.sh run.sh s2n.mk scram stuffer test-deps test.sh tests tls tmp tmp2 trun.sh utils Should this change be fuzz tested? Will it handle untrusted input? Create a separate issue to track the fuzzing work.
Out of scope:
Is there anything the solution will intentionally NOT address?
The text was updated successfully, but these errors were encountered:
Problem:
Here is a link: https://github.com/lrstewart/s2n/blob/master/api/s2n.h
A short description of what the problem is and why we need to fix it. Add reproduction steps if necessary.
Solution:
A description of the possible solution in terms of S2N architecture. Highlight and explain any potentially controversial design decisions taken.
Requirements / Acceptance Criteria:
What must a solution address in order to solve the problem? How do we know the solution is complete?
CMakeLists.txt LICENSE Makefile NOTICE README.md api bam-bam-boogieman bin cmake codebuild codecov.yml coverage coverage.info crypto docker-images docs error issues_page lib libcrypto-build libcrypto-root pq-crypto rename_default_branch.sh rename_github_links.sh run.sh s2n.mk scram stuffer test-deps test.sh tests tls tmp tmp2 trun.sh utils Will this change trigger SAW changes? Changes to the state machine, the s2n_handshake_io code that controls state transitions, the DRBG, or the corking/uncorking logic could trigger SAW failures.
CMakeLists.txt LICENSE Makefile NOTICE README.md api bam-bam-boogieman bin cmake codebuild codecov.yml coverage coverage.info crypto docker-images docs error issues_page lib libcrypto-build libcrypto-root pq-crypto rename_default_branch.sh rename_github_links.sh run.sh s2n.mk scram stuffer test-deps test.sh tests tls tmp tmp2 trun.sh utils Should this change be fuzz tested? Will it handle untrusted input? Create a separate issue to track the fuzzing work.
Out of scope:
Is there anything the solution will intentionally NOT address?
The text was updated successfully, but these errors were encountered: