Skip to main content
Information Security

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • This is useful, but something that could check what's linked to the running processes would be much better. Getting names/paths of executables and running ldd against them tells you what would be used if you restarted the binary, not what the running process is actually linking to now. Commented Jan 30, 2017 at 4:36
  • Your newer script identifies the paths associated with linked libraries, but that's insufficient information with which to identify whether the library that's linked is the same as what's at that path now. Identifying packages that provide the library is not the goal. Rather I want to identify running processes that are still using old versions of libraries. Commented Jan 30, 2017 at 13:36
  • It sounds like what you want is to be able to hash the library content in memory and compare that with a hash of the content stored on disk. Is that what you're trying to do? Commented Jan 30, 2017 at 18:34