Re: Silly crackers... NT is for kids...

2001-08-17 Thread Nate Williams
> Which just brings me to another point, why not just turn ssh on by default > and turn telnetd off by default, given the latest exploit. As Bruce already mentioned, this is the new default in 4.4. Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the b

Re: Silly crackers... NT is for kids...

2001-08-17 Thread Chris Costello
On Friday, August 17, 2001, Jonathan M. Slivko wrote: > I'm saying without any intervention of any kind. -- Jonathan Hence the part about "By default". If the person installing FreeBSD does nothing when asked about inetd.conf, no inetd services are enabled. This means telnetd, too. -- +---

Re: Silly crackers... NT is for kids...

2001-08-17 Thread Jonathan M. Slivko
ROTECTED]> To: "Jonathan M. Slivko" <[EMAIL PROTECTED]> Cc: "Nate Williams" <[EMAIL PROTECTED]>; "Matt Piechota" <[EMAIL PROTECTED]>; "Carroll, D. (Danny)" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent:

Re: Silly crackers... NT is for kids...

2001-08-17 Thread Bruce A. Mah
If memory serves me right, "Jonathan M. Slivko" wrote: > Which just brings me to another point, why not just turn ssh on by default > and turn telnetd off by default, given the latest exploit. Thanks for > bringing up a point that I wanted to bring to the security team for awhile. >From the rele

Re: Silly crackers... NT is for kids...

2001-08-17 Thread Michael Bryan
"Jonathan M. Slivko" wrote: > > Which just brings me to another point, why not just turn ssh on by default > and turn telnetd off by default, given the latest exploit. Umm, because the -next- exploitable bug might be in sshd, not telnetd? There are lots of good reasons to run ssh and not tel

Re: Silly crackers... NT is for kids...

2001-08-17 Thread Jonathan M. Slivko
ROTECTED]> Sent: Friday, August 17, 2001 5:11 PM Subject: RE: Silly crackers... NT is for kids... > > Even for authentication? > > > > I can understand using a telnet client to manually test SMTP servers or > > other protocols, but I cannot understand why you *need* telnet. &