1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
//! Binding a socket exactly one process at a time may own (#5182).
//!
//! Why: a console-supervised child is spawned, killed, and respawned on demand,
//! and a child that dies without unlinking its socket leaves a file that makes
//! the next `bind` fail with `EADDRINUSE`. [`super::bind_hardened`] deliberately
//! does NOT unlink for it — folding an unconditional unlink in there would let
//! any process silently steal a socket another one is live on. So the
//! probe-then-take-over decision belongs in its own entry point, where the
//! condition it turns on is stated once.
//!
//! What: [`bind_singleton_hardened`] asks whether anything is actually
//! answering. If something is, it refuses rather than clobbering a live owner.
//! If nothing is, the file is a corpse: it is unlinked and rebound through
//! [`super::bind_hardened`], so the replacement is `0600` in a `0700` directory
//! exactly as a first bind would be.
//!
//! 🔴 The takeover fires ONLY on [`SocketVerdict::NotServing`], the verdict the
//! kernel actually proves (ENOENT / ECONNREFUSED), **and only when the path is
//! a socket to begin with**. An ambiguous probe —
//! [`SocketVerdict::Inconclusive`] — is treated as a live owner and refused.
//! The asymmetry is the point: refusing a dead socket costs one failed start
//! that a retry fixes, while unlinking a live one strands its owner on an
//! inode nothing can reach.
//!
//! 🔴 The file-type half of that rule is load-bearing and was missing until
//! #7312. Linux and macOS disagree about which errno a connect to a NON-socket
//! returns: macOS/BSD `unp_connect` answers `ENOTSOCK`, which classifies as
//! `Inconclusive` and refuses, while Linux's `unix_find_other` sets
//! `-ECONNREFUSED` before its `S_ISSOCK` test, which classifies as
//! `NotServing` and licensed an unlink. So on Linux a daemon pointed at a path
//! holding an ordinary file deleted that file and bound over it. The probe
//! cannot be made to answer this — `lstat` can, and does, first.
//! [`super::verify_socket_for_connect`] has always applied that rule on the
//! dialing side; this is its missing half on the binding side.
//!
//! The probe is a bare `connect`, not [`super::connect_hardened`], and that is
//! deliberate. The question here is only "is a process serving this path", and
//! a verification failure (wrong mode, wrong owner) does not answer it — a live
//! server with a wrong-mode socket would be misread as a corpse and unlinked
//! out from under itself.
//!
//! 🔴 Invariant (#8759): every caller runs its whole lstat → probe → unlink →
//! bind → listen sequence while holding an exclusive, non-blocking `flock` on
//! `<socket>.lock`. Without it, two starters could both prove the same corpse
//! dead and both unlink and bind — the second unlinking the first's fresh
//! socket — or one could probe the other's socket in the gap between `bind`
//! and `listen`, where a connect is refused, and read it as a corpse. Either
//! way both returned `Ok` and both served. Under the lock, a binder sees only a
//! socket another binder finished listening on, so the probe refuses it; a
//! binder that finds the lock held refuses with
//! [`UdsSecurityError::BindInProgress`]; and one that cannot take the lock at
//! all refuses with [`UdsSecurityError::BindLock`] instead of binding unlocked.
//! The lock file is never removed: unlinking it while another process has it
//! open would let a third lock a fresh inode alongside. Like the socket path,
//! the lock path is never followed through a symlink, and anything but a
//! regular file there refuses with [`UdsSecurityError::BindLock`].
//!
//! `trusty-agents`' `CtrlSocket::bind_singleton` predates this and still carries
//! its own copy; migrating it is a separate change, not a side effect of one
//! that adds two new bind sites.
//!
//! Test: `tests.rs` — `bind_singleton_*` and `takeover_verdict_*`.
use ;
use OpenOptionsExt;
use ;
use Duration;
use UnixListener;
use ;
use ;
/// How long the takeover probe waits for an answer.
///
/// A local socket answers or refuses in microseconds, so a full second is not a
/// latency budget — it is headroom, so that `Inconclusive` means "the kernel
/// would not answer" rather than "this machine was busy". The supervisor's
/// 200 ms liveness probe runs per request and cannot afford that; this runs
/// once per process start and can. A starved 200 ms probe here read as
/// `Inconclusive` and refused a genuinely stale socket, which is safe but
/// wrong.
const PROBE_TIMEOUT: Duration = from_secs;
/// What [`bind_singleton_hardened`] must do about a path that already exists.
///
/// Why a named decision rather than an inline `match`: the two refusal arms are
/// awkward to reach through real syscalls — `Inconclusive` needs a socket whose
/// connect neither completes nor is refused, and `NotASocket` needs a kernel
/// that reports the file type through the errno, which macOS does and Linux
/// does not. Separating the decision from the syscalls makes every arm testable
/// unprivileged on either platform, the same reason
/// [`super::dir::DirVerdict`] exists.
///
/// Test: the `takeover_verdict_*` tests in `tests.rs`.
pub
/// Decide whether an existing path may be unlinked and rebound.
///
/// Why: see [`TakeoverVerdict`]. The file type is checked FIRST and outranks
/// the probe, because on Linux the probe's answer for a non-socket is
/// indistinguishable from its answer for a dead socket (#7312).
/// What: `NotASocket` whenever `is_socket` is false, whatever the probe said;
/// otherwise `TakeOver` on the one verdict the kernel proved, `Occupied` on
/// every other. `verdict` is `None` when the caller skipped the probe because
/// the path is not a socket — a non-socket occupant costs no `connect`, since
/// the errno one would return is the very thing that misread it.
/// Test: `takeover_verdict_refuses_a_non_socket_even_when_the_probe_says_dead`,
/// `takeover_verdict_refuses_a_non_socket_that_was_never_probed`,
/// `takeover_verdict_takes_over_a_dead_socket`,
/// `takeover_verdict_refuses_a_served_socket`,
/// `takeover_verdict_refuses_an_inconclusive_probe`.
pub
/// Bind `path`, taking over a socket file no process is serving.
///
/// # Errors
///
/// [`UdsSecurityError::AlreadyServing`] when another process answers the path,
/// or when the probe cannot settle the question — a caller must not proceed,
/// because two listeners on one socket means every delivery goes to whichever
/// the kernel picks. [`UdsSecurityError::NotASocketFile`] when the path holds
/// something that is not a socket, which this function refuses rather than
/// deletes (#7312). [`UdsSecurityError::BindInProgress`] when another process
/// holds the bind lock, and [`UdsSecurityError::BindLock`] when the lock cannot
/// be taken at all (#8759). Otherwise any [`super::bind_hardened`] error.
///
/// Test: `bind_singleton_takes_over_a_stale_socket_file`,
/// `bind_singleton_racing_takeover_leaves_exactly_one_owner`,
/// `bind_singleton_refuses_while_another_binder_holds_the_lock`,
/// `bind_singleton_fails_closed_when_the_bind_lock_cannot_be_opened`,
/// `bind_singleton_refuses_a_symlink_to_a_file_at_the_lock_path`,
/// `bind_singleton_releases_the_bind_lock_when_it_returns`,
/// `bind_singleton_refuses_a_socket_someone_is_serving`,
/// `bind_singleton_refuses_a_regular_file_and_leaves_it_on_disk`,
/// `bind_singleton_hardened_refuses_a_symlink_to_a_dead_socket`,
/// `bind_singleton_hardened_refuses_a_symlink_to_a_live_socket`,
/// `bind_singleton_binds_a_fresh_path`.
pub async
/// [`bind_singleton_hardened`]'s body, with a hook run after the takeover
/// decision and before the unlink.
///
/// Why: the #8759 race lives between "the probe proved this socket dead" and
/// "unlink it and bind"; a test forces a second binder into exactly that gap
/// by running it inside `before_takeover`, with no sleep standing in for the
/// interleaving.
/// What: identical to [`bind_singleton_hardened`]; `before_takeover` runs only
/// on the [`TakeoverVerdict::TakeOver`] arm.
/// Test: `bind_singleton_racing_takeover_leaves_exactly_one_owner`.
pub async
/// Take the exclusive, non-blocking bind lock beside `path`.
///
/// Why: #8759 — see the invariant in the module doc. Like every other path
/// this module touches (#7312), the lock path must never be followed through a
/// symlink: a followed link would create and lock the link's target instead.
/// What: opens `<path>.lock` with `O_NOFOLLOW` (created `0600`, never
/// truncated, never removed), refuses the descriptor unless `fstat` says it is
/// a regular file, then `try_lock`s it. Contention is
/// [`UdsSecurityError::BindInProgress`]; a symlink, a non-regular file, or any
/// I/O failure is [`UdsSecurityError::BindLock`] naming the lock path. The
/// returned file holds the lock until dropped.
/// Test: `bind_singleton_refuses_while_another_binder_holds_the_lock`,
/// `bind_singleton_fails_closed_when_the_bind_lock_cannot_be_opened`,
/// `bind_singleton_refuses_a_symlink_to_a_file_at_the_lock_path`,
/// `bind_singleton_refuses_a_dangling_symlink_at_the_lock_path`,
/// `bind_singleton_refuses_a_symlink_to_a_directory_at_the_lock_path`,
/// `bind_singleton_refuses_a_fifo_at_the_lock_path`,
/// `bind_singleton_releases_the_bind_lock_when_it_returns`.
/// Reword a failed lock-file `open` by what occupies the lock path.
///
/// Why: `O_NOFOLLOW` reports a symlink as `ELOOP` (`EMLINK` on FreeBSD) and a
/// directory as `EISDIR`, neither of which says why the bind was refused.
/// What: an `lstat` of `lock_path` picks the message — a symlink or any other
/// non-regular file gets a named reason; anything else keeps the OS error. The
/// `open` already refused; this stat decides only the wording, never the
/// outcome.
/// Test: `bind_singleton_refuses_a_symlink_to_a_directory_at_the_lock_path`,
/// `bind_singleton_fails_closed_when_the_bind_lock_cannot_be_opened`.
/// The error for a lock path held by something other than a regular file.
/// `<path>.lock`: the bind lock's file, beside the socket it guards.
pub