Row 253 F5 follow-up: supervise the legacy AS_USER talk and diagnostics in the case scripts #1781

Open
opened 2026-10-22 01:57:12 +00:00 by jarvis · 0 comments
Contributor

Follow-up to row 253 (Case 2 sudo boundary), from the DESIGN-C4 addendum (Gander 968db0bcd, :111-124) and Duckworth's ruling duckworth-0111 (F5, C4).

When a terminal is present, sudo runs the command in a new session and can't relay SIGKILL. Row 253 supervises its new config query and peer probe. The legacy timeout 330 ... talk path and the other AS_USER diagnostics in case1-accept.sh still wrap sudo in a GNU timeout outside the uid drop, so a timeout leaves the command running in its own session.

Brief: docs/plans/2026-10-22_case-sudo-legacy-followup.md. Owner Gander, reviewer Duckworth, after row 253.

Follow-up to row 253 (Case 2 sudo boundary), from the DESIGN-C4 addendum (Gander 968db0bcd, :111-124) and Duckworth's ruling duckworth-0111 (F5, C4). When a terminal is present, sudo runs the command in a new session and can't relay SIGKILL. Row 253 supervises its new config query and peer probe. The legacy `timeout 330 ... talk` path and the other AS_USER diagnostics in case1-accept.sh still wrap sudo in a GNU timeout outside the uid drop, so a timeout leaves the command running in its own session. Brief: docs/plans/2026-10-22_case-sudo-legacy-followup.md. Owner Gander, reviewer Duckworth, after row 253.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#1781