sshd containers don't let logins on some systems with older
PAM library because /proc/self/loginuid is not always readable
or writeable. Examples of possible failures on such systems are
erroneous cold and live migrations.
This fix does not upgrade PAM but makes pam_loginuid optional
for nova_ssh and keystone_ssh.
Reviewed: https:/ /review. openstack. org/413030 /git.openstack. org/cgit/ openstack/ kolla/commit/ ?id=aae9193675e d214f7a44557084 09532ea1665255
Committed: https:/
Submitter: Jenkins
Branch: master
commit aae9193675ed214 f7a445570840953 2ea1665255
Author: Vladislav Belogrudov <email address hidden>
Date: Tue Dec 20 13:53:33 2016 +0300
Containerized sshd does not work with older PAM
sshd containers don't let logins on some systems with older
PAM library because /proc/self/loginuid is not always readable
or writeable. Examples of possible failures on such systems are
erroneous cold and live migrations.
This fix does not upgrade PAM but makes pam_loginuid optional
for nova_ssh and keystone_ssh.
More information: /github. com/docker/ docker/ issues/ 5663 /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 726661 /git.fedorahost ed.org/ cgit/linux- pam.git/ tree/modules/ pam_loginuid/ pam_loginuid. c#n61
https:/
https:/
https:/
Change-Id: Ic14255b042ceed cff536c062bdcba 00502af7a87
Closes-Bug: #1651395