Date: Mon, 26 Jun 2000 12:32:30 +0200 From: Alexander Langer <alex@big.endian.de> To: David O'Brien <obrien@FreeBSD.ORG> Cc: Adrian Chadd <adrian@FreeBSD.ORG>, arch@FreeBSD.ORG Subject: Re: Disabling inetd? Message-ID: <20000626123230.C7800@cichlids.cichlids.com> In-Reply-To: <20000626031547.J14265@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Mon, Jun 26, 2000 at 03:15:48AM -0700 References: <20000626053525.U85886@argon.gryphonsoft.com> <20000626115146.S36017@zoe.bastard.co.uk> <20000626031547.J14265@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thus spake David O'Brien (obrien@FreeBSD.ORG): > > If I remember right, the telnet port isn't insecure by itself, only > > open telnet connections. So there really isn't anything to be said > > for killing telnet for 'out of the box security' - if people use > > telnet rather than ssh, they're going to enable it anyway. > I cannot quite parse what you are saying. What does speaking about a > port's security mean? I think he means, that not inetd/telnet itself is the problem, e.g. because of a buffer overflow, but the unencrypted transfer of the passwords through the open connection is. Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000626123230.C7800>