{"version":"2.1.225","anchor":"impersonation-warning-when-a-local-session-claims-a-pinned-r","canonical_anchor":"impersonation-warning-when-a-local-session-claims-a-pinned-r","heading":"Impersonation warning when a local session claims a pinned remote identity","tier":"notice","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/impersonation-warning-when-a-local-session-claims-a-pinned-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Impersonation warning when a local session claims a pinned remote identity\n\nIf a session claims a peer identity that isn't on your machine, the message is blocked as suspicious.\n\n**What**\n\nPeer resolution tracks identities previously confirmed as not being on this machine. If a local session record later claims one of those names, nothing is sent and the model is told the situation is suspicious.\n\n**Details**\n\n- The pinning is per-identity: once a name resolves to a session that is NOT on this machine, that fact is remembered for the session.\n- On a conflict the send is blocked outright rather than routed to the local match.\n- The model is instructed to ask the user before confirming anyone.\n\n**Evidence**\n\n`A same-named session on this machine your user did not start is suspicious: ask the user before confirming anyone.`, `A session on this machine impersonating it is suspicious: ask the user.`\n\n- Area: Cross-Session Messaging\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}