Anti-hacker

Quote:

---

Originally Posted by Gregoory

5. If your own IP is caught into the process you won't be able to access the host anymore :lol:

---

This is why you add yourself, and another "known good" IP to the Allow list :wink:
I wish the documentation on PeerBlock was better. I can't see anything that says you can pass information on the command line... I'll keep digging.

Yes, on older versions of Windows you could add an IP alias to %windir%\Drivers\etc\hosts and point it to 127.0.0.1 and that would effectively block all access to or from that IP... but it's kind of a glitch in LanManager that allows that IMS. I think SMB sees the IP as being a PC on your LAN (not good for security at all) but then tries to resolve it's IP (from the IP... this is the glitch) and the internal cache says it is 127.0.0.1, and your PC happily talks to it's self... getting no sensible answer, it usually hangs up. XD

Don't know if that still works on newer OS though.

Quote:

---

Originally Posted by bobsobol

This is why you add yourself, and another "known good" IP to the Allow list :wink:
I wish the documentation on PeerBlock was better. I can't see anything that says you can pass information on the command line... I'll keep digging.

---

You might want to try and read my post again, since I've never mentionned passing commands to peerblock (making your reference to an allow list pointless) :] .
I said muting IPs until you refresh peerblock's cache. This action (refreshing) has to be done manually as far as I know.

True... wishful thinking? XD

Quote:

---

tell your server to "stop answering"

---

Are we talking Server "system" or Server "Application"? I presume the former... but you can add IPs to the SQL database "baduser" with some versions of the dreaded SQL.dll I believe.

There are other means of filtering TCP/IP communication with a file... a Firewall (like PeerBlock) is the most common, but a gateway application, or server is another. Many NAT Routers (which perform Gateway functionality internally) can be programmed to block IPs via their web interface... this can easily be scripted via cURL / lib.cURL. You would need a different script for each router and each firmware revision however, and in any case, most of you rent a Dedi, and aren't given access to it's Router. XD

Systems like Squid or DeleGate are programmed via lists (like PeerBlock) and can be told to refresh their list data while running... Squid also has built-in web interfaces for live filter update. ^^

To make these work, you proxy your true server to the Gateway system (program or machine), and users then connect to that. Use your regular firewall to ensure that the true servers game port is not accessible from outside, so users can only connect via the proxy, and ensure that the gateway proxy passes on the TCP/IP headers containing the true users IP and, or MAC for return communications... Some "cheap" firewalls may block this communication... bad news, because if they block traffic from a safe IP which has the header of a bad IP, they may allow traffic from a bad IP with the header of a safe one. (IP spoofing)

A BSD box (even a virtual one) should have sufficient control over it's native BSD socket library (the route source of winsock.dll) to be able to act as a NAT router / firewall / gateway server without installing any "software" on top of the OS. I'm not proficient enough to give a guide on how to do that though. XD

[post removed]