<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <title>Blocking by Country Code - Apache Web servers - tribe.net</title>
  <link rel="alternate" href="http://apacheservers.tribe.net/thread/36bf0a56-f494-467b-b177-0efe357517a5?format=atom" />
  <subtitle>Tribe.net. Local Connections</subtitle>
  <entry>
    <title>Re: Blocking by Country Code</title>
    <link rel="alternate" href="http://ApacheServers.tribe.net/thread/36bf0a56-f494-467b-b177-0efe357517a5#87749b29-9f7a-40fe-9bc8-05e188aad5b5" />
    <author>
      <name>Stefan</name>
    </author>
    <id>http://ApacheServers.tribe.net/thread/36bf0a56-f494-467b-b177-0efe357517a5#87749b29-9f7a-40fe-9bc8-05e188aad5b5</id>
    <updated>2005-09-19T21:40:10Z</updated>
    <published>2005-09-19T21:40:10Z</published>
    <summary type="html">If you're really concerned about hackers, you may want to think about restricting them at the firewall level.&#xD;
&#xD;
Blocking them on the webserver level means that they already have some limited access to your network. Blocking from Apache will only protect Apache, and it's possible there are other vulnerabilities on that same machine, or on other machines which are on the same network.</summary>
    <dc:creator>Stefan</dc:creator>
    <dc:date>2005-09-19T21:40:10Z</dc:date>
  </entry>
  <entry>
    <title>Re: Blocking by Country Code</title>
    <link rel="alternate" href="http://ApacheServers.tribe.net/thread/36bf0a56-f494-467b-b177-0efe357517a5#7893c78f-ae62-4a6e-afa5-3c5e544a7b51" />
    <author>
      <name>$item.owner.firstName</name>
    </author>
    <id>http://ApacheServers.tribe.net/thread/36bf0a56-f494-467b-b177-0efe357517a5#7893c78f-ae62-4a6e-afa5-3c5e544a7b51</id>
    <updated>2005-09-18T00:22:55Z</updated>
    <published>2005-09-18T00:22:55Z</published>
    <summary type="html">Cesspools like Ukraine and Russia don't deserve to be on the Internet, so I just block them entirely - not just from Apache.&#xD;
Add this to your /ets/hosts.deny:&#xD;
ALL: .ru&#xD;
That keeps them out of everything.</summary>
    <dc:creator>$item.owner.firstName</dc:creator>
    <dc:date>2005-09-18T00:22:55Z</dc:date>
  </entry>
  <entry>
    <title>Re: Blocking by Country Code</title>
    <link rel="alternate" href="http://ApacheServers.tribe.net/thread/36bf0a56-f494-467b-b177-0efe357517a5#6e359acb-a0db-4061-b4c7-ae782289be16" />
    <author>
      <name>robt.</name>
    </author>
    <id>http://ApacheServers.tribe.net/thread/36bf0a56-f494-467b-b177-0efe357517a5#6e359acb-a0db-4061-b4c7-ae782289be16</id>
    <updated>2005-03-01T20:58:34Z</updated>
    <published>2005-03-01T20:58:34Z</published>
    <summary type="html">I'm going to 2nd the mod_security suggestion. I had a server up for close to 2 years without a firewall (aside from kernel level anti-spoofing and synflood protection with iptables/netfilter) simply by turning services off and using mod_security. It played hell with squirrell mail but some tweaking with httpd.conf (apache 1.3) and I was good to go. &#xD;
