Skip to content

release: v0.5.0 — the security release - #389

Merged
homer6 merged 85 commits into
mainfrom
dev
Nov 4, 2026
Merged

homer6 merged 85 commits into
mainfrom
dev

Conversation

@homer6

@homer6 homer6 commented Nov 3, 2026 •

Copy link
Copy Markdown
Owner

Release v0.5.0: the security release. Notes: docs/releases/v0.5.0.md.

Tracking: #363 (this release), #286 (the security epic).

What it includes

Known issues

Verification

  • CI: three consented runs of all.yml on dev. Each job counts from the newest run that ran it.
    • 41657155620 at 3c85772: every job.
    • 41689101415 at 3835b98: the 43 jobs that failed.
    • 41707574171 at 86f6c76: the last 4.
    • Result: 59 toolchain jobs, 0 test failures, plus clang-tidy and fuzz green. That covers Linux, macOS, Windows (MSVC, clang-cl, MSYS2) and FreeBSD, on x86_64 and arm64.
  • Local, at 86f6c76:
    • Tests: gcc-15 1423 passed, clang-22 1396, gcc-16 1505, and both ASan presets, all with 0 failed.
    • Snippets: GCC 15 and 16 1698 checked with 0 failed. Clang 22 had 19 failures, all in the known baseline (0 new).
    • Guidelines snippets: 1006 checked, 0 failed.
    • Other checks: links, index, workflows and evals pass, and clang-tidy has no findings.
  • What's untested: dev is now 81cc1d3. The only change since 86f6c76 is release: v0.5.0 notes, version, platform report and support notes #388 (docs, the README and the project(VERSION) line), so nothing was re-run.

After the merge

  1. Tag v0.5.0 on the merge commit.
  2. Create the GitHub release from the notes, with links made absolute at the tag.
  3. Comment on and close Release v0.5.0 #363 and Epic: v0.5.0 — security #286.

homer6 added 30 commits November 3, 2026 05:21
One page per section of the owner's report "Security Practices for
Modern C++", nearly as written; each page links its verification issue.
The report's premise that C++ is not memory-safe is left out, and the
README separates security from safety.

Related to #287
Check each claim against primary sources and our toolchains, add the
page conventions, and test the feature-test macros, the integer
comparison example and libstdc++'s unoptimized-only assertions default.
P4433R0 turned out to be about the failed C++26 DIS ballot, so the
page now says contracts and library hardening are unsettled.

Related to #288
A /cpp-security entry point for the security section: threat model
first, the page table, the review checklist with an attack-first
finding format, hardening a build for the actual toolchain and
confirming it, and planning the verification. It reads each page's
imported/verified status and treats imported claims as leads.

Related to #312
feat(skills): add the cpp-security skill
docs(security): verify the threat-modeling page
docs(security): verify the ownership-and-lifetime page
docs(security): verify the bounds page
docs(security): verify the integers page
docs(security): verify the object-representation page
docs(security): verify the parsing-and-validation page
docs(security): verify the concurrency page
docs(security): verify the error-handling page
homer6 added 23 commits November 3, 2026 09:30
GCC 14.2's libstdc++ has no C++ <stdckdint.h>, so __has_include finds GCC's C header, whose ckd_add casts to _Bool and doesn't compile as C++. Both FreeBSD jobs (GCC 14.2) failed on integers_test.cpp. libstdc++ defines the macro from 14.4, 15.3 and 16 (checked); the page records what was measured.

Related to #369
…layout

With libc++'s standard string layout the size byte that user.size() reads sat inside Ping's int, so ASan saw an in-bounds read and the bad run block failed on every Linux and Intel-macOS libc++ job. Ping now has no data members, so Login's string lies wholly past the end of the real object on libstdc++ and both libc++ layouts.

Related to #370
The hardened presets build at -O2, where GCC on x86-64 expands std::rint inline as the rounded magnitude with the sign copied back; rint(-2.5) under FE_UPWARD gave -3. -frounding-math, GCC's documented flag for code that changes the rounding mode, keeps it correct. The cfenv page's Gotchas record the finding.

