Stabilize diagnostic export and preserve authorized policy continuity
This commit is contained in:
1 parent
0a5df7398e
commit
09bf616d98
18 files changed
+364
-57
No files matched your search
@@ -4,6 +4,25 @@ Status: source patch prepared and checked; **not compiled or runtime verified**.
|
||||
Do not distribute this patch as a proven security fix until the acceptance gates
|
||||
below pass against the resulting binary.
|
||||
|
||||
## Latest stable candidate checked
|
||||
|
||||
The official [Electron44.7.1 release](https://github.com/electron/electron/releases/tag/v44.7.1)
|
||||
uses Chromium152.0.7977.149. Its Windows x64 ZIP was downloaded into an isolated
|
||||
ignored directory, checked against the official SHA256 manifest and extracted
|
||||
with contained-path, symlink and size checks. ZIP SHA256:
|
||||
`ace7ce1580d33e9fe7284823d7e23ba687263c448d85d8dc4b5daa9bba73f97a`.
|
||||
|
||||
Actual positive controls in fresh profiles transmitted synthetic RTC bytes and
|
||||
a benign HTTPS submission from both initial about:blank and srcdoc frames.
|
||||
The matching managed header cases still terminated their renderers with
|
||||
missing `network.mojom.MdnsResponder`, bad IPC123 and exit3. The tagged binder
|
||||
source also lacks `NoOpP2PSocketManager`. Therefore this available stable binary
|
||||
does not resolve the gate. Project dependencies remain unchanged.
|
||||
|
||||
Ignored evidence: `artifacts/electron4471-binary-proof.json`. The first run's
|
||||
about:blank positive timeout remains retained; a separate profile-isolated
|
||||
paired run verified both controls without changing attempts or deadlines.
|
||||
|
||||
## Exact basis and provenance
|
||||
|
||||
The adjacent patch targets Chromium `152.0.7977.130`, used by Electron `44.7.0`.
|
||||
|
||||
Reference in new issue
Block a user