View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003184 | unreal | ircd | public | 2007-01-03 08:07 | 2007-01-03 15:49 |
| Reporter | innerfire | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 3.2.2 | ||||
| Summary | 0003184: ircd is not confirming reverse dns | ||||
| Description | the ircd is not confirming the reverse dns by checking the forward. This allows someone to set a domain they do not own as a reverse dns and the ircd will never know the difference. | ||||
| Steps To Reproduce | Set the reverse dns to something absurd. Login and do a whois.. you have that hostname. 208.6.39.118 is a good example with the isp completely screwing up the DNS. | ||||
| 3rd party modules | |||||
|
|
Unreal3.2.2 ?:p Also, I'm not aware of any such bug in Unreal3.2* |
|
|
This is definetly something that only you have experienced, perhaps the dns resolver your using is screwed up ? |
|
|
[10:43:46] ircd@drone:~/Unreal> host 208.6.39.118 118.39.6.208.in-addr.arpa domain name pointer wireless-dockpoint.39.6.208.in-addr.arpa. [10:46:49] ircd@drone:~/Unreal> host wireless-dockpoint.39.6.208.in-addr.arpa ;; Truncated, retrying in TCP mode. wireless-dockpoint.39.6.208.in-addr.arpa has address 208.6.39.254 wireless-dockpoint.39.6.208.in-addr.arpa has address 208.6.39.2 wireless-dockpoint.39.6.208.in-addr.arpa has address 208.6.39.3 wireless-dockpoint.39.6.208.in-addr.arpa has address 208.6.39.4 wireless-dockpoint.39.6.208.in-addr.arpa has address 208.6.39.5 wireless-dockpoint.39.6.208.in-addr.arpa has address 208.6.39.6 wireless-dockpoint.39.6.208.in-addr.arpa has address 208.6.39.7 wireless-dockpoint.39.6.208.in-addr.arpa has address 208.6.39.8 wireless-dockpoint.39.6.208.in-addr.arpa has address 208.6.39.9 ..... wireless-dockpoint.39.6.208.in-addr.arpa has address 208.6.39.118 .......... etc etc in-addr.arpa addresses are perfectly valid. noone can spoof their host with this since this can be done with every ip in existence. maybe the ircd should ignore these hostnames ? |
|
|
That isp has definitely made a big mistake. My complaint is that if the ircd was confirming the result by doing a forward lookup then it would have noticed that the two don't match and discarded the host name. There is no need to special case in-addr.arpa. 10:35 [IF] -!- Mack [[email protected]] 10:35 [IF] -!- ircname : P0WeRZ0nE11 10:35 [IF] -!- modes : 10:35 [IF] -!- : is connecting from *@wireless-dockpoint.39.6.208.in-addr.arpa 208.6.39.118 |
|
|
So this is 3.2.2 or not? We don't support old IRCd's. |
|
|
10:35 [IF] -!- : is connecting from *@wireless-dockpoint.39.6.208.in-addr.arpa 208.6.39.118 "My complaint is that if the ircd was confirming the result by doing a forward lookup then it would have noticed that the two don't match and discarded the host name." your completely wrong; wireless-dockpoint.39.6.208.in-addr.arpa points to 256 different ip addresses, one of which is 208.6.39.118 (ie. wireless-dockpoint.39.6.208.in-addr.arpa DOES match 208.6.39.118), so this entire report is actually completely bogus, the domain name in-addr.arpa is real, and ANYONE can use it |
|
|
Well.. whatever it was 3.2.6 fixes it. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2007-01-03 08:07 | innerfire | New Issue | |
| 2007-01-03 08:12 | syzop | Note Added: 0012979 | |
| 2007-01-03 08:12 | syzop | Note Edited: 0012979 | |
| 2007-01-03 08:16 | djGrrr | Note Added: 0012980 | |
| 2007-01-03 08:21 | djGrrr | Note Added: 0012981 | |
| 2007-01-03 09:40 | innerfire | Note Added: 0012983 | |
| 2007-01-03 09:44 | syzop | Note Added: 0012984 | |
| 2007-01-03 10:31 | djGrrr | Note Added: 0012985 | |
| 2007-01-03 10:32 | djGrrr | Note Edited: 0012985 | |
| 2007-01-03 12:51 | innerfire | Note Added: 0012986 | |
| 2007-01-03 15:49 | syzop | Status | new => closed |
| 2007-01-03 15:49 | syzop | Resolution | open => no change required |
