> built as a static binary without any dependencies
> As pamspy rely on libpam, we have to set the path where libpam is installed on your distribution.
Confusing text in the readme. Does it have dependencies or not?
> As pamspy rely on libpam, we have to set the path where libpam is installed on your distribution.
Confusing text in the readme. Does it have dependencies or not?
In this case the function of the program is to hook a library function in `libpam` using eBPF so it has libpam as a “dependency” in roughly the same way that a program which converts wav to mp3 depends on “the input wav file”.
Given that this is a somewhat unusual way to depend on a `.so` file it’s reasonable for there to be some ambiguity in the language here.
> 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.
Like pointing a disassembler at a shared library, it's not needed to run the disassembler, it's the thing you're disassembling.