+20
−19
Loading
this ensures PAM users always get the intended version of a module when multiple versions of the same module exist on a system. most packages which consume `pam` and link against `libpam.so` do so only to access its API, and not because they care about the specific `pam_<xyz>.so` modules provided by that `pam`. but when specifying modules by name only, PAM-capable applications may well load the `pam_<xyz>.so` from the `pam` they were compiled against instead of the pam declared in `security.pam.package`. by fully qualifying `modulePath` we ensure that users can actually swap out pam modules without rebuilding the world.