Track startup MITM CA env#26314
Closed
winston-openai wants to merge 8 commits into
Closed
Conversation
This was referenced Jun 4, 2026
…tm-startup-ca-env # Conflicts: # codex-rs/network-proxy/src/certs.rs
…tm-startup-ca-env
… into dev/winston/mitm-startup-ca-env
…tm-startup-ca-env
…tm-startup-ca-env
…tm-startup-ca-env
Contributor
Author
|
Closing as superseded by the focused #29013 and #29014 stack. The replacement isolates the persisted MITM private key and preserves file-backed custom CAs present at Codex startup, with zero |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Child-specific CA material can only be handled safely if the proxy remembers which CA variables came from process startup and how relative paths were originally resolved.
What
SSL_CERT_DIR, and the startup working directoryStack
Validation
just test -p codex-network-proxy