If your saved hooks-sharing answer can't be verified, you're asked to decide again in /hooks.
What's wrong with this entry?
When a cloud session is offered this machine's hooks, a stored answer is ignored if the session could write the file holding it. That check can now fail outright, producing a new result telling you the file could not be located to check who can write it and asking you to decide in /hooks.
- Only applies on the cloud-session hooks path.
- The switched-off message is now the actual reason truncated to 200 characters; the previous fixed text about device binding likely being off was removed.
- Registration outcomes
consent_distrusted,dormantandfailedare now reported separately in telemetry. - Answering "not now" now clears the session's pins and standing rather than only disarming.
could not be located to check who can write it. Decide for this session in /hooks., consent_distrusted
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.234
SessionEnd hooks lose the
bypass_permissions_disabledreasonBoth mention hook
-
v2.1.236
Hooks and Ctrl-C go quiet once shutdown has started
Both mention hook
-
v2.1.236
Shutdown seals transcript writes and gives SessionEnd hooks more time
Both mention hook