Why would TCP wrappers stop working for sshd?

Posted by toby1kenobi on Server Fault See other posts from Server Fault or by toby1kenobi
Published on 2014-05-27T08:38:51Z Indexed on 2014/05/27 9:29 UTC
Read the original article Hit count: 124

Filed under:
|

On a couple of CentOS 5 servers sshd seems to have become 'unwrapped' - previously I was using TCP wrappers and hosts.allow/hosts.deny to control access, but these are now not being used. If I execute

$ldd /usr/sbin/sshd | grep libwrap 
$

it outputs nothing, whereas on servers where TCP wrappers are still working I see

libwrap.so.0 => /lib64/libwrap.so.0 (0x00002b2fbcb81000)

Does anyone know what might cause this, or how it could be rectified?

Updated As requested:

$ rpm -qV openssh-server
S.5....T  c /etc/pam.d/sshd
S.?....T  c /etc/ssh/sshd_config
S.5.....    /usr/sbin/sshd

© Server Fault or respective owner

Related posts about centos

Related posts about ssh