{"version":"2.1.275","anchor":"remote-control-requests-now-carry-attestation-data","canonical_anchor":"remote-control-requests-now-carry-attestation-data","heading":"Remote control requests now carry attestation data","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/remote-control-requests-now-carry-attestation-data","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Remote control requests now carry attestation data\n\nRemote control tool\/permission requests now carry attestation data\n\n**Unclear.** What attestation mechanism produces these values or how they are validated is not stated in the finding.\n\n**What**\n\nWhen a remote session forwards a tool or permission request to a callback (the code that decides how to handle it), it now also includes `attestationStatus` and `attestationRaw` fields alongside the existing timing information.\n\n**Why**\n\nThis gives remote-control handlers more information to verify the authenticity of an incoming request before acting on it.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}