| 2008-04-27 15:27:24 |
Bolek |
description |
Binary package hint: openssh-server
After installing Hardy Heron, I see following messages in my long when connecting to my system using SSH (telnet and ftp are disabled so I cannot comment on those):
Apr 27 10:52:03 tux-229 sshd[733]: PAM adding faulty module: /lib/security/migrate
Apr 27 10:52:03 tux-229 sshd[733]: PAM unable to dlopen(/lib/security/nullok)
Apr 27 10:52:03 tux-229 sshd[733]: PAM [error: /lib/security/nullok: cannot open shared object file: No such file or directory]
Each time a connection is made, these three entries are added. I checked the pointers, and indeed, these modules are not installed:
/lib/security/migrate
/lib/security/nullok
/lib/security/migrate
Providing that I have performed a standard Hardy Heron installation, I cannot imagine the above three mentioned security modules were 'optional' and would require me to install them manually. Can anybody, please, comment on this? This issue was not present in Gutsy and I can say with certainty, that it is a Hardy Heron 'phenomenon'.
Information as per your request:
1)
=> lsb_release -rd
Description: Ubuntu 8.04
Release: 8.04
2)
=> apt-cache policy openssh-server openssh-client
openssh-server:
Installed: 1:4.7p1-8ubuntu1
Candidate: 1:4.7p1-8ubuntu1
Version table:
*** 1:4.7p1-8ubuntu1 0
500 http://ubuntu.media.mit.edu hardy/main Packages
100 /var/lib/dpkg/status
openssh-client:
Installed: 1:4.7p1-8ubuntu1
Candidate: 1:4.7p1-8ubuntu1
Version table:
*** 1:4.7p1-8ubuntu1 0
500 http://ubuntu.media.mit.edu hardy/main Packages
100 /var/lib/dpkg/status
3) I do not expect to see following message in the log upon logging via ssh:
Apr 27 10:52:05 tux-229 sshd[1059]: PAM adding faulty module: /lib/security/migrate
Apr 27 10:52:05 tux-229 sshd[1059]: PAM unable to dlopen(/lib/security/nullok)
Apr 27 10:52:05 tux-229 sshd[1059]: PAM [error: /lib/security/nullok: cannot open shared object file: No such file or directory]
4) No applicable as per #3. It appears that PAM modules are missing as per my earlier description of the problem.
Thanks. |
Binary package hint: openssh-server
After installing Hardy Heron, I see following messages in my log when connecting to my system using SSH (telnet and ftp are disabled so I cannot comment on those):
Apr 27 10:52:03 tux-229 sshd[733]: PAM adding faulty module: /lib/security/migrate
Apr 27 10:52:03 tux-229 sshd[733]: PAM unable to dlopen(/lib/security/nullok)
Apr 27 10:52:03 tux-229 sshd[733]: PAM [error: /lib/security/nullok: cannot open shared object file: No such file or directory]
Each time a connection is made, these three entries are added. I checked the pointers, and indeed, these modules are not installed:
/lib/security/migrate
/lib/security/nullok
/lib/security/migrate
Providing that I have performed a standard Hardy Heron installation, I cannot imagine the above three mentioned security modules were 'optional' and would require me to install them manually. Can anybody, please, comment on this? This issue was not present in Gutsy and I can say with certainty, that it is a Hardy Heron 'phenomenon'.
Information as per your request:
1)
=> lsb_release -rd
Description: Ubuntu 8.04
Release: 8.04
2)
=> apt-cache policy openssh-server openssh-client
openssh-server:
Installed: 1:4.7p1-8ubuntu1
Candidate: 1:4.7p1-8ubuntu1
Version table:
*** 1:4.7p1-8ubuntu1 0
500 http://ubuntu.media.mit.edu hardy/main Packages
100 /var/lib/dpkg/status
openssh-client:
Installed: 1:4.7p1-8ubuntu1
Candidate: 1:4.7p1-8ubuntu1
Version table:
*** 1:4.7p1-8ubuntu1 0
500 http://ubuntu.media.mit.edu hardy/main Packages
100 /var/lib/dpkg/status
3) I do not expect to see following message in the log upon logging via ssh:
Apr 27 10:52:05 tux-229 sshd[1059]: PAM adding faulty module: /lib/security/migrate
Apr 27 10:52:05 tux-229 sshd[1059]: PAM unable to dlopen(/lib/security/nullok)
Apr 27 10:52:05 tux-229 sshd[1059]: PAM [error: /lib/security/nullok: cannot open shared object file: No such file or directory]
4) No applicable as per #3. It appears that PAM modules are missing as per my earlier description of the problem.
Thanks. |
|
