27 lines
1.3 KiB
Markdown
27 lines
1.3 KiB
Markdown
# Phase 1.0AG: bounded ELF admission
|
|
|
|
Status: `BOUNDED_ELF_ADMISSION_IMPLEMENTED_HISTORICAL_ARTIFACT_BYTES_MISSING`
|
|
|
|
Date: 2026-07-29
|
|
|
|
The bytes-only validator admits only an exact SHA-256-bound, little-endian
|
|
x86-64 `ET_DYN` payload of at most 2 MiB. All ELF, program-header, optional
|
|
section-header and load-segment ranges must be contained in the supplied
|
|
immutable byte string.
|
|
|
|
At most 32 program headers, 256 section headers and eight load segments are
|
|
accepted. Load memory is limited to 64 MiB across a 128 MiB virtual span.
|
|
Segments must have power-of-two alignment no greater than 2 MiB, must not
|
|
overlap, and may never be both writable and executable. `PT_INTERP` is
|
|
forbidden and the entry must fall inside an executable load segment.
|
|
|
|
The parser has no path or file interface and performs no mapping, relocation
|
|
or execution. Synthetic tests cover identity, hash, type, machine, bounds,
|
|
alignment, overlap, permissions, interpreter, entry and header-count failures.
|
|
|
|
The consumed Phase-1.0M artifact is a size/hash reference only. Its exact bytes
|
|
are absent from the scanned workspace, so Phase 1.0AG does not claim to have
|
|
admitted it. A future canary must be rebuilt and validated from its exact bytes.
|
|
Before target mapping can be designed, the supported dynamic table and
|
|
relocation subset must be specified with the same bounds.
|