TACACS+ protocol client library and PAM module in C. This PAM module support authentication, authorization (account management) and accounting (session management)performed using TACACS+ protocol designed by Cisco.
if I understand correctly, libtac is licensed under LGPLv3, so it can be dynamically linked to another applications without infecting them with GPL restrictions.
But pam_tacplus is licensed under GPLv3, which means that any PAM-aware application that uses pam_tacplus must also be licensed under a GPL-compatible license. This requirement arises because a PAM-aware application will implicitly load any PAM-module specified in the PAM configuration into its address space.
PAM itself ships under both a permissive license (modified BSD) and the GPL.
My question is: is this on purpose or can you also allow dual licensing for pam_tacplus as well?
Hello,
if I understand correctly, libtac is licensed under LGPLv3, so it can be dynamically linked to another applications without infecting them with GPL restrictions.
But pam_tacplus is licensed under GPLv3, which means that any PAM-aware application that uses pam_tacplus must also be licensed under a GPL-compatible license. This requirement arises because a PAM-aware application will implicitly load any PAM-module specified in the PAM configuration into its address space.
PAM itself ships under both a permissive license (modified BSD) and the GPL.
My question is: is this on purpose or can you also allow dual licensing for pam_tacplus as well?