Skip to content

security: verify and improve resource-limits.md #299

Closed

Description

@homer6

Turn the imported docs/security/resource-limits.md (availability and resource exhaustion) into a verified page.

  • Check every claim against a primary source (vendor docs, cppreference, CERT, OWASP, papers); fix or remove what doesn't hold, and say so in the PR.
  • Cite the Core Guidelines rule IDs and SEI CERT rule IDs (IDs and links only; don't copy CERT text).
  • Replace or add examples of our own, compile-checked, and tests in tests/security/ where a claim can be checked.
  • Link the safety foundations (docs/guidelines/safety.md, the docs/examples/ pages) instead of repeating them.
  • Positive framing: what makes C++ code secure.

Specific: Allocation budgets, recursion/nesting depth, algorithmic complexity, bad_alloc behaviour; tested limits.

Part of #286. PR into dev-0.5, from a feature branch in its own worktree.

Activity

  1. self-assigned this
    on Nov 3, 2026
  2. homer6 commented on Nov 3, 2026

    @homer6
    OwnerAuthor

    Delivered in #326.

    What changed

    • docs/security/resource-limits.md: verified rewrite (per-request budgets, decompression bounds, bounded queues, algorithmic worst cases, hash flooding with locally verified unsalted std::hash, allocation failure behaviour).
    • tests/security/resource-limits_test.cpp: 3 tests.
    • docs/security/README.md: status → verified.

    Why

    • std::hash salting checked against cppreference's note and by running libstdc++ 15 and libc++ 22 in separate processes; CERT MEM52-CPP against SEI's lists.

    Still open

    • Nothing for this page.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

securityv0.5.0 security work

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions