{"version":"2.1.269","anchor":"session-event-signing-moved-from-local-key-material-to-a-del","canonical_anchor":"session-event-signing-moved-from-local-key-material-to-a-del","heading":"Session-event signing moved from local key material to a delegated async signer","tier":"internal","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/session-event-signing-moved-from-local-key-material-to-a-del","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Session-event signing moved from local key material to a delegated async signer\n\nSession-event signing now delegates to an external signer instead of signing locally with an in-process key\n\n**What**\n\nSession events used to be signed synchronously using Node's built-in cryptography library with a raw private key held in the process. Signing is now asynchronous and delegates the actual signing operation to an injected signer object, rather than performing the cryptographic signature in-process against local key material.\n\n**Why**\n\nMoving signing to a delegated, asynchronous signer means the private key material no longer needs to live directly in the process doing the signing, which can support setups where signing happens through a separate, more controlled component.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}