Under the hood
Useful2 Signal3
Messages from your other sessions now identify the exact process run, not just the pid.
What's wrong with this entry?
Anonymous. No account, no email.
What
Messages arriving over the local cross-session socket now record a verified process start value along with the sender's pid, so the origin identifies a specific process run rather than just a pid.
Details
- The connection handler resolves the peer token once per connection and reuses the token read during setup when the pid matches, instead of re-reading it per message.
Evidence
verifiedPeerProcStart
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