Repository navigation
fix(tokio): check Unix allowlist before qmux negotiation - #6907
Conversation
Quest-Claim: 41a5e764944505d9
Co-Authored-By: GPT-6 <noreply@openai.com>
Co-Authored-By: GPT-6 <noreply@openai.com>
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 19 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
kixelated
left a comment
There was a problem hiding this comment.
Automated review by review (OpenAI)
Reviewed commit: e21ded1
No actionable bugs found in the changed code and relevant surrounding paths. Moving the existing kernel-credential allowlist check ahead of qmux::uds::accept closes the intended parser-exposure gap without changing the public API or allowed-peer negotiation. The private pending-handshake boundary is a straightforward solution; independent tasks, deadlines, drain handling, and credential-matching semantics remain intact. The new real-socket test covers both refusal before negotiation bytes and successful allowed-peer ALPN negotiation.
Verification limits: source review through GitHub only; I did not run tests or independently reproduce the PR's reported CI results.
|
Merge summary for e21ded1:
(Written by Claude Opus 5.5) |
Problem
A Unix listener checked its configured UID/GID/PID allowlist only after QMux's in-band handshake. A refused local user could reach the negotiation parser despite failing the credential gate.
Approach
Check kernel peer credentials in the private pending Unix handshake before calling
qmux::uds::accept. Keep the same allowlist matcher, independent connection tasks, and handshake deadline. The current consumer is the server's configured Unix listener.Impact
Listener::acceptretains its existing behavior; the server passes its configured allowlist through a private method.Validation
64).moq-lite-06, stalled handshake concurrency, shutdown, and configured publisher path. No sleeps, new timeout, host user changes, or mocked credentials.just fixstops at the unchangedrs/moq-mux/benches/catalog.rs:226reference to nonexistenthang::catalog::MAX_RENDITIONS. Only the two changed source files were then formatted;git diff --checkpasses.nix develop --command just cipasses one21ded1cc0c5a85d28f362e5e3c821df996ec0cbin 274 seconds, including strict Rust feature extremes, transport boundary checks, 5,341 Rust tests (85 skipped), and repository tooling. The new refusal test passes in that full run. No runner-image/UID-map check was selected for this diff.Alternatives
Keeping the check after transport negotiation leaves the parser reachable. Moving it to the existing private socket-to-handshake boundary avoids a new public allowlist API.
Follow-ups
The benchmark compile error also blocks moq-dev/moq#6902 and moq-dev/moq#6898. An open-PR search found no dedicated repair. Repair it independently; it is outside the UDS boundary change. The required clean-head
just cipasses, and the changed source formatting is verified.(Written by GPT-6)