<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blacklist on nagg.eu</title><link>https://nagg.eu/tags/blacklist/</link><description>Recent content in Blacklist on nagg.eu</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 13 Oct 2013 16:06:38 +0000</lastBuildDate><atom:link href="https://nagg.eu/tags/blacklist/index.xml" rel="self" type="application/rss+xml"/><item><title>ipset, a clever and effective way to block indesired hosts</title><link>https://nagg.eu/ipset-a-clever-and-effective-way-to-block-indesired-hosts/</link><pubDate>Sun, 13 Oct 2013 16:06:38 +0000</pubDate><guid>https://nagg.eu/ipset-a-clever-and-effective-way-to-block-indesired-hosts/</guid><description>&lt;p&gt;This post is meant to be the sequel of the one I wrote one month ago about &lt;!-- raw HTML omitted --&gt;CentOS as router, transparent proxy, and much more&lt;!-- raw HTML omitted --&gt;.&lt;br&gt;
A big chunk of the precedent article is on how configure squid and squidGuard to act as a transparent proxy with URLs filtering capabilities.&lt;br&gt;
But there&amp;rsquo;s a problem with that: nowadays many sites (f4c3b00k.c0m just to name the most annoying one) are HTTPS.&lt;br&gt;
With HTTP one can really easily intercept a packet and read the payload (which contains the URL) but with HTTPS this is not possible anymore since the payload is encrypted.&lt;br&gt;
The only way to be able to read the payload of an HTTPS packet is doing a man-in-the-middle attack with a fake certificate, but that&amp;rsquo;s not advisable and you really don&amp;rsquo;t wanna do it.&lt;br&gt;
If, like in my case, we are not interested in what the users are doing but we just want them to not be able to access some sites/services/whatever ipset (combined with iptables) are the right tools for the job.&lt;br&gt;
iptables is a pretty powerful tool, the only real issue is that it doesn&amp;rsquo;t scale pretty well if the number of the rules is very big, and this is not a good thing since we probably want to blacklist thousands of IPs.&lt;br&gt;
And here comes ipset: with it it&amp;rsquo;s possible to manage huge blacklists without iptables slowing down.&lt;/p&gt;</description></item><item><title>CentOS as router, transparent proxy, and much more</title><link>https://nagg.eu/centos-as-router-transparent-proxy-and-much-more/</link><pubDate>Mon, 16 Sep 2013 18:59:19 +0000</pubDate><guid>https://nagg.eu/centos-as-router-transparent-proxy-and-much-more/</guid><description>&lt;p&gt;As usual, long story short: I&amp;rsquo;ve to setup a firewall to log traffic, block some stuff and do some other things.&lt;br&gt;
– epel repo is required –&lt;br&gt;
The system is made of a single CentOS machine with 2 physical network adapters:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;eth0, connected to WAN, static IP address 192.168.0.3&lt;/li&gt;
&lt;li&gt;eth1, connected to LAN, static IP address 10.0.0.1/24&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id="-network-adapters-configuration"&gt;.:. Network adapters configuration&lt;/h2&gt;
&lt;p&gt;WAN network adapter:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;[root@CentOS ~]# vi /etc/sysconfig/network-scripts/ifcfg-eth0

DEVICE=&amp;#34;eth0&amp;#34;
BOOTPROTO=&amp;#34;none&amp;#34;
HWADDR=&amp;#34;**:**:**:**:**:**&amp;#34;
IPADDR=192.168.0.3
NETMASK=255.255.255.0
GATEWAY=192.168.0.1
DNS=192.168.0.1
IPV6INIT=&amp;#34;yes&amp;#34;
IPV6_AUTOCONF=&amp;#34;yes&amp;#34;
NM_CONTROLLED=&amp;#34;yes&amp;#34;
ONBOOT=&amp;#34;yes&amp;#34;
TYPE=&amp;#34;Ethernet&amp;#34;
UUID=&amp;#34;***&amp;#34;
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;LAN network adapter:&lt;/p&gt;</description></item></channel></rss>