{"version":"2.1.271","anchor":"remote-attach-sessions-can-now-re-bind-the-device-event-sign","canonical_anchor":"remote-attach-sessions-can-now-re-bind-the-device-event-sign","heading":"Remote sessions re-bind the event signer when security tier is raised","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/remote-attach-sessions-can-now-re-bind-the-device-event-sign","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Remote sessions re-bind the event signer when security tier is raised\n\nRemote sessions now re-key their event signer after the server escalates the security tier, instead of only binding it once\n\n**What**\n\n- Remote-attach sessions' device event signer now supports `rebindEventSigner()`, which re-reads the session's current device binding and rebinds the signer if it changed, instead of only being set once at attach time.\n\n- The remote session client now handles a new `security_update` control frame. When it reports `security_tier` as `elevated`, the session flags that a raise was seen, and on the next reconnect it calls `rebindEventSigner()` to re-establish the signer under the new tier.\n\n- Concretely, `SessionsV2Client` handles this as a new SSE event type carrying `security_tier`; an elevated tier triggers `onSecurityTierRaised`, which sets `securityTierRaiseSeen` and causes the next reconnect to re-key the session's event signer.\n\n**Why**\n\nThis keeps a remote session's cryptographic event signer in sync when the server tightens security requirements mid-session, without forcing the user to start a new session.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}