Skip to content

Run TCP fuzz tests in CI #27

@mark-e-deyoung

Description

@mark-e-deyoung

Problem

tests/fuzz_tcp.py exists (oversized message, garbage handling, post-fuzz health) but is never invoked by CI. The 10MB message limit and garbage handling are important security properties to verify continuously.

Proposed Solution

Add a CI step after the daemon smoke test: start daemon, run python tests/fuzz_tcp.py, verify exit code 0. Python is pre-installed on windows-latest.

References

  • Testing audit item 4

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions