[Unreal-users] IP cloaking
Status: Beta
Brought to you by:
wildchild
|
From: tabris <ta...@ta...> - 2005-07-14 19:01:34
|
I realize that this would be a module question, and that it likely=20 would not be recommended. However, I think there is a sufficient use=20 for a IP cloaking method that would keep the first 2 or 3 octets=20 uncloaked, as it would be easier to recognize people. I remember that the last time this proposal came up, there were a=20 couple objections.=20 a) security. 255 possibilities is supposedly sufficiently trivial to=20 attack.=20 b) IRC Clients not handling it correctly. This is a possibility that is=20 harder to trivialize. However, I remember ConferenceRoom 1.8.x doing=20 this (and 2.x as well), and IRC clients handled it just fine. istr they=20 having an IP cloak like so (this is an actual cloak pulled from my logs=20 from a ConferenceRoom server I went to back in 2003): 4.18.44.KU929=3D This is NOT to mean that I want to remove the MD5 cloaking algo. I just=20 want to modify the IPv6 and IPv4 cloaking to make it easier to identify=20 which network/ISP that a user is connecting from, thus making it easier=20 to identify a user on-sight. I would have checked the forums, but they appear to be missing/down. I=20 have also considered coding this myself, but I am insufficiently sure=20 that I understand the algorithm in use, as well as being not confident=20 in my ability to do so. Won't necessarily stop me from trying, if I get=20 enough time. Anyway, does anybody else want this? Would anybody else use it? =2D- tabris =2D Q: Why is Poland just like the United States? A: In the United States you can't buy anything for zlotys and in Poland you can't either, while in the U.S. you can get whatever you want for dollars, just as you can in Poland. -- being told in Poland, 1987 |