On 01/31/2013 07:08 PM, drago01 wrote: > On Thu, Jan 31, 2013 at 12:05 PM, Karel Volný <kvolny@xxxxxxxxxx> wrote: >> Dne Čt 31. ledna 2013 18:32:57, Ed Greshko napsal(a): >>> On 01/31/2013 06:15 PM, drago01 wrote: >>>> Yes there are usecases for telnet, the OP one isn't. >>> How do you know? As far as I can tell from the thread, no one asked and he >>> didn't state. >> from the original question: >> >> "Trying 192.168.1.15..." >> >> ... that doesn't look like in a public Internet address block ;-) > telnet omen.com > Trying 70.89.176.169... > Connected to omen.com. > Escape character is '^]'. > Fedora release 18 (Spherical Cow) > Kernel 3.7.4-204.fc18.x86_64 on an x86_64 (9) > men login: > > .... looks very public to me ;) Well, you took the extra effort to see if his host was exposed. Yet, that doesn't give insight to his case for needing it. I suppose I approach things a bit differently. In the case where I would see a person has exposed their system to a vulnerability I would ask them if they knew that to be the case and go from there. In any event, a package supplied with fedora "should" work and clearly telnet service doesn't. FWIW, the problem seems not to be in telnetd but actually in /usr/bin/login. -- Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. -- Rick Cook, The Wizardry Compiled -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
