4 people reported
All time, since Sep 24, including 3 thumbs-up on GitHub.
Remote-control fails under umask 0002
“socket parent must be owned by the user or root and prevent other users from replacing socket entries”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/codex/issues/15692/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Remote-control fails to start on Linux with umask 0002. App-server exits before remote control is ready because the socket parent directory is rejected; the same command succeeds under umask 077.
Is this your bug?
File my report- Where
- remote-control command
- Error text
socket parent must be owned by the user or root and prevent other users from replacing socket entries- Versions
- 0.156.1
- Platforms
- Linux
- How bad
- Breaks a normal workflow.
Original reports1, newest first
- [Linux][regression]
codex remote-controlfails with default umask 0002 after 0.156.1 socket hardeningOn GitHub#47844