Under the hood
Useful2 Signal2
When bridge owner pinning refuses a session it now reports the reason.
What's wrong with this entry?
Anonymous. No account, no email.
What
The check that pins a remote bridge session to the credential owner can now be handed a preset owner and returns both a decision and a reason, where it previously just returned nothing on failure. Reasons include no token, disabled, not a store login, not the owner, unresolved, and no identity.
Details
- The returned pin also exposes a way to ask whether the owner was verified.
- Some paths report unresolved rather than performing a lookup, so the outcome depends on which checks the session start runs.
Evidence
not_store_login
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
Remote bridge replaces stale-epoch recovery with a one-shot supersession close
Both mention bridge
-
v2.1.236
Remote bridge waits for the disconnect notice, and an inbox fetch that is always off
Both mention bridge
-
v2.1.236
Bridge shuts down cleanly on SIGHUP
Both mention bridge