Re: Cannot Stealth port 113
Available news archives: comp.lang.tcl - comp.lang.python - comp.security.firewalls - sci.crypt - comp.lang.php - comp.lang.javascript
Google
 
Web news.hping.org


comp.security.firewalls archive

Re: Cannot Stealth port 113

From: Spack <news@worldofspack.co.uk>
Date: Fri Dec 23 2005 - 10:09:30 CET

Leythos wrote on Thu, 22 Dec 2005 23:00:41 GMT:

> In article <hi9mq1ph70ocb076tm9gugl7via98dde6u@4ax.com>, me@privacy.org
> says...
>> On Thu, 22 Dec 2005 16:18:24 -0500, "Bill & Debbie" <billdeb@sccoast.net>
>> wrote:
>>
>>> When I run GRC all ports are stealthed except for 113. It comes up blue
>>> (closed). I have a wireless connection using Linksys BEFW11S4 router.
>>>
>>> I'm running ZoneAlarm.
>>>
>>> Any help changing port 113 from Closed to Stealthed would be greatly
>>> appreciated.
>>>
>> You shouldn't 'stealth' 113/tcp period.
>
> Why, it won't make any difference to most home users, and little if any
> difference to corporate users.
>

Makes plenty of difference to most people I know, including me - IRC and
Usenet connect are much slower, as the servers I use both connect back to
113. I don't have an ident service running, but even so connects are quick
so long as connections as RST rather than dropped - if you have a
"stealthed" 113, you end up having to wait 30 seconds for the connect
attempt at the other to timeout.

Dan
Received on Fri Dec 23 20:08:54 2005