What probably matters to youSection of the release
What
With the isolatePeerMachines protection enabled, sending a message to a Remote Control session, to a cloud session, or to a name that could not be resolved because the cloud session list was unavailable, now stops and asks for your explicit approval instead of going ahead.
Details
The three triggering cases are bridge addresses, resolved cloud sessions, and unresolvable names during a failed session-list lookup.
Evidence
isolatePeerMachines is enabled \u2014 cross-machine message requires explicit approval
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