Related to #371
docs(security): bounds bad-run example reads through a pointer
docs(claude): quote the attribution footer without link syntax
fix(fuzz): rename the parse_port corpus file nul to embedded-nul
docs(security): gate ckd_add on __cpp_lib_stdckdint_h, not __has_include
docs(security): make the bad-downcast example caught on every string layout
test(numerics): build cfenv_test with -frounding-math on GCC
Every platform workflow and all.yml take a jobs input, a regex searched for in each job's name. Each workflow's jobs are listed in .github/ci/<workflow>.json, and a plan job (tools/ci/plan.py) turns the matching entries into each job's matrix, so jobs that don't match never start. A fix-up run can start only the jobs that failed, on the fixed commit, instead of re-running every job of their workflows.

check_workflows.py checks that each workflow and its job list agree. collect_results.py supersedes per job name, so a fix-up run replaces only the jobs it ran, and the workflow table links every run a workflow's jobs come from. The GCC 16 ASan job gets its own name; it shared one with the plain GCC 16 job.

Related to #376
ci: select which jobs a workflow run starts
The clang-tidy job failed on six prctl calls in deployment_test.cpp's Linux-only tests: prctl is a variadic C system call with no typed alternative. On libstdc++ 15 (Ubuntu 26.04), hardening_test.cpp's library-hardened branch is compiled and its two macros are flagged too; they must stay macros (tested by #if, and GTEST_SKIP must return from the test body). Both are kept with NOLINT blocks and the reason.

Related to #378
…lang

In the Clang 22 hardened build (-O2), Clang moved 1.0 / x past fetestexcept, so HoldAndUpdateEnv saw FE_DIVBYZERO. The page's example has #pragma STDC FENV_ACCESS ON; the test now has it too, at block scope for Clang, like the test's other uses.

Related to #379
/sdl makes C4996 an error, and C4996 deprecates standard C functions the tests check (fopen, gmtime, strncpy, sscanf...) in favour of Annex K's _s versions, so the hardened MSVC build failed with 38 errors. Defining _CRT_SECURE_NO_WARNINGS silences only that warning; /sdl's runtime checks and other errors stay. hardening.md says so.

Related to #380
test(security): mark the intentional clang-tidy macro and vararg uses
test(numerics): FENV_ACCESS in the cfenv test's quiet_reciprocal on Clang
build(harden): define _CRT_SECURE_NO_WARNINGS with MSVC's /sdl
libc++ 18 checks formattability with its own context type, so a format() that takes only std::format_context made std::format reject Secret: tests/security/deployment_test.cpp didn't build in the Clang 18 libc++ job. A templated format works everywhere; the page says why.

Related to #384
attributes_test.cpp calls its own [[deprecated]] old_api() on purpose and silenced the warning with #pragma GCC diagnostic only, which MSVC ignores. Under /sdl the deprecation warning C4996 is an error, so the hardened MSVC build still failed after #383. MSVC now gets #pragma warning(disable: 4996) around the call.

Related to #380
docs(security): template the Secret formatter's format on the context
test(language): silence the deliberate deprecated call on MSVC too
docs/releases/v0.5.0.md with the local counts and the per-platform table of the three release runs (41657155620, 41689101415, 41707574171); project VERSION 0.5.0 (release_notes_exist); docs/platform-support.md, the toolchain pages, the README table and badges regenerated from those runs and the local runs at 86f6c76; the runs archived; docs/platform-support/notes.md re-derived claim by claim against the results.

Related to #363
release: v0.5.0 notes, version, platform report and support notes
@homer6 homer6 changed the title Dev v0.5.0 release: v0.5.0 — the security release Nov 3, 2026
@homer6 homer6 mentioned this pull request Nov 3, 2026
7 tasks done
@homer6
homer6 merged commit f97b460 into main Nov 4, 2026
@homer6

homer6 commented Nov 4, 2026

Copy link
Copy Markdown
Owner Author

Merged into main as a merge commit (f97b4608) on Steve's review; dev kept.

Checked: base main ← head dev at 81cc1d3, mergeable, no AI attribution. Proof is in the description: 59 CI toolchain jobs with 0 test failures across runs 41657155620, 41689101415 and 41707574171, and the local runs at 86f6c76 (only #388's docs and version line came after; not re-run).

Done after the merge: tag v0.5.0 on f97b4608, and the GitHub release with links made absolute at the tag.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Release v0.5.0

1 participant