{"version":"2.1.236","anchor":"local-socket-messaging-checks-which-process-it-is-talking-to","canonical_anchor":"local-socket-messaging-checks-which-process-it-is-talking-to","heading":"Local socket messaging checks which process it is talking to","tier":"internal","area":"Multi-Session","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/local-socket-messaging-checks-which-process-it-is-talking-to","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Local socket messaging checks which process it is talking to\n\nLocal socket messages now verify which process is on the other end.\n\n**What**\n\nThe helpers that send messages and control commands over the local socket now carry an expected peer process id, verified against the connecting process along with a child-token check, and the inbox teardown and key-file state move behind an accessor. Failing to publish the inbox auth key still refuses to start an inbox.\n\n**Evidence**\n\n`[uds-messaging] Failed to publish the inbox auth key (refusing to run an inbox no peer can authenticate to): `\n\n- Area: Multi-Session\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}