Closed david415 closed 8 years ago
https://github.com/subgraph/procsnitchd
the procsnitchd solution comes with a caveat; the calling party must not use the response data if the connection was closed before response received. that is, there be a race condition if the calling party didn't noticed the socket was destroyed and created, it's inode would differ and thus the associated process information different.
i made it work. roflcoptor plays nice with procsnitchd. please review this pull request --> https://github.com/subgraph/roflcoptor/pull/28
we only need to be root so that the procsnitch API can read the /proc filesystem. instead we could run as a non-root user and use a UNIX domain socket RPC to get the /proc information. the procsnitchd daemon answers to these RPC queries and runs as root.