Skip to content

security: verify and improve README.md + language-versions.md #288

Closed

Description

@homer6

Turn the imported docs/security/README.md + language-versions.md (the layered model and toolchain vs language version) 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: Feature-test macros, toolchain support per facility (C++11–C++26), C++26 contracts and library hardening status from vendor pages.

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 the PR above (security/288-overview → dev-0.5).

    What changed

    • docs/security/README.md: verified overview, the page conventions (MUST/SHOULD, Core Guidelines + CERT IDs, tests in tests/security/, imported/verified status), status column, fixed source links.
    • docs/security/language-versions.md: rewritten and verified; the libstdc++ -O0-only assertions default, the library hardening switches and defaults, feature-test macros per facility, the corrected C++26 status (P4433R0 is about the DIS ballot), integer-comparison and feature-gating examples.
    • tests/security/language-versions_test.cpp: 7 tests (new security area).

    Why

    • Each claim was checked against GCC 15 release notes, libc++ and MS STL hardening docs, P4433R0, Microsoft's C++ security guidance, and the headers and behaviour of GCC 15.2, GCC 16.2 and Clang 22.

    Still open

  3. homer6 commented on Nov 3, 2026

    @homer6
    OwnerAuthor

    Merged in #314 (4a270a5) into dev-0.5. No changes since the PR opened.

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