View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002260 | unreal | ircd | public | 2004-12-30 00:48 | 2004-12-31 23:06 |
| Reporter | Tony | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | open | ||
| Product Version | 3.2.3 | ||||
| Summary | 0002260: Add incoming connection port information to connection notices for opers/admin | ||||
| Description | Display the connection requesting computers port number for all connections to the server(s) in the connection notices. This would help tremendously when trying to get rid of lamers that have 4,000 proxies available on odd port numbers that are not picked up by bopm. You could use this information to refine your port scans in bopm to block them. | ||||
| 3rd party modules | |||||
|
|
This wont help one bit. When I make a connection to a server on port 6667, my local port may be anything over 1024. When you connect through a proxy it works the same exact way. When you connect to a proxy, you have your local port going to the proxies public port, when the proxy accepts the connection, you are assigned one of its local ports (to keep the proxy port open). Once the connection is accepted on the proxy, the proxy proceeds to connect to the server using the same method that any client would. If proxy detection were as easy as you suggest, I am sure someone would have done it ages ago. |
|
|
indeed |
