selamun aleykum services.conf umda sole bir sey var ..
PHP Kod: Kodu kopyalamak için üzerine çift tıklayın!
########################################################################### # # Proxy detection # ########################################################################### # Note: if ProxyDetect is not set, all parameters after it in this section # are optional. # ProxyDetect [OPTIONAL] # # Enables insecure proxy detection. Services will automatically # scan each incoming user and akill those that use insecure proxy. # # Anope currently supports detection of Wingate (port 23), SOCKS4/5 # (port 1080), and HTTP proxy (ports 3128 and 8080). It uses the # protocol of each proxy type to connect to an IRC server, it does # not only check if the port is open (so your users may still have # an open telnet server on their port 23 for example). # # WARNING: You should get the authorization of the administrator of # the computer which runs the proxy detector before enabling it; not # all administrators will accept it. Also note that in certain # countries, port scanning is prohibited. # # This feature requires threading support to be compiled into Anope. #ProxyDetect # ProxyThreads <number> [REQUIRED] # # Sets the number of threads Services will launch when starting. Each # thread will have the responsibility to scan queued hostname for # proxies. # # This value must be set depending of the number of users you have # on your network. The more threads are used, the more simultaneous # checks can be done. Remember however, that threads are # resource-consuming. # # WARNING: On Linux, each thread takes a background process, and there # is an additional process used for thread management; this is a problem # if you are limited in the number of background process you can use # (on a paid shell for example). #ProxyThreads 1 # ProxyMessage... <message> [RECOMMENDED] # # Sets the notices that will be sent out to users before Services # scan them for proxy. You may not use all of them, but just as much as # necessary. ProxyMessage1 "Proxy Taramasinsdan geciyorsunuz..." ProxyMessage2 "If you see a connection on port 23, 1080, 3128 or 8080 from" ProxyMessage3 "my.box.net, please disregard it, as it is the detector in action." ProxyMessage4 "See http://proxy.myirc.net/ for information about our proxy policy." ProxyMessage5 "Enter" ProxyMessage6 "whatever" ProxyMessage7 "you want" ProxyMessage8 "here." # ProxyCheck... [OPTIONAL] # # Determines what types of proxy Anope will try to find (respectively # Wingate on port 23, SOCKS4 on port 1080, SOCKS5 on port 1080, HTTP # proxy on port 3128, HTTP proxy on port 8080 and HTTP proxy on port # 80). ProxyCheckWingate ProxyCheckSocks4 ProxyCheckSocks5 ProxyCheckHTTP1 ProxyCheckHTTP2 ProxyCheckHTTP3 # ProxyTimeout <time> [REQUIRED] # Sets the maximum length of time we allow a connect/read operation to # take. If you set this value too high, your threads may hang on a single # check for a very long time. The best is to try different values # and see which one is the more efficient for your network. ProxyTimeout 15s # ProxyTestServer <ip> <port> [REQUIRED] # # Sets the *IP* and port of the IRC server to use as a target when # testing users for proxy. ProxyTestServer "208.98.40.169" PORT # ProxyExpire <time> [RECOMMENDED] # # Sets the length of time before a proxy host cache entry expires, if # not used. ProxyExpire 30d # ProxyCacheExpire <time> [REQUIRED] # # Sets the length of time before a normal host cache entry expires, if # not used. This cannot be set to 0d. # # Every non-proxy hosts will be stored in cache (to avoid too many scans # to the same host), so you should set this enough low to not fill your # memory, especially on large networks. ProxyCacheExpire 1d # ProxyAkillReason <reason> # # Sets the reason that will be used to AKILL an user from the network # if a proxy is detected. ProxyAkillReason "You're using an insecure proxy. See http://proxy.myirc.net/config.html for information about how to config your proxy in a safe manner." # WallProxy [OPTIONAL] # # Sends a WALLOPS/GLOBOPS when an user using an insecure proxy is being # AKILLed. WallProxy # ProxyMax <number> [REQUIRED] # # Sets the maximum proxy cache entries that can be displayed in a single # call to OperServ CACHE. ProxyMax 50
simdi bu proxy korumasimi ? eger proxy korumasi ise aktifmidir ?
aktif degise nerelerinde duzenleme yapilarak kaldirila bilir bu konuda bilgili arkadaslardan yardim istiyorum ..
VESSELAM ..