Firewalls: Re: Access to TCP Port 113

Firewalls
(July 1995)

Indexed By Thread: [Previous] [Next]

Subject:	Re: Access to TCP Port 113
From:	Julian Assange <proff @ suburbia . apana . org . au>
Date:	Thu, 13 Jul 1995 13:28:46 +1000 (EST)
To:	paul @ hawksbill . sprintmrn . com (Paul Ferguson)
Cc:	firewalls @ greatcircle . com
In-reply-to:	<9507130020 . AA26919 @ hawksbill . sprintmrn . com> from "Paul Ferguson" at Jul 12, 95 07:20:33 pm

> Blocking _shouldn't_ wreak too much havoc, but you may notice that
> establishing connections to outside services may seem to hang during
> the connection process while the tcp/113 request times out.
> 
> My vote: Block it.
> 

Yes, after all US sprint has to protect the usernames/uids of all the hackers
come out from their internal network.

Typical small minded isolationist stance.

-Proff

Follow-Ups:

Re: Access to TCP Port 113
From: Al McPhee <mcphee @ nucleus . com>

References:

Re: Access to TCP Port 113
From: paul @ hawksbill . sprintmrn . com (Paul Ferguson)

Indexed By Date	Previous:	Re: Netscape & SSL From: Chris . Martin @ amd . com (Chris Martin)
Indexed By Date	Next:	Changing a firewall setup. From: Darren Reed <avalon @ coombs . anu . edu . au>
Indexed By Thread	Previous:	Re: Access to TCP Port 113 From: paul @ hawksbill . sprintmrn . com (Paul Ferguson)
Indexed By Thread	Next:	Re: Access to TCP Port 113 From: Al McPhee <mcphee @ nucleus . com>