Thanks...
Suggested not to put ssh in inetd.conf since the regeneration of keys will
be slow...
Solution: build ssh with tcpwrappers enabled (see documentation/readme)
>The problem was the user was coming through using SSH... which is not in
>inetd.conf. All access in inetd.conf WAS disallowed for him as it should
>have been.
>
>Do I just add a similar line into inetd.conf for ssh then for it to be
>wrapped as well?
--Dan
--------------------------------------------------------------------------
Dan Kirkpatrick dkirk_at_phy.syr.edu
Computer Systems Manager
Department of Physics
Syracuse University, Syracuse, NY
http://www.phy.syr.edu/~dkirk Fax: (315) 443-9103
--------------------------------------------------------------------------
Received on Wed Jan 26 2000 - 21:54:23 NZDT