Univention Bugzilla – Bug 37129
univention-pam is not installed until the system is configured by univention-system-setup
Last modified: 2015-03-25 16:44:13 CET
univention-pam is not installed until the system is configured by univention-system-setup. This affects the installation DVD and the EC2 instances. Because of this the special message of the day (motd.setup) for appliance mode is not shown during login on console or via ssh.
As univention-pam is quiet LDAP dependent and univention-system-setup-boot should also be able to setup a base system without LDAP, always installing univention-pam just to get pam_motd.so used might not be so good. Also consider all the cases where login might fail because of not yet configured/running LDAP.
*** Bug 37753 has been marked as a duplicate of this bug. ***
A pam-config module has been added. It is configured for /etc/pam.d/common-session and provides the same functionality as the UCR template 20system-setup-login-message: Show /etc/motd.setup Upon installing univention-pam, the base UCR template for /etc/pam.d/common-session is installed and takes over. As univention-system-setup-boot is uninstalled when completing the system-setup process, no remnants of the pam-config file should remain on a joined system. r58726 univention-system-setup 8.1.66-23.850.201503090924 r58729 2015-03-09-univention-system-setup.yaml
OK - 2015-03-09-univention-system-setup.yaml OK - UCS 4.0-1 appliance + errata update OK - appliance motd normal OK - appliance motd amazon OK - after setup, normal /etc/issue
<http://errata.univention.de/ucs/4.0/116.html>