-
Notifications
You must be signed in to change notification settings - Fork 12.9k
fix(config): use deny for Unix socket permissions #24970
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
noneparsing for socket deniesFor any existing user/profile config that already has
[permissions.*.network.unix_sockets]entries set to"none", this enum now deserializes only"allow"/"deny", so Codex will reject the config during startup instead of treating that entry as a denied override. The new outward spelling can still be"deny", butDenyshould keep a#[serde(alias = "none")]compatibility alias here and on the mirrored managed/feature/proxy config enums, matching the filesystem permission migration pattern.Useful? React with 👍 / 👎.