Document runtime-confirmed CI signer selection and crypto reuse
This commit is contained in:
1 parent
40165ccbb2
commit
28f284be8f
3 files changed
+87
-7
No files matched your search
@@ -51,8 +51,10 @@ it should not be read as describing the corrected source unchanged.
|
||||
|
||||
## Requires the test VM or additional matching binaries
|
||||
|
||||
Live kernel testing is not available yet. Extracted VM artifacts, host mocks,
|
||||
and compilation do not close these:
|
||||
The first user-run kernel trace is available for Windows 11 22631 x64 with
|
||||
TESTSIGNING enabled. It confirms the BthPS3 signer-selection comparison and
|
||||
primary-signature CI path below. That one run, extracted artifacts, host mocks
|
||||
and compilation do not close the remaining work:
|
||||
|
||||
1. Run the paired `CiValidateFileObject` flag `0`/`0x20` probe on 19041/19045
|
||||
with TESTSIGNING off and a loadable signed test driver. Preserve complete
|
||||
@@ -77,8 +79,14 @@ and compilation do not close these:
|
||||
5. Measure signing-time propagation, zero/sentinel values, timestamp expiry,
|
||||
revocation freshness/network policy and weak-crypto policy. Record OS policy,
|
||||
Secure Boot/HVCI/WDAC and exact files, not just a boolean result.
|
||||
6. Establish multiple/nested signature-selection behavior with a signed corpus;
|
||||
extend supported PE gaps/overlays only after differential evidence.
|
||||
6. Extend the observed multiple/nested selection result beyond the first run.
|
||||
On Windows 11 22631 x64 with TESTSIGNING enabled, `0x20` returns Microsoft;
|
||||
`0xA0` and direct primary SHA-256 `CiCheckSignedFile` return Nefarius with the
|
||||
same signing time and matching signer/timestamp policy observations. All
|
||||
calls and policy statuses succeed, the file snapshots match, and no trace
|
||||
events are lost. TESTSIGNING-off, general enumeration, full `0x80` semantics
|
||||
and cross-build/policy behavior remain open. Extend supported PE gaps/overlays
|
||||
only after differential evidence.
|
||||
7. Resolve page-hash allocation destruction, normalized-entry/truncation meaning,
|
||||
terminal-entry handling and cross-version layouts before publishing a general
|
||||
page-hash API. `CiFreePolicyInfo` is not an established destructor for it.
|
||||
|
||||
Reference in new issue
Block a user