I think I just answered my own question,
The sshd binary was compiled with TCP wrappers support. This makes it an
exception to the rule.
Have a happy.
-----Original Message-----
From: asosin [SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, July 04, 2000 4:22 PM
To: [EMAIL PROTECTED]
Subject: Re: SSH being blocked by TCP wrappers ?
I'm hoping someone has an idea of how to solve this question. As far as
the books describe this, sshd can be started in two ways in Linux: a).
\etc\inetd.conf b). as a daemon the script is placed in the
/etc/rc.d/init.d directory and then a simlink is created from
/etc/rc.d/rc(x) (where x is the number of init level).d to a function in
/etc/rc.d/init.d directory.
My question is as follows, TCP wrappers are suppose to block TCP
connections which are started as services. If I have disabled all the
entries in the /etc/rc.d/init.d directory including the sshd, and instead I
used method b). above to start sshd.
How is it possible for the TCP wrappers to stop ssh connections coming into
the server ?
When I type in tksysv it lists sshd as a daemon and not a service. Is sshd
running as a daemon or a service ?
If you prefer, please reply to my e-mail address.
Thanks.
