You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Diagnose the local TLS trust-store discrepancy without weakening pinning #18
On the local Python 3.12.14 host, the test observes two trusted roots after loading its fixture, although it expects one. An otherwise empty client SSL context already contains an environment root. The same failure was reproduced on original PR revision c244c8c and main 416cc81; the published correction at 9ddf79a passed all 24 hosted CI checks.
Acceptance criteria
Capture a minimal reproduction and the Python/OpenSSL/runtime configuration needed to explain the additional root, without dumping credentials or unrelated environment values.
Compare the affected host with a clean runtime and identify the source of the additional trust anchor.
Document the diagnosis and a supported isolated test environment, or implement a narrowly scoped correction if a production defect is demonstrated.
Preserve assertions for the intended pinned root, hostname checks, rejection of untrusted certificates, and environmental control behavior.
Run the focused transport tests and full suite on any changed implementation, recording exact revisions and results.
Keep the current assertion active. Do not broaden accepted trust roots, disable verification, or skip the test to obtain a green result.
This is an inherited host-specific discrepancy, not a demonstrated regression in #16. It is a bounded follow-up and does not block the currently green hosted merge candidate.
Verification update — 16 November 2026 (AI-assisted, owner-authorized).
PR #20 merged as e48a75a331b61cfa7f0b861805f485a0e5c47bc5. The dated diagnosis and read-only diagnostic preserve the existing trust-root, hostname, untrusted-certificate and environment-control assertions.
The owner confirmed that the Python 3.12.14 failure ran in another environment and that environment is currently unrecoverable. On the current Python 3.15.2 workstation, empty contexts contain zero trusted roots; the six focused transport tests pass normally and with -I -S. All seven pinned hosted Python lanes passed the full 399-test suite on merged main, including the unchanged TLS assertions: merged-main CI.
Status: currently unreproduced; historical cause unknown. The supported current environments pass, but this does not identify the injecting component or demonstrate a repair to the unavailable host. The diagnostic is ready to capture runtime and trust-root fingerprints if the discrepancy recurs, without loading CAs, making network requests, or printing environment values.
Keep this issue open under its existing diagnosis criteria. No assertions were broadened or skipped, and no production TLS change was needed.
Activity
Merge PR #16: gated Experiment 2 and evidence corrections
Merge pull request #20: verify recovered evidence and runtime behavior
k2jac9 commentedon Nov 16, 2026
Verification update — 16 November 2026 (AI-assisted, owner-authorized).
PR #20 merged as
e48a75a331b61cfa7f0b861805f485a0e5c47bc5. The dated diagnosis and read-only diagnostic preserve the existing trust-root, hostname, untrusted-certificate and environment-control assertions.The owner confirmed that the Python 3.12.14 failure ran in another environment and that environment is currently unrecoverable. On the current Python 3.15.2 workstation, empty contexts contain zero trusted roots; the six focused transport tests pass normally and with
-I -S. All seven pinned hosted Python lanes passed the full 399-test suite on merged main, including the unchanged TLS assertions: merged-main CI.Status: currently unreproduced; historical cause unknown. The supported current environments pass, but this does not identify the injecting component or demonstrate a repair to the unavailable host. The diagnostic is ready to capture runtime and trust-root fingerprints if the discrepancy recurs, without loading CAs, making network requests, or printing environment values.
Keep this issue open under its existing diagnosis criteria. No assertions were broadened or skipped, and no production TLS change was needed.