{"version":"2.1.225","anchor":"pid-1-no-longer-counts-as-an-ancestor-when-verifying-a-peer-","canonical_anchor":"pid-1-no-longer-counts-as-an-ancestor-when-verifying-a-peer-","heading":"PID 1 no longer counts as an ancestor when verifying a peer connection","tier":"notice","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/pid-1-no-longer-counts-as-an-ancestor-when-verifying-a-peer-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### PID 1 no longer counts as an ancestor when verifying a peer connection\n\nSessions running as the main process in a container no longer get wrongly matched to peer connections.\n\n**What**\n\nAncestor 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.\n\n**Details**\n\n- 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`\n- the array descendant helper returns false immediately for pid 1 (`if (t === 1) return !1`)\n- the cached lookup now requires `process.pid !== 1 && i.includes(process.pid)`\n- gated by platform: the ancestor walk reads \/proc, so this is the Linux path\n\n**Evidence**\n\n`[peer-cred] peer pid lookup failed`\n\n- Area: Cross-Session Messaging\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}