Now I don't think I ever got whacked but who can ever be sure :)&#xD;
&#xD;
Good luck!</summary>
    <dc:creator>robt.</dc:creator>
    <dc:date>2005-03-01T20:58:34Z</dc:date>
  </entry>
  <entry>
    <title>Re: Blocking by Country Code</title>
    <link rel="alternate" href="http://ApacheServers.tribe.net/thread/36bf0a56-f494-467b-b177-0efe357517a5#09ba3ea3-bfb3-4737-bd30-6e0d114400cc" />
    <author>
      <name>$item.owner.firstName</name>
    </author>
    <id>http://ApacheServers.tribe.net/thread/36bf0a56-f494-467b-b177-0efe357517a5#09ba3ea3-bfb3-4737-bd30-6e0d114400cc</id>
    <updated>2005-03-01T07:14:39Z</updated>
    <published>2005-03-01T07:14:39Z</published>
    <summary type="html">check out mod_security and mod_dosevasive.  This wont get you blocking by country code, but both can help you block weenies on the fly.</summary>
    <dc:creator>$item.owner.firstName</dc:creator>
    <dc:date>2005-03-01T07:14:39Z</dc:date>
  </entry>
  <entry>
    <title>Re: Blocking by Country Code</title>
    <link rel="alternate" href="http://ApacheServers.tribe.net/thread/36bf0a56-f494-467b-b177-0efe357517a5#efe9642d-00d6-41fc-ad9e-6225102dcc40" />
    <author>
      <name>Eli</name>
    </author>
    <id>http://ApacheServers.tribe.net/thread/36bf0a56-f494-467b-b177-0efe357517a5#efe9642d-00d6-41fc-ad9e-6225102dcc40</id>
    <updated>2005-03-01T01:35:10Z</updated>
    <published>2005-03-01T01:35:10Z</published>
    <summary type="html">That would be blocking by geolocation not country code. On the plus side, this can run much faster since you don't need to do DNS lookups. On the minus side, unless you subscribe to a service like Digital Envoy's NetAcuity ( http://www.digitalenvoy.net/ ) there is a lot of tweaking involved to stay on top of changes.&#xD;
&#xD;
I use NetAcuity from a PHP module for live website checking and from Perl for log processing. I don't pay the bills, though, and I have no idea how much it is costing. Probably in the four figures a year range. &#xD;
&#xD;
There are free tools, but I can't think of any names offhand. There are also published tables of which registry gives out which IPs which can be used to find the offending netblocks for "Deny x.y" statements.&#xD;
&#xD;
It is a nasty way to kill script kiddies though, since it also denies real visiters and doesn't stop kiddies who have compromised cable modem users in Idaho.</summary>
    <dc:creator>Eli</dc:creator>
    <dc:date>2005-03-01T01:35:10Z</dc:date>
  </entry>
  <entry>
    <title>Re: Blocking by Country Code</title>
    <link rel="alternate" href="http://ApacheServers.tribe.net/thread/36bf0a56-f494-467b-b177-0efe357517a5#c2842f73-5b78-4498-b445-39a6e0a53146" />
    <author>
      <name>Chas</name>
    </author>
    <id>http://ApacheServers.tribe.net/thread/36bf0a56-f494-467b-b177-0efe357517a5#c2842f73-5b78-4498-b445-39a6e0a53146</id>
    <updated>2005-02-28T19:34:08Z</updated>
    <published>2005-02-28T19:34:08Z</published>
    <summary type="html">What do you do if they are a .com, .net, .org or a host of other domain extentions that are used world wide?&#xD;
&#xD;
Need something that identifies where they are coming from and boots them before entry.</summary>
    <dc:creator>Chas</dc:creator>
    <dc:date>2005-02-28T19:34:08Z</dc:date>
  </entry>
  <entry>
    <title>Re: Blocking by Country Code</title>
    <link rel="alternate" href="http://ApacheServers.tribe.net/thread/36bf0a56-f494-467b-b177-0efe357517a5#92d5559a-e22d-4155-a43e-920f976727f7" />
    <author>
      <name>cjpa</name>
    </author>
    <id>http://ApacheServers.tribe.net/thread/36bf0a56-f494-467b-b177-0efe357517a5#92d5559a-e22d-4155-a43e-920f976727f7</id>
    <updated>2005-02-28T09:39:59Z</updated>
    <published>2005-02-28T09:39:59Z</published>
    <summary type="html">Something like this?&#xD;
&#xD;
&amp;amp;lt;Location /&gt;&#xD;
  order allow,deny&#xD;
  deny from *.ru&#xD;
&amp;amp;lt;/Location&gt;</summary>
    <dc:creator>cjpa</dc:creator>
    <dc:date>2005-02-28T09:39:59Z</dc:date>
  </entry>
  <entry>
    <title>Blocking by Country Code</title>
    <link rel="alternate" href="http://ApacheServers.tribe.net/thread/36bf0a56-f494-467b-b177-0efe357517a5#40fd9a97-64df-4248-9bef-7980389f3e03" />
    <author>
      <name>Chas</name>
    </author>
    <id>http://ApacheServers.tribe.net/thread/36bf0a56-f494-467b-b177-0efe357517a5#40fd9a97-64df-4248-9bef-7980389f3e03</id>
    <updated>2005-02-28T08:45:00Z</updated>
    <published>2005-02-28T08:45:00Z</published>
    <summary type="html">Does anyone know how to set up apache to restrict access based on county code? These script kiddies are driving me nuts and most of them are coming from Russia, the Ukraine and so on.&#xD;
&#xD;
Any help would be appreciated.</summary>
    <dc:creator>Chas</dc:creator>
    <dc:date>2005-02-28T08:45:00Z</dc:date>
  </entry>
</feed>



