{"version":"2.1.234","anchor":"one-approval-path-for-sending-files-and-messages-to-peer-mac","canonical_anchor":"one-approval-path-for-sending-files-and-messages-to-peer-mac","heading":"One approval path for sending files and messages to peer machines","tier":"notice","area":"Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/one-approval-path-for-sending-files-and-messages-to-peer-mac","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### One approval path for sending files and messages to peer machines\n\nFile and message sends to peer machines share one approval path and refuse altered answers.\n\n**What**\n\nSendFile and the message-send path now share a single permission routine when isolation between peer machines is turned on. It re-asks for permission, and refuses the send if the answer comes back altered.\n\n**Details**\n\n- Refusals name their reason: `recipient_changed` when the permission handler points the send at a different recipient, `bad_shape` when it returns something the tool cannot accept, and `non_text_message` when it rewrites the message into a non-text form.\n- Only runs when peer-machine isolation is on and the permission phase has not already happened for that send.\n\n**Evidence**\n\n`The permission handler changed the recipient (from `\n\n- Area: Session Messaging\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}