Under the hood
Useful1 Signal1
Socket path comparisons and error handling in cross-session messaging got tightened.
What's wrong with this entry?
Anonymous. No account, no email.
What
Cross-session messaging resolves both paths before comparing directories when deciding whether a .sock file is a sibling socket, and rejects one further class of path outright. The local HTTP server now destroys the socket after logging a client response error instead of leaving it open.
Details
- The regexes matching PEM private-key BEGIN and END lines in the secret scanner moved from shared module-level globals, which carried match position between calls, into fresh per-call instances.
- The auto-mode classifier's latch for a rejected beta moved from a single module-wide boolean into per-session state, so one session no longer latches it for another.
- All four are unconditional.
Evidence
Client response error:
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
Messages injected by a host are classified separately from peer messages
Both mention cross
-
v2.1.234
Cross-session control requests check ids more carefully
Both mention cross
-
v2.1.234
Notice acks now wait for the record to persist
Both mention cross