BOPM Configuration issue with http ports
Posted: Sun May 01, 2005 11:01 am
Hello,
I'm new to running IRCD's but have successfully configured Unreal and IRCServices for my IRC Server. Things have been running well but I've been doing some research regarding the use of bopm and I have some questions.
I've been reviewing the config file and have a bopm running on my server but I have some questions concerning the portion of the config file that relates to the http ports in particular. I am also running a webserver from this same server (actual server machine) and would like to know if the configuration of the bopm can or will have an effect on this webserver as it is currently configured (the defaults). The area in question is as follows:
Can someone explain what this particular area of the config does and also indicate whether or not this portion of the config will impact my webserver in any way? Does Unreal have ping cookies as described in the last portion of the config shown here?
Any and all comments are welcome.
I'm new to running IRCD's but have successfully configured Unreal and IRCServices for my IRC Server. Things have been running well but I've been doing some research regarding the use of bopm and I have some questions.
I've been reviewing the config file and have a bopm running on my server but I have some questions concerning the portion of the config file that relates to the http ports in particular. I am also running a webserver from this same server (actual server machine) and would like to know if the configuration of the bopm can or will have an effect on this webserver as it is currently configured (the defaults). The area in question is as follows:
Code: Select all
* HTTP CONNECT - very common proxy protocol supported by widely known
* software such as Squid and Apache. The most common sort of
* insecure proxy and found on a multitude of weird ports too. Offers
* transparent two way TCP connections.
*/
protocol = HTTP:80;
protocol = HTTP:8080;
protocol = HTTP:3128;
protocol = HTTP:6588;
/*
* SOCKS4/5 - well known proxy protocols, probably the second most
* common for insecure proxies, also offers transparent two way TCP
* connections. Fortunately largely confined to port 1080.
*/
protocol = SOCKS4:1080;
protocol = SOCKS5:1080;
/*
* Cisco routers with a default password (yes, it really does happen).
* Also pretty much anything else that will let you telnet to anywhere
* else on the internet. Fortunately these are always on port 23.
*/
protocol = ROUTER:23;
/*
* WinGate is commercial windows proxy software which is now not so
* common, but still to be found, and helpfully presents an interface
* that can be used to telnet out, on port 23.
*/
protocol = WINGATE:23;
/*
* The HTTP POST protocol, often dismissed when writing the access
* controls for proxies, but sadly can still be used to abused.
* Offers only the opportunity to send a single block of data, but
* enough of them at once can still make for a devastating flood.
* Found on the same ports that HTTP CONNECT proxies inhabit.
*
* Note that if your ircd has "ping cookies" then clients from HTTP
* POST proxies cannot actually ever get onto your network anyway. If
* you leave the checks in then you'll still find some (because some
* people IRC from boxes that run them), but if you use BOPM purely as
* a protective measure and you have ping cookies, you need not scan
* for HTTP POST.
*/
protocol = HTTPPOST:80;
Any and all comments are welcome.
.
perator(s) online
efender!