{"version":"2.1.207","anchor":"remote-control-unsigned-request-rejection-feedback","canonical_anchor":"remote-control-unsigned-request-rejection-feedback","heading":"Remote Control: Unsigned Request Rejection Feedback","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.207\/e\/remote-control-unsigned-request-rejection-feedback","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.207","markdown":"### Remote Control: Unsigned Request Rejection Feedback\n\nWhen Remote Control receives a remote command or permission response without a valid device signature, it now:\n\n- Logs the rejection to stderr with details including attestation status and actionable hints.\n- Sends an explicit error `control_response` back to the sender, so the remote device knows the request was refused (previously the rejection was silent).\n- Rate-limits burst warnings: after a threshold, further warnings for the same burst are suppressed with a note.\n- Provides specific re-enrollment hints based on the attestation failure type (absent key, keyless device, etc.).\n\n**Evidence**\n\nRejection notifier and response writer (search for `\"Remote Control is rejecting a burst of unsigned remote activity\"` and `\"[remote-io] refusal write failed\"`)"}