Repository navigation
Anti-REA Forge v1.3.0
Anti-REA Forge 1.3.0 — Private inputs and residual disclosure channels
Release date: 2026-11-18. Python core and JavaScript SDK use 1.3.0.
The existing v1 signed-document formats and CLI/import names are unchanged.
This release closes specific publication gaps reproduced against the official
v1.2.0 wheel. It adds a production interface for current private-file references,
checks configured asset keys in Python bytecode integers, separates eligible
embedded LLVM compiler metadata, and detects private PEM markers inside one
outer JSON hex/Base64 encoding. Ordinary distributed code remains analyzable.
Measured changes
| Control | Official v1.2.0 | v1.3.0 candidate | Required positive / compatibility evidence |
|---|---|---|---|
| 12 canonical Python integer-key representations | Allows all 12; real REA constants reconstruct the exact key | Positively rejects all 12 on disk and in executable ZIP apps | Each recovered key authenticates and decrypts an owned AES-GCM payload; normal PYC remains executable |
| Actual Clang embedded IR after symbol stripping | Gate allows output; llvm-dis recovers 4 private names, a source path and arithmetic |
Reports compiler metadata; splitter removes the eligible public IR channel | Exact private bitcode/command bytes retained; original, old public and new public runtime results are [48, 85, 122]; .text and dynamic symbols unchanged |
| Actual raw and wrapped compiler bitcode | Allows both, renamed and in nested ZIPs | Refuses all 4 layout cases as unsupported inspection | llvm-dis really recovers both compiler-produced inputs; no claim of full bitcode parsing or macOS execution |
| Private implementation accidentally copied into a JS release | Default policy allows the source file | Configured live reference rejects the exact copy | Real REA private-source nodes 1 → 0 → 1 for accidental / public-only / restored layouts; all graphs complete |
| Current private source differs from an old manually entered digest | Old digest permits the changed copy | Live reference rejects the current exact copy | A new snapshot is taken on each check and rechecked through prepare |
| 8 outer PEM representations | Allows all 8; actual Ed25519 signatures verify | Positively identifies all 8 | Two ordinary public/nonsecret controls still pass |
| 2 recoverable PEM representations outside decode budgets | Allows both | Refuses as incomplete inspection | Actual decoding/signing still succeeds; excluded from the eight positive detections |
The Python and private-source controls run against both the pinned npm REA 6.9.0
and the source build at 675287517c98c702ee88ad036c5e3b8dd4bcc7a7. They exercise real
CLI providers, not an autonomous model session. Compiler and PEM controls use
actual standard readers; those experiments do not invoke REA. Fixture counts
are not vulnerability counts or a general resistance/recall percentage.
Baseline integrity
All new paired benchmarks can bind their baseline interpreter to the official
v1.2.0 wheel. Required CI supplies that wheel and verifies its SHA-256:
b16280c1f81cb6cec5a028102edeefdaf8b62e9300da3e87acb1878b3f0ab75b
The experiments compare every installed package file with the verified wheel
and recheck package inventories at completion. Candidate identities and analyzer
versions/build inventories are recorded in the JSON results. A wrong version,
incomplete analyzer output or changed tool/package ends the experiment; it is
never converted into a successful protection result.
New private-file references
Keep the implementation outside the public build and declare its input files
in the build-only project configuration:
{
"version": 1,
"product": "MyApp",
"root": "../dist",
"policy": "policy.json",
"asset_key_files": ["../../issuer/data.key"],
"private_input_files": ["../../service/operation.py", "../../service/config.json"]
}scan-release, check and prepare also accept repeatable
--private-input-file arguments. scanRelease and checkProject in the SDK
accept privateInputFiles. Extra references add to the saved configuration;
an empty extra list cannot disable it. Configured paths resolve relative to the
project file; direct CLI paths resolve from the working directory.
Each reference must be a nonempty regular file outside the release root. The
limits are 64 files, 8 MiB per file and 64 MiB total. No glob expansion,
directory recursion or source execution is performed. Missing files, links,
reparse points, special files and changed inputs fail the operation. The build
operator must control the files and their ancestors. Identity checks and hash
rechecks detect ordinary replacement; they are not an atomic snapshot against
a hostile filesystem owner.
Exact whole-payload copies produce private_input_exposure, including inspected
ZIP and ASAR members and verified unpacked ASAR siblings. Reports show reference
counts and rule indexes without adding external source paths or separate
reference hashes. Existing public inventory hashes remain visible, including
the hash of an accidentally published exact copy.
Transformed, compiled, concatenated, encoded or partial copies do not match
this particular rule. Keep private service code out of the public build graph,
review the allowed output inventory and include all relevant source/config
references. The new service example reuses the
existing run_authorized_operation API. It does not introduce a new HTTP/RPC
protocol or claim a newly discovered authorization bypass. Host authentication,
transport, quotas and access control remain application responsibilities.
Configured keys in Python bytecode
When asset_key_files are configured, recognized stable CPython PYC headers
enter the canonical-marshal-integer/v1 profile. For each known 32-byte key the
scanner derives canonical base-2¹⁵ marshal integer records for big/little-endian,
signed/unsigned reconstruction and their reference-flag variants. It streams
at most 64 MiB and never calls marshal.load, imports examined code, or
executes it.
The separate report fields are pyc_asset_keys_checked,
pyc_asset_key_files_checked, pyc_asset_key_scan_completed and
pyc_asset_key_profile. JSON/DER completion remains independent. A matched
record produces asset_key_exposure with representation
python-marshal-integer; unsupported headers, changed lengths, short integer
aliases or exhausted budgets produce a fixed unverifiable finding.
The header classification covers stable magic values for CPython 3.7–3.14;
the release guard itself still requires Python 3.10+. Header recognition does
not validate every marshal object or execute one version's bytecode under
another version. Each integer interpretation must have at least 128 significant
bits; this is a bounded-pattern condition, not an entropy estimate. An
unconfigured key remains recoverable, and the benchmark preserves that failure
as an explicit boundary. Computed/split constants, noncanonical encodings and
general Python implementation secrecy are outside this profile.
Exact framing and official-source references
Compiler metadata
The native readers report compiler_metadata_present and
compiler_metadata_sections separately from debug evidence:
| Format | Recognized canonical sections | Action |
|---|---|---|
| ELF | .llvmbc, .llvmcmd, .llvm.lto |
Gate finding; eligible data can be split privately |
| PE | .llvmbc, .llvmcmd |
Gate finding; no PE rewriting added |
| Mach-O | __LLVM,__bitcode, __LLVM,__cmdline, __LLVM,__bundle |
Gate finding in each supported slice; no Mach-O rewriting added |
| Standalone bitcode | Raw 42 43 C0 DE and wrapper DE C0 17 0B |
Recognized but unsupported; native metadata completion is false |
scan-release applies these checks under check_native_metadata. The native
gate adds require_no_compiler_metadata, true by default; unavailable ELF
section names cannot establish absence. If a product intentionally ships this
metadata, review and explicitly set the relevant policy opt-out.
The ELF splitter accepts only unique, nonallocated PROGBITS compiler sections
with ordinary flags or SHF_EXCLUDE, no section links/entry semantics, and no
overlap with any file-backed program segment. It checks exact private payload
fingerprints and existing runtime-segment/dynamic-interface invariants. Failure
rolls back its new outputs. Public machine code still implements the algorithm
and remains available to disassemblers.
The checked-in real producer result uses Clang/llvm-dis 19.1.7 on Linux;
required CI independently runs the control with LLVM 18. PE/Mach-O additions
have structural parser regressions, including byte orders and fat slices; those
tests are not new Windows/macOS compiler/runtime measurements.
Wrapped PEM and shared budgets
The JSON scanner recognizes supported private PEM headers inside one outer
hex/Base64 encoding, including leading notes accepted by actual PEM consumers.
It scans bounded hints across the JSON string, then confirms decoded markers.
Node-compatible Base64 handling is reused; a label is conservative disclosure
evidence, not mathematical validation of every possible key.
PEM and DER share a 64-candidate / 256 KiB decoded-byte per-document budget.
Each admitted candidate retains the 256 KiB raw-text / 64 KiB decoded-byte
limit. Even a false alignment hint consumes the budget for its actual decode.
Large unrelated strings remain accepted without private-key parsing; a private
candidate beyond a limit is unverifiable. These budgets sit within the existing
8 MiB / 64-depth / 100,000-node JSON limits. Arbitrary nested wrappers, split keys
and computed material are not evaluated.
Upgrade and release verification
- Install matching 1.3.0 core and SDK archives from the
release. - Add current private-file references and known asset keys to trusted build
configuration. Rebuild from original native inputs when separating compiler
IR; do not remove an arbitrary allocated section to force a passing result. - Review newly rejected artifacts and explicit policy choices. Removing the
finding from a report does not remove leaked material from the artifact. - Keep staging directories immutable and trusted while
preparescans, signs
and verifies their contents. Deploy private implementations separately.
The existing 13 required CI jobs remain in force, covering Linux, Windows
and macOS. Real compiler and REA controls are mandatory in their jobs. Fresh
wheel/sdist installs must exercise the new private-input, PYC, PEM and standalone
bitcode behavior; the packed SDK must exercise private-file arguments. The
publisher requires each boolean to be exactly true and verifies the exact main
commit, complete required job set, clean install evidence and archive hashes.
Local tool-dependent skips are reported separately in the
local validation record.
The published release-evidence.json, installation-report.json and
SHA256SUMS bind the downloadable files to their tested commit. The earlier
v1.2 corpus results remain available and their mandatory controls continue to
run; historical observations are not relabeled as new measurements.
Reproduce the new controls
Use fresh output/work paths, a candidate interpreter, the verified v1.2 wheel
installed in a separate environment, and npm ci --prefix benchmarks/recovery-tools.
node benchmarks/python_key_recovery.mjs --python /trusted/candidate/python \
--baseline-python /trusted/v1.2/python --baseline-wheel /trusted/open_release_guard-1.2.0-py3-none-any.whl \
--out python-key-recovery.json
node benchmarks/private_input_controls.mjs --python /trusted/candidate/python \
--baseline-python /trusted/v1.2/python --baseline-wheel /trusted/open_release_guard-1.2.0-py3-none-any.whl \
--out private-input-controls.json
python benchmarks/encoded_pem_recovery.py --python /trusted/candidate/python \
--baseline-python /trusted/v1.2/python --baseline-wheel /trusted/open_release_guard-1.2.0-py3-none-any.whl \
--out encoded-pem-recovery.json
python benchmarks/llvm_metadata_recovery.py --llvm-bin /usr/lib/llvm-18/bin \
--python /trusted/candidate/python --baseline-python /trusted/v1.2/python \
--baseline-wheel /trusted/open_release_guard-1.2.0-py3-none-any.whl \
--work new-llvm-corpus --out llvm-metadata-recovery.jsonFor both Node controls, add --rea-source /trusted/rea --rea-source-commit 675287517c98c702ee88ad036c5e3b8dd4bcc7a7 to select the separately built source
distribution. Compiler controls require Linux Clang/llvm-dis and GNU tools.
Evidence files
- Python: npm /
source. - Private inputs: npm /
source. - Actual LLVM recovery and preservation.
- Wrapped PEM signing recoveries and budgets.
- Chinese assessment and
security limits.