add libpam.so.0 and libpam_misc.so.0 to exclude list#558
add libpam.so.0 and libpam_misc.so.0 to exclude list#558Zaraka wants to merge 1 commit intoAppImageCommunity:masterfrom
Conversation
|
What happens if an application requires |
well if it is a direct linkage it will fail, so I'm not sure I understand your question. I argue that bundled libpam will always be useless as that won't make PAM on the client Linux suddenly work. Each Distro will probably have a completely different PAM setup, the only thing it will share will be the modules and I'm certain they will be shared only with name and 'API', not the implementation. |
|
I don't care about PAM working, as long as the application will run. But if a system lacks libraries that the application links to, then the application will fail to run. And that's what we want to avoid. |
|
but with your argument excludelist has to be empty, because what if user links to libX11.so.6 for example? |
2 participants
Pam libraries are system specific, when using bundled PAM libs from e.g. fedora on Debian you can get an error such as
Authentication failed: Module is unkown. Using system PAM libraries works completely fine, also If the system doesn't have PAM libraries I do not think PAM works at all, so there should not be any reason to bundle them.