Skip to content

Epic: v0.5.0 — security #286

Closed
Closed

Description

@homer6

v0.5.0 is about helping users write secure C++: code that holds up against an adversary (trust boundaries, untrusted input, secrets, attack surface, hardening, verification, supply chain). Security is not the same as safety: docs/guidelines/safety.md covers correctness and memory safety; docs/security/ builds on it and links to it where a safety defect is the attack path.

Framing: C++ written to the Core Guidelines (explicit ownership, bounded interfaces, checked conversions, the type/bounds/lifetime profiles) and verified with analysis, sanitizers and fuzzing is the path to secure code. The pages never present C++ as "not memory-safe".

Branching: work lands on dev-0.5 (forked from dev at ddf1dfa). Each issue gets a feature branch in its own worktree and a PR into dev-0.5. dev-0.5 is rebased onto dev when dev moves.

Plan:

  1. Import the owner's research report ("Security Practices for Modern C++") into docs/security/, one page per section, nearly as written (the owner chose import-then-fix).
  2. Verify and improve each page: check claims against primary sources, cite Core Guidelines and SEI CERT rule IDs, add our own tested examples (tests/security/<page>_test.cpp), link the safety foundations.
  3. Prove the claims across platforms: hardened build presets and CI jobs, death tests that show hardening fires, fuzz harnesses, clang-tidy.
  4. Make the skills and docs use it: security review in modern-cpp/cpp-guidelines, evals, CLAUDE.md, platform report.

The checklist of child issues follows below.

Checklist

1. Import

2. Verify and improve each page

3. Prove it across platforms

4. Skills and docs

Activity

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

    @homer6
    OwnerAuthor

    Shipped in v0.5.0: https://github.com/homer6/cpp-docs/releases/tag/v0.5.0 (release PR #389, tag on f97b4608). Every child issue is closed; docs/security/ is on main, with the hardened, fuzz and clang-tidy CI jobs and the security skill. Follow-ups outside the epic: #354 (UBSan in the Apple fuzz build), #313 (contracts status).

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