12 KiB
SEC-07 · Exact package candidate and compatibility acceptance
Status: published delivery accepted after independent review 6b371be, exact dependency-first publication and fresh official-feed verification. Only Abstractions0.6.6 and UI1.0.0 were published. No application was deployed and no production secret or connection was used.
Frozen source and minimal package set
Clean package-input revision: bd257c68274cd9a9d2e718c89f5e728ec7926bd2. Both SourceRevisionId and RepositoryCommit were explicitly set to that revision, independent of later shared-worktree commits. SDK: 10.0.403, Release, deterministic/CI build. Source acceptance: SEC07-source.trx 81 passed, 0 failed, 0 skipped. The project-level UI version is 1.0.0; Directory.Build.props remains 0.6.6. Core and backends are not part of this release.
| Exact artifact | SHA-256 |
|---|---|
| ZB.MOM.WW.Secrets.Ui.1.0.0.nupkg | 346c32acb0166c2704465fa7b9cec31c8f58af2d2a37296e03c0021fe50d7815 |
| ZB.MOM.WW.Secrets.Abstractions.0.6.6.nupkg | 5cb0386469638bda89eb6c9afa25ead397b86730c3c5e43e4e496269d316acdc |
Artifacts are in ZB.MOM.WW.Secrets/artifacts/ui-consistency/. SEC07-artifacts.json records full paths, archive entries, dependency IDs/floors and repository metadata. UI floors: Abstractions0.6.6, Theme1.0.1, Audit0.1.0, Auth.AspNetCore0.1.4, Novell.Directory.Ldap.NETStandard3.6.0. The existing LDAP promotion was also present in published UI0.6.2. Abstractions has no package dependencies. UI contains both new module assets, exact frozen-source bytes, and no duplicate ZIP entries. The official Theme1.0.1 package hash is 995b117b0245577598c91404ed7957c071ebe3413696c8be48b419c9deb1bd5d.
The exact UI/Abstractions target versions were absent from the official feed at the recorded SEC07-preflight-collisions.json time. Recheck immediately before publication; do not overwrite an existing version.
Packaging and isolated restoration
The library was exported from the frozen commit into a clean temporary archive, with its filesystem root canonicalized using Path.resolve() before invoking NuGet. Each of these two exact project paths was restored using official-NuGet.Config and isolated /tmp/scada-secrets-theme101-official-packages, then packed:
dotnet pack src/ZB.MOM.WW.Secrets.Abstractions/ZB.MOM.WW.Secrets.Abstractions.csproj -c Release --no-restore -o /Users/dohertj2/.codex/worktrees/scada-ui-consistency/scadaproj/ZB.MOM.WW.Secrets/artifacts/ui-consistency -p:ContinuousIntegrationBuild=true -p:Deterministic=true -p:SourceRevisionId=bd257c68274cd9a9d2e718c89f5e728ec7926bd2 -p:RepositoryCommit=bd257c68274cd9a9d2e718c89f5e728ec7926bd2 -p:RepositoryType=git
dotnet pack src/ZB.MOM.WW.Secrets.Ui/ZB.MOM.WW.Secrets.Ui.csproj -c Release --no-restore -o /Users/dohertj2/.codex/worktrees/scada-ui-consistency/scadaproj/ZB.MOM.WW.Secrets/artifacts/ui-consistency -p:ContinuousIntegrationBuild=true -p:Deterministic=true -p:SourceRevisionId=bd257c68274cd9a9d2e718c89f5e728ec7926bd2 -p:RepositoryCommit=bd257c68274cd9a9d2e718c89f5e728ec7926bd2 -p:RepositoryType=git
Cwd is the canonical archived ZB.MOM.WW.Secrets directory recorded in SEC07-artifacts.json; NUGET_PACKAGES is the isolated official cache above. No CLI Version override was used. Retained restore/pack logs show zero warnings/errors. NuGet archive timestamps are not asserted reproducible; source, repository metadata and actual accepted bytes are pinned.
candidate-NuGet.Config maps only the two exact candidate IDs to the local feed, remaining ZB.MOM.WW.* to the official feed and public packages to NuGet.org. No credentials are committed. compatibility/ui-only/UiSmoke.csproj explicitly references only UI1.0.0 and Theme1.0.1; a fresh isolated restore inferred Abstractions0.6.6 and built with zero warnings/errors. SEC07-ui-only-inference.json verifies both cached candidate hashes and their local source. This proves the published dependency floor, rather than a masking explicit contracts pin.
Actual old-binary compatibility: 66/66
compatibility/legacy/LegacyProvider.csproj was compiled against the published Abstractions0.6.2. Runner references that resulting DLL directly, not its project. The provider has no concrete GetSnapshot member. It was not rebuilt against new contracts.
compatibility/runner/Compatibility.csproj runs once with CoreVersion=0.6.2, once with CoreVersion=0.6.3, loading the actual published matching Core, SQL replicator and Akka replicator packages. Each run passed 33 checks, including:
- default interface snapshot dispatch on the old-compiled provider; owned snapshot zeroing on disposal without corrupting the provider buffer;
- normalization and exact450/451 name boundary; actual older AES envelope encrypt/decrypt, maximum valid name, tampered-tag rejection, name AAD rejection and KEK rewrap;
- actual older SQLite migration/persistence, initial revision0 then increment/preserved creation, metadata, tombstone retention/exclusion and no synthetic plaintext in stored bytes;
- actual SQL replicator forwarding to an in-process hub and actual SQL store interface mapping; actual Akka encrypted-row DTO roundtrip and local actor mailbox;
- all exported types loading and exact UI/contracts/Theme informational revisions.
The runner explicitly pins the existing patched public dependency line: Microsoft.Data.Sqlite10.0.13, native SQLite2.1.13, Pkcs9.0.21. This is part of the tested compatibility graph, not a claim that every older downstream dependency graph is secure or supported. The old implementation nupkgs remain unchanged. Both transitive vulnerability audits returned no findings; no suppression or skipped check was added. SEC07-core{062,063}-{graph,audit,runtime}.json retains graphs, audit results and each runtime check. SEC07-compatibility-package-bytes.json verifies all12 runtime UI/contracts/Theme/old implementation DLLs against exact package bytes/source metadata.
Reproduction, cwd this validation directory; use isolated NUGET_PACKAGES=/tmp/scada-secrets-compat-packages:
dotnet restore compatibility/legacy/LegacyProvider.csproj --configfile official-NuGet.Config
dotnet build compatibility/legacy/LegacyProvider.csproj -c Release --no-restore
# Repeat with CoreVersion=0.6.3 after recording the first runtime hashes.
dotnet restore compatibility/runner/Compatibility.csproj --configfile candidate-NuGet.Config -p:CoreVersion=0.6.2
dotnet build compatibility/runner/Compatibility.csproj -c Release --no-restore -p:CoreVersion=0.6.2
dotnet run --project compatibility/runner/Compatibility.csproj -c Release --no-build --no-restore -p:CoreVersion=0.6.2 -- 0.6.2 bd257c68274cd9a9d2e718c89f5e728ec7926bd2 SEC07-core062-runtime.json
dotnet list compatibility/runner/Compatibility.csproj package --include-transitive --format json
dotnet list compatibility/runner/Compatibility.csproj package --vulnerable --include-transitive --format json
These are synthetic fixed keys, ephemeral SQLite and local-only Akka. There was no SQL connection, remote/cluster deployment, real key provider rotation or production inventory. The added450-character limit is a validation delta: longer existing names/tombstones need a host inventory decision before Abstractions adoption. A rotating provider must implement an atomic snapshot itself if required; the legacy DIM cannot promise atomic rotation of separate legacy getters.
Packaged two-host browser acceptance: 44/44
Both hosts restored/built against package UI1.0.0 from a fresh /tmp/scada-secrets-ui100-host-packages cache; there is no UI ProjectReference in package mode. Per-page host links the actual OtOpcUa wrapper and its Bootstrap; the global host uses ScadaBridge Bootstrap. Final synthetic origins were http://127.0.0.1:63037 and http://127.0.0.1:63038 (OS-assigned loopback ports). SEC07-host-*-{restore,build}.log records zero-warning builds. packaged_smoke.py and SEC07-packaged-browser.json record 22 checks per host, no page errors:
- exact UI/Theme identity; all7 downloaded CSS/font/module assets equal accepted package bytes;
- one live route, filtering/clear, all four field associations, invalid-name focus and target draft isolation;
- reveal/hide with non-sensitive status, fail-closed audit failure;
- saved outcome despite audit/refresh failure, metadata-only Retry with unchanged mutation count;
- native modal safe initial focus, Tab containment, Escape and scroll cleanup without delete;
- manage-only cannot reveal; denied role HTTP403.
The preceding source matrix remains accepted: 93/93 rendered checks,1440/390px and native browser200% zoom, long metadata, reduced motion, real focus, Bootstrap composition and measured contrast5.144–16.877:1; see SEC05-06-confirmation/results.json. No additional broad screenshot/polish loop was needed for unchanged packaged DOM.
Retained diagnostic evidence is explicit. First package smoke read associations immediately after a Blazor click and caught the pre-render DOM in global mode; its failure is retained as SEC07-packaged-browser-initial.*. Waiting for the actual rendered name control produced all44 passes, with no source change. A first compatibility helper assumed SQLite insert revision>0; actual contract begins0, so the helper was corrected to assert0 then increment, retaining SEC07-core062-initial-runtime.log.
A rejected first archive used /var while NuGet canonicalized project references to /private/var; UI pack omitted its Abstractions floor. That output was rejected and moved outside the candidate feed (artifacts/ui-consistency-rejected-var-alias/); SEC07-initial-packaging-failure.json records the evidence. Canonicalizing the clean archive root repaired the graph without altering source/version. Earlier shared-cache contamination of an unpublished Theme candidate was also detected by byte checks; final source and package proofs use the exact official Theme hash in isolated caches. No failure was hidden by audit suppression.
Independent review and release completion
Parent must independently inspect the two nupkgs/nuspecs, frozen source, hashes and dependency/compatibility proof before publication. Publish exactly these two accepted artifacts through the established process only after approval and a new collision check. Then independently download both official artifacts, compare both SHA-256 values and repeat UI-only plus integration-host restoration from an empty official-only cache, with no candidate source. Until that official-feed proof passes, consumers must not adopt the new package pins.
Rollout adopts UI1.0.0/Abstractions0.6.6/Theme1.0.1 together, preserving reviewed Core/backends. Preserve previous immutable artifacts. Rollback UI/assets together; never replay mutations, remove tombstones or change encryption/storage format as a UI rollback. Preserve target-isolation corrections when feasible.
Published delivery completion
Independent parent review 6b371be accepted exact nuspec/source/README/module/runtime parity.
Immediate preflight rechecked both hashes and official target404s; Abstractions0.6.6 was pushed
first, then UI1.0.0, with exact paths and no repack, wildcard, skip-duplicate or backend release.
Fresh independent official GETs matched both reviewed hashes (SEC07-publication.json).
A new empty /tmp/scada-secrets-ui100-official-delivery-packages cache restored and built
UI-only, per-page and global host projects using only official-NuGet.Config. All libraries
were package assets, candidate sources absent, and exact UI/Abstractions/Theme bytes and official
.nupkg.metadata source verified (SEC07-official-delivery.json). Rebuilt official-feed hosts
on OS-assigned ports63782/63793 passed 44/44 focused browser/asset checks with no page errors
(SEC07-official-browser.json); no local candidate source/build fallback was used.
The delivery gate is complete: consumer reviewed pins may now adopt UI1.0.0/Abstractions0.6.6/
Theme1.0.1, subject to the documented name-limit and host runtime caveats. Source package identity
remains bd257c68274cd9a9d2e718c89f5e728ec7926bd2. All owned canaries were stopped after acceptance;
no temporary credential config was created or retained. The committed NuGet configurations
contain source mapping only, no credentials. Existing system credentials were not modified.