Linked by Thom Holwerda on Mon 12th Feb 2007 18:30 UTC, submitted by stare
Thread beginning with comment 211858
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: This is not an Exploit
by fsckit on Mon 12th Feb 2007 19:51
in reply to "RE: This is not an Exploit"
RE[3]: This is not an Exploit
by stare on Mon 12th Feb 2007 20:41
in reply to "RE[2]: This is not an Exploit"
RE[2]: This is not an Exploit
by Priest on Tue 13th Feb 2007 09:31
in reply to "RE: This is not an Exploit"
RE[3]: This is not an Exploit
by jziegler on Tue 13th Feb 2007 13:05
in reply to "RE[2]: This is not an Exploit"
Yes, it is. If you install S10, S10u1 or S10u2, the "full install", in.telnetd is running. Only in the latest release, S10u3, you have the option to install it "secure by default". In that case, the only internet-listening daemon is sshd. All other are either stopped, or are listening on 127.0.0.1 only.






Member since:
2005-07-06
Plain simple, although it's a serious BUG on the telnet daemon service, I won't consider it as an "EXPLOIT".
Well, this bug will be exploited :-)
Third, why use Telnet on the wild?
Telnetd is enabled by default on Solaris 10.