Cross-session messages verify the peer's process start time, not just its pid.
What's wrong with this entry?
Messages sent between sessions over the local socket, and the receipts for held messages, now carry an expected process start time alongside the expected pid. A reused pid on its own no longer passes verification.
expectPeerProcStart
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