Date: Sat, 14 Nov 1998 12:50:47 +1300 (NZDT) From: Andrew McNaughton <andrew@squiz.co.nz> To: Andy Farkas <andyf@speednet.com.au> Cc: freebsd-isp@FreeBSD.ORG Subject: Re: no more telnet Message-ID: <Pine.BSF.4.01.9811141240570.685-100000@aniwa.sky> In-Reply-To: <Pine.BSF.4.05.9811140105060.6128-100000@backup.zippynet.iol.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 14 Nov 1998, Andy Farkas wrote: > > Installing ssh won't save you a trip to the console if it's currently > > required, since you need access before you can install ssh. Once you're > > back up though you might consider installing ssh and running it as a > > daemon, (not through inetd) so that it acts as a backup access method in > > case your problem returns. > > > > Andrew McNaughton > > > > Are you suggesting that I replace telnetd with ssh?? Seeing as how I am > the only one that has shell access ... sounds .. secure... What I was suggesting is that if you have a problem with telnet and that fixing it requires a trip to a remotely located machine, then you might want a backup access method other than telnet. Ssh has security advantages but the redundancy (ie leave telnet in) is what I was suggesting might be useful in your current situation. I routinely use ssh rather than telnet, but I still have telnet there as a fallback. Ssh installs cleanly and easily from the standard sources. It won't take you long to get going. Security is not the issue you've raised, but in so far as you're concerned about sniffers, it's worth keeping in mind that the number of users is a minor security issue compared to sending your root password in clear text. Andrew McNaughton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.01.9811141240570.685-100000>