Prepare independently reviewed zlib-only image candidate
All checks were successful
Publish exact zlib-only remediation candidate / publish-candidate (push) Successful in 13s

Assistant: codex
Assistant-Model: gpt-6.1-sol
Assistant-Session: 01a126e1-76f8-7643-8cf3-e93336539ade
This commit is contained in:
tegwick 2026-10-11 11:36:02 +02:00
parent f0f89b6d1d
commit 9b4bb25d32
154 changed files with 29358 additions and 1 deletions

View file

@ -0,0 +1,61 @@
# Exact74 zlib candidate final Product acknowledgment
```yaml
reviewer: informed-decision-owner (agent informed-decision, codex)
decision: approved
work_item: INFD-WP-ADHOC-2026-10-11-T08
scope: exact local T05 source preparation after lower-layer whiteout correction
manifest_sha256: 724aa4777eb1c8976d868e5f504473f4b6d58f13d750d87aefa5c8d5ca0747ec
comment: >-
Same completed T08 preparation trial, with work-record refinement prepared
before this formal final acknowledgment. Initial5f334/intermediate8bc6 and
changes-requested85ffd remain exact historical reviews and evidence.
This is source technical agreement only, not publication/native go,
founder acceptance, scored new success or T05 completion.
```
All74 final staged hashes independently verify. Actual66-to74 changes remain
within artifact-audit source/tests/receipts/docs plus historical archive additions;
Containerfile/workflow/signed APK/index/pins/buildcontext, image78bfdcc/config625d,
package/runtime/backend/app/identity/policy, scanner DB/full scan/SBOM and WP
source scope remain unchanged from original preparation. Initial and intermediate
candidate source archives retain their exact manifest/bytes.
The checker separately collects current layer additions and lower-layer whiteout
removals/opaque prefixes. It filters only previous-layer state and merges the
current layer additions afterward, preserving them in either archive order.
This corrects the concrete Product finding: nested/root opacity and explicit
ancestor removal no longer delete new same-layer files. Five audit tests pass,
including12 whiteout cases for root/nested removal/opacity and reversed-order
replacements, optimized malformed before-read refusal and directory mode/UID/GID
refusals. The three original Product counterexamples are independently rerun
against frozen74 checker and all preserve new same-layer files.
[OCI layer specification](https://github.com/opencontainers/image-spec/blob/main/layer.md)
requires this lower-layer boundary and order-independent opacity handling.
Independent reread of existing actual local saved-image archives passes with
corrected reconstruction:313directories in each image, zero directory metadata
delta, exact final changes only libz/APK installed DB, nine base layers preserved,
effective runtime equality, only zlibr0 to r1 SBOM delta, and retained scan
base1MED/candidate0 at same database. No rebuild, container execution, scanner
repeat or native data/provider operation occurred in this review. Earlier source
checks of APK trust/bytes/backend/purpose remain applicable because their
artifacts/code are unchanged. Signature execution evidence remains retained maker
apk verify against exact763 trusted keys; no fresh Product crypto execution
claimed. Zero findings is bounded to that retained database snapshot, with
Alpine detector/EOL-list limitations; no estate risk grade or future guarantee.
Initial Product5f334 and intermediate8bc6 acknowledgments are historical, with
the latter subsequently refined after the explicit85ffd finding. The finding
and all its counterexample bytes remain under
`docs/evidence/2026-10-11-zlib-candidate-product-complete-review/changes-requested-85ffd628/`.
This exact74 acknowledgment resolves that finding without rewriting it as prior
success. No new privileged trial or human approval is inferred from refinements.
T05 remains progress, WP0009 active, manual follow-up due2026-10-18. Root exact
source review/commit, existing admitted owner CI candidate publication, actual
registry provenance/package/context and full published scan/SBOM proof precede
separate exact native founder release acceptance; installedr1/runtime/full-rescan
proof precedes T05 closure. Current763/nativec96 T04 result, DB/config/PVC/identity,
approved R2 helper/journal and INFD-IN-0010 unpromoted state remain untouched.
No owner checkout writes, publication, credential access or native commands.

View file

@ -0,0 +1,55 @@
# Exact amended zlib candidate Product confirmation
```yaml
reviewer: informed-decision-owner (agent informed-decision, codex)
decision: approved
work_item: INFD-WP-ADHOC-2026-10-11-T08
scope: exact amended local T05 source candidate preparation only
manifest_sha256: 64509029b3de6d33e3675587663ccdae027d9ea18aba83750892480766dd03b8
comment: >-
Same completed T08 preparation trial: work-record refinement was prepared
before this formal exact acknowledgment. Initial Product agreement/manifest
5f334 remains historical, including its bounded audit validation. This final
confirmation covers the guard refinement, not publication/native approval,
a second scored success or T05 completion.
```
All58 final staged hashes verify; all27 initial candidate snapshots match
immutable manifest8d345bb2. Actual initial-to-current diff changes only four
existing paths: artifact checker, its comparison and local-validation receipts,
and README. New audit tests/refinement record and original source archive are
additions. No Containerfile/workflow, signed APK/index/pins/four-file context,
package/runtime/backend/app/identity/policy artifact, scan/SBOM/DB or WP source
scope changed. Local daemon78bfdcc/config625d remain unpublished; source recipe
contextc554 and actual retained DB03cacb remain exact. Original four-source-test
and Product five negative-probe findings remain applicable, not needlessly rerun.
The artifact checker now refuses optimized Python before any archive/JSON read,
so assertions cannot silently disappear. Directory mode/UID/GID metadata is
included in final layer reconstruction and diff enforcement. Three new source
tests pass: malformed archive under -O refuses explicitly before reads; identical
directory metadata passes; each mode/UID/GID mutation refuses without a report.
These fixtures are isolated synthetic source tests. Independent reread of actual
existing local saved-image archives confirms equal directory counts and no
directory metadata delta; the same two final changed files are libz and APK DB,
nine base layers remain prefix and effective runtime config/SBOM/scan match.
No new image build, container launch, scan, customer/native data or provider call
was performed by this review.
Initial Product review and validation retain their exact bytes under
`docs/evidence/2026-10-11-zlib-candidate-product-final-review/initial-5f334757/`;
original current review file remains the initial agreement, with this separate
final acknowledgment carrying the refinement. Signature trust conclusions stay
bounded to pinned signed artifacts/unchanged trust metadata, actual retained
maker apk verify and enforced recipe; this acknowledgment does not claim fresh
cryptographic execution. Zero findings remains specific to retained sameDB scan,
not an estate risk grade or future safety assurance.
T05 remains progress, WP0009 active and manual follow-up due2026-10-18. Root
source review/commit and admitted owner CI candidate publication, exact actual
published registry provenance/package/full scan/SBOM, separate fresh native
founder release acceptance and installedr1/runtime/full-rescan proof remain
required. Existing approved R2 helper/journal, native image763, DB/config/PVC/
identity and T04/c96 outcome are unchanged. INFD-IN-0010 remains unpromoted and
unimplemented. This technical acknowledgment grants no native action, human
acceptance, credential capability or publication execution.

View file

@ -0,0 +1,74 @@
# Bounded zlib candidate Product owner review
```yaml
reviewer: informed-decision-owner (agent informed-decision, codex)
decision: approved
work_item: INFD-WP-ADHOC-2026-10-11-T08
scope: exact local zlib-only source candidate technical preparation
manifest_sha256: 8d345bb2bde3efce4d0cc99dfc2f883a64f79c42d2cd4abb288229a995e9ad66
comment: >-
Informed-decision intent requires human binding and preserved evidence; this
candidate changes only a native compression dependency while preserving
application authorization/presentation behavior. T08 review work record was
completed first. This is technical source agreement, not native go, publication
receipt, founder acceptance or T05 completion.
```
All27 staged hashes and retained evidence-file hashes independently verify.
Independent saved-image archive readback confirms all nine exact763 base diff_ids
as prefix, equal effective runtime configuration with only explicitly normalized
empty/false/null defaults, and final filesystem changes exactly
`usr/lib/libz.so.1.3.2` and `lib/apk/db/installed`. Modes/owners remain equivalent.
Application36 files, policy9d7, trust keys, APK world, Python dependencies, OpenSSL
and UID/GID10001 remain equal. Root build identity returns to10001:10001.
No service values, namespace, DB, customer data, config, PVC, schema, audience,
policy pins, protected helper or existing release journal is changed.
Package/index bytes match pinned official HTTPS download hashes. Both signed
archives name alpine-devel@lists.alpinelinux.org-6165ee59.rsa.pub, already present
in unchanged baseline trust metadata. Retained actual maker apk verify success
against exact763 installed keys is the execution evidence; this review separately
checks archive signatures' metadata, bytes and trust identity, without claiming
a new signature-verification execution. Containerfile requires digest checks and
`apk verify` success before offline named-package upgrade; no allow-untrusted or
keys-dir override. Existing trusted keys are not replaced.
[Official apk verify documentation](https://github.com/alpinelinux/apk-tools/blob/master/doc/apk-verify.8.scd)
defines integrity/signature checking and nonzero failure.
Upgrade selects only zlib from retained local signed index, disables network,
preupgrade and logging, and removes temporary public artifacts.
Both full CycloneDX/Trivy artifacts independently show44 packages and only
zlib1.3.2-r0 to1.3.2-r1 version delta. Full baseline has one MEDIUM
CVE-2026-85091; candidate has zero findings at the retained same database
03cacb40452ceb74afdfca072cb82f79ee884dfac006ef24a4dfdad133b0f917.
No severity suppression is inferred or permitted. Alpine3.24 EOL-list warning
and actual38 OS/6 Python detector coverage remain disclosed. This is bounded
scan improvement at that snapshot, not estate risk grading or future safety.
Local daemon image78bfdcc and saved OCI config625d are distinct disclosed
representations; neither is a published registry digest or native image proof.
Four existing source tests pass, covering eight mutations; five additional Product
mutations of app source, trust keys, APK world, network and provider/data flags
refuse. Independent archive/SBOM/scan readback agrees with maker artifact receipt.
Retained four compression vectors/three malformed refusals/crypto/JWT/waitress
and ten installed purpose variants are local synthetic checks, not live PDP
or customer/native-data testing. No new container or native execution by reviewer.
Workflow publishes only a source-bound candidate through existing admitted owner
registry capability after root source review/commit: exact40hex source revision,
fixed owner archive, four input hashes/contextc554, exact763 base, no-network
bounded build, unchanged runtime comparison and purpose checks before push.
It has no kubectl, Argo, DB/admin, namespace or runtime deployment action.
The workflow is unexecuted; source review does not attest CI credentials, actual
publication or published artifact equivalence. Root must retain actual CI/source
revision and registry descriptor/layer/config/package/signature/context readback,
then full published scan/SBOM and scoped candidate release preparation. Only
distinct exact informed-decision founder native approval followed by installedr1,
runtime/purpose and full-rescan proof can close T05. Future image-only rollback
to763 preserves latest DB; no historical snapshot restore.
T05 remains progress, WP0009 active, manual follow-up due2026-10-18; no automatic
controller is implied. T04/c96 accepted outcome and original uncertain journals
remain historical and immutable. INFD-IN-0010 is unchanged and unpromoted.
No new native authority, owner checkout write, credential/login, deployment or
customer-data access occurred in this review.

View file

@ -0,0 +1,37 @@
# Exact66 zlib audit whiteout Product finding
```yaml
reviewer: informed-decision-owner (agent informed-decision, codex)
decision: changes_requested
work_item: INFD-WP-ADHOC-2026-10-11-T08
scope: exact66 local candidate artifact-audit source refinement
manifest_sha256: 3e41ab391cda26f09a556fecef8a17c2759ef2899e43eb136b25ef4b3fde23a0
comment: >-
Same completed T08; work record prepared before this formal finding.
No actual candidate-image failure or new scored/native trial. Preserve
initial5f334 and intermediate8bc6 acknowledgments as historical.
```
All66 staged hashes independently verify. Whiteout leading-dot and root opaque
handling corrections address the prior cases, but remaining stream-order behavior
violates the lower-layer boundary. A synthetic parent layer contains usr/child/old;
next layer writes a new file before its whiteout marker. Three retained isolated
probes reproduce incorrect deletion: usr/new then usr/.wh..wh..opq, root new then
.wh..wh..opq, and usr/child/new then usr/.wh.child. Actual parsed sets lose the
same-layer new file in every case. Frozen checker/manifest and reproducible
probe/receipt are retained under docs/evidence/2026-10-11-zlib-candidate-product-whiteout-review/.
[OCI layer specification](https://github.com/opencontainers/image-spec/blob/main/layer.md)
requires whiteouts to affect only parent layers and opacity to precede new entries
regardless archive ordering. Correct reconstruction should apply whiteouts to
the prior layer state and then merge current layer additions, preserving both
marker-before and marker-after order semantics. Add meaningful root/nested opaque
and explicit-directory removal cases with same-layer children/replacements.
The existing four no-new-sibling cases cannot establish this boundary.
This finding is confined to audit-source semantics, not APK trust or actual image
contents/build/scan. Current actual candidate image/context/package/workflow/
runtime and scanner evidence remain unchanged; no native/read-only command or
customer/DB/credential access occurred. T05 remains progress/WP0009 active;
publication and distinct founder native release/installed proof remain pending.
A corrected exact frozen packet needs final technical confirmation.