Commit Graph

27 Commits

Author SHA1 Message Date
qybaihe 2dc4eea241 feat(challenge): CrackMe v8 SEAL v2 — private harden seed, drop keySha256
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.
2026-11-04 19:06:03 +08:00
qybaihe 6037c35bf1 feat(challenge): CrackMe v8 Aegis — 2.0 engine + R1–R12 recipes
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).
2026-11-03 12:22:32 +08:00
qybaihe 124ddecf6f fix(release): sync CrackMe SEAL blaVersion with 2.0.0
v7-seal rejects seal.blaVersion != package.json; bump v6/v7 labels and
extend sync-version.mjs so future bumps keep SEALs in lockstep.
2026-11-03 11:59:31 +08:00
qybaihe 339415cc76 feat(harden): refuse lane-independent JS gates unless allowed
protect/defend/harden refuse JS/TS that looks lane-independent unless
allowLaneIndependentGates / --allow-lane-independent / allow_lane_independent.
CrackMe v6 teaching fixture now opts in explicitly (preserve mix/seal + allow
lanes). Skill v1.5.2 + docs: no silent stable WASM ABI; prefer whole-key mixing.
2026-11-03 03:38:51 +08:00
qybaihe be0eeb201b fix(redteam): emit unverified JSON when REA dist absent
Keep CI soft-skip exit 0, but print bla-redteam-rea/v1 status unverified
so agents never treat SKIP as a red-team pass. Harness covers the path.
2026-11-03 03:34:08 +08:00
Dery Ferdika 3c18b1460b fix(release): sync version metadata across package metadata (#57)
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>
2026-11-02 20:36:02 +08:00
Dery Ferdika 91548db603 test(crackme): import lib.mjs with relative specifier for paths with spaces (#58)
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.
2026-11-02 20:32:07 +08:00
Timo Zhang e621d8e4ce fix(challenge): ship Meridian hardened bundle under challenge/v7/hardened 2026-11-01 02:15:55 +08:00
Timo Zhang 19679467b8 feat(challenge): CrackMe v7 Meridian — real app, chained ARX, self-integrity
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.
2026-11-01 02:15:55 +08:00
qybaihe cabdbb24ca feat(firmware): UF2 not-main-flash/file-container decoys vs REA #8230
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.
2026-11-01 02:14:23 +08:00
Timo Zhang 171e67ec1f CrackMe v6 harden-native: bla harden multi-format challenge replaces tiered draft
- challenge/v6 is now hardenProject() (== bla harden) output over a public
  template: Node vault + HTML panel (executed by the vault) + WASM core,
  bankrupt, llmDirectives=false, emitManifest=false, fixed seed.
- Per-build constants come from CRACKME_V6_KEY/FLAG; SEAL.json publishes
  digests only. Public demo fixture drives CI.
- crackme:seal + tests: digest pinning, uniform DENIED, honeypots,
  fixture re-harden unlock + reproducibility, anti-strip, secret-gated
  release reproduction.
- Archive PR #38 tiers under challenge/archive/v6-tiered-protect, v5.2
  under challenge/archive/v5.
2026-11-01 00:55:07 +08:00
qybaihe 823ea01af0 fix(crackme): Windows-safe dynamic import for protector API
Use pathToFileURL when loading dist/engine/protector.js so
crackme:build / crackme:seal work under Node ESM on Windows CI.
2026-11-01 00:44:33 +08:00
qybaihe 8f1f13397b CrackMe v6: BLA-generated tiered challenge
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.
2026-11-01 00:42:42 +08:00
qybaihe 71cf950485 feat(android,dex): counter REA #8154 with external-invoke decoy multidex (v1.5.2)
Plant a byte-valid classesN.dex whose decoy callers each invoke-static
android.util.Log.d, saturating MAX_EXTERNAL_XREF_BYTES (~1 MiB) on unsigned
APKs. Developer root manifest and existing DEX export surface preserved.
verify:rea now walks bridge/**/*.java (72 checks).
2026-10-31 02:16:13 +08:00
qybaihe b2d6436007 feat(native,bun): counter REA #6998 Bun standalone module graphs; preserve Bun appended-trailer executables byte-exact (v1.5.1)
- 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.
2026-10-30 02:12:44 +08:00
qybaihe e5a566a3f5 feat(android,manifest): counter REA #7379/#7818 with AndroidManifest component decoys (v1.4.9)
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.
2026-10-29 02:09:36 +08:00
qybaihe c77c468f73 feat(android,r8): counter REA #7456/#7472 with mapping poison + JNI decoy .so (v1.4.6)
Register PROGUARD_MAPPING_* / ANDROID_JNI_* / MAX_NATIVE_EXPORT_ROWS in identity.
Add android-r8.ts (residual conflicts past candidates:8, malformed past 16, ELF64
AArch64 ET_DYN with real Java_* dynsym). Wire into unsigned APK + DEX trailer.
verify:rea now 54 checks (Object.freeze-aware). Tests 206/206 on Node 24.
2026-10-28 02:12:47 +08:00
qybaihe 3e92cf6caa fix(ci): soft-skip verify:rea when REA_ROOT is empty; release v1.4.2
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
2026-10-27 13:09:03 +08:00
qybaihe 7aff8e68dc test+docs: anti-strip gate, real-REA-only evidence, demote verify:rea
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.
2026-10-27 09:56:45 +08:00
qybaihe 61f2de9cbe feat(shields): trip REA Safetensors MODEL_JSON_NESTING
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.
2026-10-27 05:12:05 +08:00
qybaihe c930073556 feat(redteam): Node 24 SQLite + Wabt E2E empirical probes
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.
2026-10-27 05:05:06 +08:00
qybaihe 31b2e036e3 feat(redteam): cover ASAR/WASM/SQLite/fuses; soft-skip CI without REA
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.
2026-10-27 04:57:33 +08:00
qybaihe 216bd32ded feat(redteam): empirical REA harness with real before/after metrics
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.
2026-10-27 04:46:21 +08:00
qybaihe a7f7c35199 feat(identity): track Go/Flutter/BEAM/EVM/PCAP/GPU/firmware REA budgets
Mirror MAX_BUILD_INFO_BYTES, MAX_POOL_URIS/TOKENS, BEAM chunk/atom
ceilings, EVM_INTERFACE_LIMITS, TSHARK_JSON_MAX_BYTES, GPU_* and
firmware staging/depth into identity + budget matrix + verify:rea.
2026-10-27 04:20:59 +08:00
qybaihe b09472eead feat(devtools): add REA constant drift harness and realign catalog
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)
2026-10-27 03:45:56 +08:00
qybaihe 98c01c992f chore(site): add sync:site script to mirror website/ to qybaihe/bla-site 2026-10-25 15:29:40 +08:00
qybaihe 986eedabf5 ci(release): bind qybaihe/bla to automated npm publishing and version sync 2026-10-25 15:19:02 +08:00