RE: ProxyPeeper v0.01a - The Real Slim Shady - 10-13-2013
(10-13-2013, 03:46 PM)noize Wrote: (10-13-2013, 12:16 PM)Geoff Wrote: It will detect if he's using a public proxy. This is because in order for the public to be able to access the proxy, the ports will be open.
The average user, or even advanced users will not have such proxy ports open to the public. It can be safely assumed in most scenarios that if these ports are open, it is a public proxy. there is a higher rate of error if you include port 80, because people do run web servers, but even then its unlikely that many people would be browsing the internet from a web server.
any ways this is more of a proof of concept thing. I dont expect it to be implemented on any wide scale.
Oh. Nice idea, but actually, most clients connect to the web through port 80, and so, they have it open.
This is likely to be just a ban hammer if you don't remove 80 from the array.
Uhm... no, most clients connect to port 80 on a webserver- the outgoing port used by a browser is always above the reserved zone (> port 1024). So if the host they are connecting from has port 80 open, its accepting incoming connections - This typically means either webserver or http proxy server. a normal PC wont have this port open.
RE: ProxyPeeper v0.01a - noize - 10-13-2013
(10-13-2013, 03:53 PM)Geoff Wrote: (10-13-2013, 03:46 PM)noize Wrote: (10-13-2013, 12:16 PM)Geoff Wrote: It will detect if he's using a public proxy. This is because in order for the public to be able to access the proxy, the ports will be open.
The average user, or even advanced users will not have such proxy ports open to the public. It can be safely assumed in most scenarios that if these ports are open, it is a public proxy. there is a higher rate of error if you include port 80, because people do run web servers, but even then its unlikely that many people would be browsing the internet from a web server.
any ways this is more of a proof of concept thing. I dont expect it to be implemented on any wide scale.
Oh. Nice idea, but actually, most clients connect to the web through port 80, and so, they have it open.
This is likely to be just a ban hammer if you don't remove 80 from the array.
Uhm... no, most clients connect to port 80 on a webserver- the outgoing port used by a browser is always above the reserved zone (> port 1024). So if the host they are connecting from has port 80 open, its accepting incoming connections - This typically means either webserver or http proxy server. a normal PC wont have this port open.
Oh, sure, yeah, I definitely confused it.
Nice idea, then.
|