With isolatePeerMachines on, cross-machine messages now stop and ask for your approval.
What's wrong with this entry?
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.
- The three triggering cases are bridge addresses, resolved cloud sessions, and unresolvable names during a failed session-list lookup.
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.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.223
Circuit-breaker permission reasons moved to a registry; isolatePeerMachines is now bypass-immune
Both mention isolate peer machine
-
v2.1.223
Circuit breakers carry declared traits instead of hard-coded name checks
Both mention isolate peer machine