Under the hood
Useful1 Signal3
On Linux, incoming session messages can be traced to the sending process and its ancestors.
What's wrong with this entry?
Anonymous. No account, no email.
What
Incoming connections on the cross-session messaging socket can now be attributed to the process tree that sent them. New helpers read /proc/<pid>/stat for the process start time, used as a liveness token, and walk up to 12 ancestor pids; the pid and chain are captured once per connection and passed into message handling.
Details
- The
/procpaths are assembled at runtime, so on non-Linux the reads simply fail and the values come back undefined. - Connection handling sits inside the cross-session messaging path, which is off by default.
Evidence
[peer-cred] peer pid unavailable (fd=
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