* Paul Scott ([EMAIL PROTECTED]) [Dec 16. 2001 02:38]: > should not setup or allow telnet at all. Is the setup for ssh exactly > the same as for telnet. I didn't see it in the example I found in the > HOWTO.
(~)% dpkg -l ssh | grep ssh ii ssh 3.0.1p1-1.2 Secure rlogin/rsh/rcp replacement (OpenSSH) So you'd do: % su % apt-get update % apt-get -u install ssh > >I suspect your telnet issues have to do with /etc/inetd.conf and/or > >tcpwrappers. > I was just beginning to discover that. That brings the questions: is > /usr/sbin/in.telnetd a real executable or will it be a link created as a > result of the contents of inetd.conf? Just remember when apt-get install ssh <g>, dpkg will do all the configuration that's needed. Don't attempt to run sshd from inetd. Check out the -i option in sshd(8) for an explanation. (I think sshd knows libwrap too, so still check out hosts_access(5)) -- Brian Clark | Debian GNU/Linux: 3950 packages to keep you busy. Fingerprint: 07CE FA37 8DF6 A109 8119 076B B5A2 E5FB E4D0 C7C8 I'm not paranoid! Which of my enemies told you this?
