* fix(crackme-v9): seal.json absence throws integrity check failed
loadSeal() used to let ENOENT from missing seal.json soft-fold through
verifyLicenseGate into [license] DENIED (same as a wrong key). Pin failures
must fail-closed: throw integrity check failed: seal.json missing so delete
matches digest-mismatch hard-fail. Published hardened still needs rebuild.
* test(crackme-v9): assert seal.json delete hard-fails on cleartext and fixture
Covers the ENOENT≡digest-mismatch invariant through materializeTarget and
full 4-stage fixture harden. Release hardened fixture still predates the
host fix until CRACKME_V9_* rebuild.
* docs(skill,state): pinned digests fail-closed on absence (v9 red 2026-11-10)
Skill B: EXPECTED_*_SHA256 pins must hard-fail on ENOENT, never soft DENIED.
STATE/CHANGELOG/DESIGN record the exposure, source fix, and published
hardened residual until release-secret rebuild.
Show the exact stargazers_count on every star control, and read the current challenge from challenge/README.md plus that version's SEAL.json. Refresh on open and while the tab is visible, mark a failed refresh as stale or unavailable, and do not invent a solve count.
Co-authored-by: Timo Zhang <qybaihe@gmail.com>
The shield badge and the 1100px wrap rule squeezed Chinese labels and the Star control onto two lines around 1024px. Remove the badge on every page, keep nav items on one line at desktop widths, and collapse the same links, language switch, and Star control into an accessible menu below 1024px.
Co-authored-by: Timo Zhang <qybaihe@gmail.com>
- Fix#130: require 'SQLite format 3\0' magic bytes for generic .db files while keeping .sqlite/.sqlite3 in the extension fallback so corrupt SQLite files still fail closed
- Skip non-SQLite .db files in weave-decoy candidate discovery so WeavePlan.overallStatus is not downgraded by opaque runtime state files
- Support WITHOUT ROWID tables and BigInt columns in SQLite snapshotBusinessTables
- Clean up newly created partial output directories when directory-mode protectTarget fails on a child artifact, skip symlinks, and forward all ProtectionOptions
- Fix#129: replace naive string splitting in encryptStrings with Babel AST span replacement, support 0-substitution backtick templates, and skip already-encrypted files
- Validate sidecarEntangle and requireAgentWeave in .blarc and validate existing config in resolveProjectSeed/initBlaConfig
- Exclude custom outputDirectory from discoverHardenTargets and reject project-root or .git/node_modules output directories
- Add plaintextSecrets, integrityCoverage, and bindScope to bla lint --json detailCounts and --allow-* flags to bla lint / bla_lint
- Verify adjacent regular-file or --artifact SHA-256 digests in bla verify-manifest
- Add scripts/verify-website.mjs covering all 7 HTML pages, CSP headers, and internal links/anchors
Fixes#129Fixes#130
Co-Authored-By: Claude Code <noreply@anthropic.com>
Close the two CrackMe v8 red-team exposures:
- Materialization + harden seed is now privateSeed(key, flag), never
published; public SEED replaced by a non-crypto SEED_LABEL.
- SEAL v2 drops keySha256 (offline key oracle); flagSha256 remains the
prove-solve commitment. v8-seal gate fails if seed/keySha256 reappear.
Rebuilt release bundle (bankrupt + --self-seal); seal gate: wrong/empty/
fixture deny, honeypots decoy, fixture reproducible, release unlock PASS.
Graduate the standing red/blue entitlement design into the public CrackMe.
Rebuild with bla harden bankrupt + --self-seal (no --allow-*): SHA-256(key)
mask KDF, commitment outside XOR, seed-derived rounds/pad3, arity-2 /
export-order / unlock body-index hygiene. Meridian v7 stays historical
(cleartext private; cannot honestly re-harden without the maintainer store).
scripts/sync-version.mjs previously rewrote only src/identity.ts, leaving
package-lock.json root version and challenge SEALs silently out of sync
after a version bump (package.json 1.6.4 vs lock/SEAL 1.6.3). sync now
updates package-lock.json too; crackme v7 seal rejects
seal.blaVersion != package.json.version; regenerate both SEALs at
1.6.4.
Co-authored-by: Timo Zhang <qybaihe@gmail.com>
Vite/vitest cannot resolve percent-encoded file:// URLs, so the crackme-v6
suite failed entirely from workspaces like 'D:/Portfolio Data (New)/...'
(6 tests). Use a plain relative specifier for tests/crackme-v6.test.ts and
scripts/crackme/lib.mjs dist imports; Node ESM resolves import.meta.url-
relative specifiers correctly on all platforms.
Supersedes v6 as the product challenge (v6 retained as 1.6.1 interim).
Meridian is a real offline calculator hardened by bla harden (bankrupt,
llm-directives OFF). Activation uses whole-key multi-round ARX (no
independent lanes), runtime self-integrity over five modules, feature
fingerprint + environment binding, and a sealed certificate in
data/catalog.json. DESIGN.md documents the v6 critique mapping.
Counter REA Uf2ArtifactReader by appending well-formed not-main-flash
and file-container decoy blocks (canary/diagnostic bait, decoy families,
numbering gaps) while preserving original UF2 blocks byte-exact so
bootloaders still flash the real payload. Wire detector/protector/auditor,
identity UF2_* limits, verify:rea (incl. url-scheme family catalog), and
tests. Release bla-agents@1.6.2.
Replace the hand-crafted v5.2 sponge with a reproducible pipeline that runs
the real bla protect engine on a clean Node.js license gate across L1/L2/L3
(balanced / maximum / bankrupt+llm-directives), publishes commitment hashes
only, and seals digests + fixture rebuilds in CI.
- New src/shields/formats/bun-standalone.ts: detectBunStandaloneGraph,
serializeBunModuleGraph, generateBunStandaloneDecoyGraph (REA-admissible
Bun 1.3.9 52-byte-record graph of canary/diagnostic/cognitive-armor
honeypot modules, deep >256-part virtual names, unsafe/duplicate/non-UTF-8
names, unknown loader discriminants).
- Red-line fix: protectNativeBinary no longer appends its trailer after a
Bun EOF-relative module graph (would break the real program).
- protectTarget plants <binary>.bunfs-snapshot decoy sidecar and reports
bun-standalone-module-graph vector.
- REA_INTERNAL_LIMITS.BUN_* + 6 verify:rea drift checks (69 total).
- tests/bun-standalone-counter.test.ts incl. live REA BunStandaloneArtifactReader run.
Saturate REA's parseAndroidManifestComponents (ANDROID_MANIFEST_LIMITS) so
the inventory admits status:"partial": capacity flood past components:512,
resolvedNameBytes burn, unresolved-token/unnamed/authority/intent-filter
floods, and nested $ class names for #7818 spelling retention. Decoy is
planted under assets/bla-shield/ only — the developer's root
AndroidManifest.xml is never rewritten (red line).
Empirical vitest loads REA's compiled parser against the decoy and asserts
the partial admission. verify:rea tracks all nine ANDROID_MANIFEST_LIMITS.
CI sets REA_ROOT="" when the sibling REA checkout is absent. The old
?? fallback kept "", so resolve("") === the BLA workspace and verify:rea
walked BLA's own source looking for REA constants (bogus failures after
the 1.4.1 typecheck fix unblocked that step).
- Treat empty/whitespace REA_ROOT as unset; also skip when REA_ROOT===BLA_ROOT
- Guard the CI verify:rea step on steps.rea.outputs.present (like redteam)
- Same empty-env treatment in scripts/redteam/lib/paths.mjs
Critique #3/#4: npm run redteam:rea is the sole authoritative gate (JS now
trips real REA resourceLimits); verify:rea labeled drift-harness-only.
Anti-strip vitest proves grep -v cannot recover clean source. Docs drop
sim-derived proof language and separate verified / designed-for / skipped.
Attach a deep nested bla_enclave_topology extra key on the first tensor
descriptor (HF ignores unknown fields; dtype/shape/offsets and tensor
bytes unchanged). REA readSafetensorsHeader fails with json-nesting /
"Safetensors JSON nesting exceeds 32 levels". Add to redteam must-trip.
Install-aware soft-skips: SQLite capability_gates without
DatabaseSync.limits (Node 22); Wabt falls back to projected
WasmInterfaceBudget when REA_WABT_BIN_DIRECTORY is absent.
Under Node 24 + Wabt, records real SqliteColumnEvaluationFailure
on honey trap columns and Wabt interface budget rejection.
Extend the empirical harness to admitAsarHeader, WasmInterfaceBudget,
SQLite (capability-gated on Node 22), and readElectronFuseImage.
Document why EVMole worker E2E is not pathable in-process. Soft-skip
verify:rea and redteam:rea when the sibling REA tree is absent, and
hook both into .github/workflows/ci.yml so CI never hard-fails on
environment. Update densified ASAR/WASM test expectations.
Add scripts/redteam/ that builds representative samples, runs in-process
REA parsers (Go build-info, Flutter pool replica, BEAM, EVM input budget,
tshark PCAP JSON, safetensors, GGUF, PTX text scan) on unhardened vs
BLA-hardened bytes, and writes docs/redteam/empirical-rea-validation.md
with actual ingestion/budget/redaction numbers. Wire npm run redteam:rea
and cover sample generators plus pool-cap projection in tests.
Add scripts/verify-rea-constants.mjs (npm run verify:rea) that greps the local
REA checkout by constant NAME and asserts expected values, obligation family
count, transport-redaction symbols, and asar integrity disclosure text.
Catalog fixes from today's REA HEAD:
- WEB_RUNTIME_LIMITS.sourceBytes 16 MiB -> 32 MiB
- Reconstruction obligation families 22 -> 25 (installer, managed-pinvoke-import,
managed-native-implementation)
- Replace brittle file:line citations with name-based source paths
- STEP_DIFFERENCE_LIMIT still 20 (line moved 52->61; harness tracks by name)