full-disclosure - Re: open telnet port

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <413F8EA6.7060408@sbcglobal.net>
From: chromazine at sbcglobal.net (Steve Kudlak)
Subject: Re: open telnet port

This sort of solution is like when goes to the doctor and says
"It hurts when I do this..." and one does a common normal
hand gesture and the doctor's response is  "well don't do that..."
This is kind a response of  that is easy for one person to make
and it really never solves the problem.

Alas I can't do to much better, not being a Solaris person, although
I do have a Solaris box to play with,  so I might be able to figure out
something. at some point. I would worry if I could do something to
the port and get data through it rather have it just time out. or 
something..

I'll ask my friend what he does as the "just don't do x"  or just get rid
of   x  never seems like a good idea.  If you try to connect with telnet
rather than ssh to that box it just doesn't go through.

Have Fun,
Sends Steve

Dave Ewart wrote:

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>On Tuesday, 07.09.2004 at 03:43 -0700, ismail syed wrote:
>
>  
>
>>HI list,
>>I have some strange problem or may be its starnge to
>>me
>>I have closed the Telnet port in Solaris 8 server by
>>hashing inetd but still its listening at port 23,even
>>after giving HUP to inetd.
>>I can do telnet from other machines to this server,
>>its getting connected but not showing login prompt.
>>Please give me solution how to close this port,I dont
>>know any other way just except hashing inetd.
>>    
>>
>
>Not sure this is actually on-topic, but have you considered simply
>*uninstalling* your Telnet daemon.  That would seem to be the safest
>thing to do.
>
>Dave.
>- -- 
>Dave Ewart
>Dave.Ewart@...cer.org.uk
>Computing Manager, Epidemiology Unit, Oxford
>Cancer Research UK
>PGP: CC70 1883 BD92 E665 B840 118B 6E94 2CFD 694D E370
>
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.2.4 (GNU/Linux)
>
>iD8DBQFBPbFKbpQs/WlN43ARAhS/AKCVdqMIYb5swFi9gKjhEvyU/0n+tQCfV3F0
>UHBDP9RNfitSqih0IxwUMn4=
>=m9g4
>-----END PGP SIGNATURE-----
>
>_______________________________________________
>Full-Disclosure - We believe in it.
>Charter: http://lists.netsys.com/full-disclosure-charter.html
>
>  
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20040908/38d40666/attachment.html