Quote:
Originally posted by MrJoe
Not gtk-gnutella's fault. And not that much that can be done about it. Except for fixing the faulty client. |
This may not be the right place to ask, but how this "forwarding alternate locations" thing works?
Is it so essential feature, that if gtk-gnutella and other clients would refuse to believe forwarded alternate locations to ports 0-1024 are valid, but must be bogus, it would make gnet worse?
Because I see a security risk here, if crackers start to use this to cause DDOS to http, ftp, *- servers; they will get more reasons to ban gnutella-clients on hosts of ISPs' customers. There is also other instances which would like to harm gnet.
And for Apache-users, putting these two lines to /etc/httpd/conf/httpd.conf helps (but won't solve the problem):
SetEnvIf Request_URI /uri-res/N2R gnet-request
CustomLog logs/access_log combined env=!gnet-request
See
http://httpd.apache.org/docs/mod/mod_log_config.html