You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
Cross-Session MessagingArea: what it touches
ImprovementsKind: in v2.1.225,
ImprovementsSection of the release
What
Ancestor verification for peer connections no longer treats a container init process as a legitimate ancestor, so a session running under PID 1 cannot be matched by accident.
Details
the Linux /proc ancestor walk now records a parent pid of 1 and stops there, where it previously discarded it by breaking at ppid <= 1
the array descendant helper returns false immediately for pid 1 (if (t === 1) return !1)
the cached lookup now requires process.pid !== 1 && i.includes(process.pid)
gated by platform: the ancestor walk reads /proc, so this is the Linux path
Evidence
[peer-cred] peer pid lookup failed
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
