  justin Australian join:1999-05-28 Brooklyn, NY | Ident - not Ident demon listens on this port, but TCP not UDP. An incorrectly configured firewall may open UDP+TCP port 113 in order to allow Ident requests in. | |
|
 |  bobdude1 Premium join:2002-08-10 Wylie, TX
| Re: Ident - not
Some IRC servers are now requiring identd and that's on 113, this may be why we're seeing more open UDP 113 ports.
I know that more and more DALnet servers will not let you on without IDENTD enabled. I think they are monitoring folks this way to cut down on booting, etc.
So I disagree that a firewall is configured incorrectly if 113 is open. The individual(s) most likely enjoy IRC chatting and that's why it's open.
...just my $0.02
[text was edited by author 2003-03-06 02:34:37]
[text was edited by author 2003-03-06 02:37:08] | |
|
 |  |  |
 |  bobdude1 Premium join:2002-08-10 Wylie, TX
| That's true...but if you use IRC quite a bit....that's not a real feasible thing to do. Maybe, a firewall (software...cheap and easy, or even as firewall appliance, not so cheap, but very secure!), and only allow you're IRC client access to the port...that will certainly cut down on any threat! | |
|
 n4cer
join:2000-09-23 Birmingham, AL | *TCP* not UDP Justin is correct.
IDENT is on *TCP* port 113, not UDP port 113, which is what this discussion is about.
Some misconfigured firewalls will have both TCP and UDP 113 open, when only TCP/113 is needed. | |
|
 |
 al92lt1
join:2003-12-06 Fernley, NV
| But what about UDP Port 113? On several security scans TCP Port 113 and UDP Port 113 were detected as OPEN. I am using a Linksys router and Kerio firewall with PPPoE DSL. In my router configuration, I managed to STEALTH TCP Port 113 by using UPnP and forwarding to a non existent IP address on my network. This technique does not work with the UDP Port 113, only the TCP Port. Can anybody advise me? | |
|
  Blusjamr
@comcast.net | Closing UDP 113 What's the option to close the udp port 113, I do not use irc? | |
|
 |
|
 |