4 ms·
I read this as, due to pamspy setting an eBPF probe, pamspy needs to know where libpam.so lives. Not that the pamspy needs libpam to be built
by mdaverde 4y ago
I read this as, due to pamspy setting an eBPF probe, pamspy needs to know where libpam.so lives. Not that the pamspy needs libpam to be built
- citronneur 4y agoExactly, we have to found the address to hook on the system, so we need the path of the currently use of libpam by other process
- sorcix 4y agoOh, makes sense, thanks!
- nicce 4y agoIt is still quite confusing. > built as a static binary without any dependencies Static binaries are explicitly used for removing the need for specific dynamic runtime dependencies. It does not refer to build dependencies, which are not interesting here. Based on the terms, I would except that libpam is included for the final binary.
- stevenhuang 4y agoThe entire point of this program is that it hooks the func inside the libpam.so actively being used by the system for auth...
- freedomben 4y agoIf libpam was compiled in, then this tool would do nothing. libpam is not a library for this tool, it's a target, like an input file. libpam is a library for the kernel of the target system. this tool hooks into it to do its work.
- nicce 4y agoExactly, it is the target. The later phrase pointed out in the original comment it to be some sort of dependency for runtime use, making the confusion. While it is not related to runtime code functionality at all.