Security issue notifications

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

Problem:

Once Nix pkgs are bumped to 2411, we could pull in uv.

Solution:

Refactor the nix/pyenv.nix to use uv and reference the pyproject.toml from #5029 .

• Newer apache won't start with RSA1024 test cert Apache test cert updates #5271
• Bump to nixpkgs 2411
• Establish a new pattern for using uv/pytest with the sslyze test first ci: Fix the sslyze test for nix #5283
• Enable the renegotiate_apache test with uv/pytest Flip Nix integration tests to use uv/pytest #5352
• Deprecate the old nix integ job and run all integ tests with uv/pytest

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.
  • 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.
  • 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?