Quote:
Originally posted by El Demonio
Ok, in about 10 mins i'll be uploading the proxy list to one junior site: http://www.bulkporn.com/plist.txt
So everyone can get it.
On vik, YES YOU CAN!, on Unix, the instruction reads as:
/sbin/route -n add -host x.x.x.x -gateway y.y.y.y -reject
x.x.x.x is your target IP to be blocked
y.y.y.y is a null or void IP
and in the .htaccess file:
deny from x.x.x.x
now you can grab the file plist.txt and add it at the end of your .htaccess file and that will solve the immediate problem, check your error log for heavily repeating IP's and get those blocked with the route instruction above.
I strongly believe in the sense of 'collective', but i wont release my code to anyone, some hacker can be reading this and can reverse engineer my code and find a loophole.
|
My manpages on route specifically state that it should not be used for firewalling. I would think ipchains/iptables(linux) or whatever command is used on your particular system would be a better way, just drop the packet coming in rather than try to reply to it and fail a route lookup, generating a host-unreachable error and all that. Also, adding records on the webserver is kinda pointless if the machine can't be reached anyway, or am I missing something?