<?xml version="1.0" encoding="UTF-8"?>
<tricks type="array">
  <trick>
    <category-id type="integer">1</category-id>
    <comments type="integer"></comments>
    <content nil="true"></content>
    <content-bbcode nil="true"></content-bbcode>
    <content-format>Textile</content-format>
    <content-html nil="true"></content-html>
    <content-textile nil="true"></content-textile>
    <created-at type="datetime">2009-09-23T19:29:43+02:00</created-at>
    <creator-id type="integer">192</creator-id>
    <deleted-at type="datetime" nil="true"></deleted-at>
    <file nil="true"></file>
    <id type="integer">1366</id>
    <lang-id type="integer" nil="true"></lang-id>
    <locale>en</locale>
    <nreports type="integer">0</nreports>
    <nvotes type="integer">5</nvotes>
    <permalink>set_up_a_secure_ssh_tunnel_proxy_and_surf_in_private</permalink>
    <published-at type="datetime">2009-09-24T05:15:16+02:00</published-at>
    <state>published</state>
    <summary>Do you want to bypass a firewall that has too many restrictions? Well, all you have to do is set up a secure SSH Tunnel. It's easy and once you do it, you can surf the web privately in addition to not being at the mercy of a network administrator who's decided to block your favorite sites.

In this HowTo, you'll learn how to create an SSH Tunnel Proxy and then set up your web browser to use it in Linux, Windows, and even Mac.</summary>
    <title>Set Up a Secure SSH Tunnel Proxy and Surf in Private</title>
    <updated-at type="datetime">2009-09-26T02:31:41+02:00</updated-at>
    <updater-id type="integer">110</updater-id>
    <url>http://www.netdip.com/ssh-tunnel-proxy-how-to-set-it-up-with-linux-windows-or-mac/</url>
    <url-code nil="true"></url-code>
  </trick>
  <trick>
    <category-id type="integer">2</category-id>
    <comments type="integer">#&lt;Comment:0x2b188422f4f8&gt;</comments>
    <content>&lt;h3&gt;Removing .NET ClickOnce Support from Firefox&lt;/h3&gt;


	&lt;table&gt;
		&lt;tr&gt;
			&lt;th&gt;Microsoft .NET Framework 3.5 Service Pack 1, released earlier this year, installs a Firefox extension which could not be uninstalled easily (registry hacking was needed). To make matters worse, this extension came with a pretty big security hole (at least, that&amp;#8217;s what everyone says). A newer version of this extension has been pushed out in May, which can be uninstalled the proper way. As it turns out, Firefox apparently has a limitation in that extensions installed at the machine level (instead of the user level) cannot be uninstalled from within the extensions &lt;span class=&quot;caps&quot;&gt;GUI&lt;/span&gt;.&lt;/th&gt;
		&lt;/tr&gt;
	&lt;/table&gt;




	&lt;p&gt;&lt;a href=&quot;http://www.osnews.com/story/21591&quot;&gt;story&lt;/a&gt;&lt;/p&gt;


	&lt;h3&gt;Stop-gap Solution To uninstall the ClickOnce support for Firefox from your machine&lt;/h3&gt;


	&lt;p&gt;&lt;a href=&quot;http://blogs.msdn.com/brada/archive/2009/02/27/uninstalling-the-clickonce-support-for-firefox.aspx&quot;&gt;Uninstalling the Clickonce Support for Firefox&lt;/a&gt;&lt;/p&gt;</content>
    <content-bbcode nil="true"></content-bbcode>
    <content-format>Textile</content-format>
    <content-html nil="true"></content-html>
    <content-textile>h3. Removing .NET ClickOnce Support from Firefox

|_. Microsoft .NET Framework 3.5 Service Pack 1, released earlier this year, installs a Firefox extension which could not be uninstalled easily (registry hacking was needed). To make matters worse, this extension came with a pretty big security hole (at least, that's what everyone says). A newer version of this extension has been pushed out in May, which can be uninstalled the proper way. As it turns out, Firefox apparently has a limitation in that extensions installed at the machine level (instead of the user level) cannot be uninstalled from within the extensions GUI.|

&quot;story&quot;:http://www.osnews.com/story/21591

h3. Stop-gap Solution To uninstall the ClickOnce support for Firefox from your machine

&quot;Uninstalling the Clickonce Support for Firefox&quot;:http://blogs.msdn.com/brada/archive/2009/02/27/uninstalling-the-clickonce-support-for-firefox.aspx</content-textile>
    <created-at type="datetime">2009-06-13T10:49:33+02:00</created-at>
    <creator-id type="integer">69</creator-id>
    <deleted-at type="datetime" nil="true"></deleted-at>
    <file nil="true"></file>
    <id type="integer">899</id>
    <lang-id type="integer" nil="true"></lang-id>
    <locale>en</locale>
    <nreports type="integer">0</nreports>
    <nvotes type="integer">6</nvotes>
    <permalink>uninstalling_the_clickonce_support_for_firefox</permalink>
    <published-at type="datetime">2009-06-15T04:09:31+02:00</published-at>
    <state>published</state>
    <summary>Microsoft is really making it hard not to distrust them, aren't they?</summary>
    <title>Uninstalling the Clickonce Support for Firefox</title>
    <updated-at type="datetime">2009-06-20T12:06:16+02:00</updated-at>
    <updater-id type="integer">110</updater-id>
    <url>http://blogs.msdn.com/brada/archive/2009/02/27/uninstalling-the-clickonce-support-for-firefox.aspx</url>
    <url-code nil="true"></url-code>
  </trick>
  <trick>
    <category-id type="integer">1</category-id>
    <comments type="integer"></comments>
    <content nil="true"></content>
    <content-bbcode nil="true"></content-bbcode>
    <content-format>Textile</content-format>
    <content-html nil="true"></content-html>
    <content-textile nil="true"></content-textile>
    <created-at type="datetime">2009-06-04T00:55:11+02:00</created-at>
    <creator-id type="integer">99</creator-id>
    <deleted-at type="datetime" nil="true"></deleted-at>
    <file nil="true"></file>
    <id type="integer">857</id>
    <lang-id type="integer" nil="true"></lang-id>
    <locale>en</locale>
    <nreports type="integer">0</nreports>
    <nvotes type="integer">3</nvotes>
    <permalink>install_and_configure_ipplan_ip_manager_in_opensuse</permalink>
    <published-at type="datetime">2009-06-05T19:11:07+02:00</published-at>
    <state>published</state>
    <summary>IPplan is a free opensource IP Address management application. IPPlan is a web based IP address management software and tracking tool simplifying the administration of your IP address space. IPplan goes beyond IP address management including DNS administration, configuration file management, circuit management and storing of hardware information.</summary>
    <title>Install &amp; Configure IPplan IP Manager in openSUSE</title>
    <updated-at type="datetime">2009-06-05T21:11:09+02:00</updated-at>
    <updater-id type="integer">110</updater-id>
    <url>http://www.susegeek.com/networking/install-configure-ipplan-ip-manager-in-opensuse/</url>
    <url-code nil="true"></url-code>
  </trick>
  <trick>
    <category-id type="integer">4</category-id>
    <comments type="integer"></comments>
    <content nil="true"></content>
    <content-bbcode nil="true"></content-bbcode>
    <content-format>Textile</content-format>
    <content-html nil="true"></content-html>
    <content-textile nil="true"></content-textile>
    <created-at type="datetime">2009-05-28T00:29:48+02:00</created-at>
    <creator-id type="integer">99</creator-id>
    <deleted-at type="datetime" nil="true"></deleted-at>
    <file nil="true"></file>
    <id type="integer">819</id>
    <lang-id type="integer" nil="true"></lang-id>
    <locale>en</locale>
    <nreports type="integer">0</nreports>
    <nvotes type="integer">1</nvotes>
    <permalink>highlight_domain_and_subdomain_for_ssl_websites_in_firefox</permalink>
    <published-at type="datetime" nil="true"></published-at>
    <state>queued</state>
    <summary>When you visit a Secure website in Firefox chances are that the FavIcon for the website is replaced with a Green bar with the details of the company. This is because of the default properties in Firefox to display detailed information of the website from the Extended Validation Certificate on the website. However, if the website doesn&#8217;t host a Extended Validation certificate then the website URL (link) in the address bar is not highlighted or in otherwords shows as a normal website URL.</summary>
    <title>Highlight Domain &amp; Subdomain for SSL websites in Firefox</title>
    <updated-at type="datetime">2009-05-28T00:29:48+02:00</updated-at>
    <updater-id type="integer">99</updater-id>
    <url>http://www.susegeek.com/internet-browser/highlight-domain-subdomain-for-ssl-websites-in-firefox/</url>
    <url-code nil="true"></url-code>
  </trick>
  <trick>
    <category-id type="integer">4</category-id>
    <comments type="integer"></comments>
    <content nil="true"></content>
    <content-bbcode nil="true"></content-bbcode>
    <content-format>HTML</content-format>
    <content-html nil="true"></content-html>
    <content-textile nil="true"></content-textile>
    <created-at type="datetime">2008-08-24T00:12:09+02:00</created-at>
    <creator-id type="integer">99</creator-id>
    <deleted-at type="datetime" nil="true"></deleted-at>
    <file nil="true"></file>
    <id type="integer">396</id>
    <lang-id type="integer" nil="true"></lang-id>
    <locale>en</locale>
    <nreports type="integer">0</nreports>
    <nvotes type="integer">2</nvotes>
    <permalink>nessus_vulnerability_scanner_in_opensuse</permalink>
    <published-at type="datetime" nil="true"></published-at>
    <state>queued</state>
    <summary>The Nessus vulnerability scanner, is the world-leader in active scanners, featuring high speed discovery, configuration auditing, asset profiling, sensitive data discovery and vulnerability analysis of your security posture. Nessus scanners can be distributed throughout an entire enterprise, inside DMZs, and across physically separate networks. Nessus can also be used for ad-hoc scanning, daily scans, and quick-response audits.</summary>
    <title>Nessus Vulnerability Scanner in openSUSE</title>
    <updated-at type="datetime">2008-08-29T11:32:06+02:00</updated-at>
    <updater-id type="integer">4</updater-id>
    <url>http://www.susegeek.com/security/nessus-vulnerability-scanner-in-opensuse/</url>
    <url-code nil="true"></url-code>
  </trick>
  <trick>
    <category-id type="integer">4</category-id>
    <comments type="integer">#&lt;Comment:0x2b18841f2080&gt;</comments>
    <content nil="true"></content>
    <content-bbcode nil="true"></content-bbcode>
    <content-format>HTML</content-format>
    <content-html nil="true"></content-html>
    <content-textile nil="true"></content-textile>
    <created-at type="datetime">2008-08-23T01:33:26+02:00</created-at>
    <creator-id type="integer">99</creator-id>
    <deleted-at type="datetime" nil="true"></deleted-at>
    <file nil="true"></file>
    <id type="integer">395</id>
    <lang-id type="integer" nil="true"></lang-id>
    <locale>en</locale>
    <nreports type="integer">0</nreports>
    <nvotes type="integer">3</nvotes>
    <permalink>acetoneiso2_a_full_feature_rich_image_iso_tool_for_opensuse</permalink>
    <published-at type="datetime">2008-08-29T09:32:19+02:00</published-at>
    <state>published</state>
    <summary>AcetoneISO2, is a feature-rich and complete software application to manage CD/DVD images. Thanks to powerful open source tools such as fuseiso, AcetoneISO2 will let You mount typical proprietary images formats of the Windows world such as ISO BIN NRG MDF IMG and is more than a simple ISO mount software.</summary>
    <title>Acetoneiso2 - A full feature rich Image/ISO tool for openSUSE</title>
    <updated-at type="datetime">2008-08-29T11:32:21+02:00</updated-at>
    <updater-id type="integer">4</updater-id>
    <url>http://www.susegeek.com/multimedia/acetoneiso2-a-full-feature-rich-imageiso-tool-for-opensuse/</url>
    <url-code nil="true"></url-code>
  </trick>
  <trick>
    <category-id type="integer">1</category-id>
    <comments type="integer"></comments>
    <content nil="true"></content>
    <content-bbcode nil="true"></content-bbcode>
    <content-format>Textile</content-format>
    <content-html nil="true"></content-html>
    <content-textile nil="true"></content-textile>
    <created-at type="datetime">2008-08-18T04:20:06+02:00</created-at>
    <creator-id type="integer">83</creator-id>
    <deleted-at type="datetime" nil="true"></deleted-at>
    <file nil="true"></file>
    <id type="integer">390</id>
    <lang-id type="integer" nil="true"></lang-id>
    <locale>en</locale>
    <nreports type="integer">0</nreports>
    <nvotes type="integer">2</nvotes>
    <permalink>how_to_know_if_your_dns_server_y_vulnerable</permalink>
    <published-at type="datetime" nil="true"></published-at>
    <state>queued</state>
    <summary>It is just so easy, you can doit in linux with one line.</summary>
    <title>How to know if your dns server is vulnerable!</title>
    <updated-at type="datetime">2009-02-27T10:04:15+01:00</updated-at>
    <updater-id type="integer">2</updater-id>
    <url>http://dclavijo.blogspot.com/2008/08/como-saber-si-nuestro-servidor-dns-es.html</url>
    <url-code nil="true"></url-code>
  </trick>
  <trick>
    <category-id type="integer">4</category-id>
    <comments type="integer"></comments>
    <content>DELETED</content>
    <content-bbcode nil="true"></content-bbcode>
    <content-format>HTML</content-format>
    <content-html nil="true"></content-html>
    <content-textile nil="true"></content-textile>
    <created-at type="datetime">2008-08-08T00:26:40+02:00</created-at>
    <creator-id type="integer">99</creator-id>
    <deleted-at type="datetime" nil="true"></deleted-at>
    <file nil="true"></file>
    <id type="integer">372</id>
    <lang-id type="integer" nil="true"></lang-id>
    <locale>en</locale>
    <nreports type="integer">0</nreports>
    <nvotes type="integer">1</nvotes>
    <permalink>truecrypt_free_opensource_on_the_fly_disk_encryption</permalink>
    <published-at type="datetime" nil="true"></published-at>
    <state>suspended</state>
    <summary>TrueCrypt is a free opensource software system for establishing and maintaining an on-the-fly-encrypted volume (data storage device). On-the-fly encryption means that data are automatically encrypted or decrypted right before they are loaded or saved, without any user intervention. No data stored on an encrypted volume can be read (decrypted) without using the correct password/keyfile(s) or correct encryption keys. Entire file system is encrypted (e.g., file names, folder names, contents of every file, free space, meta data, etc).</summary>
    <title>TrueCrypt - Free opensource on the fly Disk Encryption</title>
    <updated-at type="datetime">2008-08-10T13:07:04+02:00</updated-at>
    <updater-id type="integer">1</updater-id>
    <url nil="true"></url>
    <url-code nil="true"></url-code>
  </trick>
  <trick>
    <category-id type="integer">4</category-id>
    <comments type="integer">#&lt;Comment:0x2b18841cc380&gt;</comments>
    <content nil="true"></content>
    <content-bbcode nil="true"></content-bbcode>
    <content-format>HTML</content-format>
    <content-html nil="true"></content-html>
    <content-textile nil="true"></content-textile>
    <created-at type="datetime">2008-08-08T00:26:38+02:00</created-at>
    <creator-id type="integer">99</creator-id>
    <deleted-at type="datetime" nil="true"></deleted-at>
    <file nil="true"></file>
    <id type="integer">371</id>
    <lang-id type="integer" nil="true"></lang-id>
    <locale>en</locale>
    <nreports type="integer">0</nreports>
    <nvotes type="integer">1</nvotes>
    <permalink>truecrypt_free_opensource_on_the_fly_disk_encryption_tool</permalink>
    <published-at type="datetime" nil="true"></published-at>
    <state>queued</state>
    <summary>TrueCrypt is a free opensource software system for establishing and maintaining an on-the-fly-encrypted volume (data storage device). On-the-fly encryption means that data are automatically encrypted or decrypted right before they are loaded or saved, without any user intervention. No data stored on an encrypted volume can be read (decrypted) without using the correct password/keyfile(s) or correct encryption keys. Entire file system is encrypted (e.g., file names, folder names, contents of every file, free space, meta data, etc).</summary>
    <title>TrueCrypt - Free opensource on the fly Disk Encryption tool</title>
    <updated-at type="datetime">2008-08-08T00:26:38+02:00</updated-at>
    <updater-id type="integer">99</updater-id>
    <url>http://www.susegeek.com/security/truecrypt-free-opensource-on-the-fly-disk-encryption-tool/</url>
    <url-code nil="true"></url-code>
  </trick>
  <trick>
    <category-id type="integer">1</category-id>
    <comments type="integer"></comments>
    <content nil="true"></content>
    <content-bbcode nil="true"></content-bbcode>
    <content-format>Textile</content-format>
    <content-html nil="true"></content-html>
    <content-textile nil="true"></content-textile>
    <created-at type="datetime">2008-07-28T18:35:00+02:00</created-at>
    <creator-id type="integer">1</creator-id>
    <deleted-at type="datetime" nil="true"></deleted-at>
    <file nil="true"></file>
    <id type="integer">355</id>
    <lang-id type="integer" nil="true"></lang-id>
    <locale>en</locale>
    <nreports type="integer">0</nreports>
    <nvotes type="integer">5</nvotes>
    <permalink>how_to_patch_bind9_against_dns_cache_poisoning_on_debian_etch</permalink>
    <published-at type="datetime">2008-08-04T17:40:38+02:00</published-at>
    <state>published</state>
    <summary>This article explains how you can fix a BIND9 nameserver on a Debian Etch system so that it is not vulnerable anymore to DNS cache poisoning.</summary>
    <title>How To Patch BIND9 Against DNS Cache Poisoning On Debian Etch</title>
    <updated-at type="datetime">2008-08-12T23:35:57+02:00</updated-at>
    <updater-id type="integer">69</updater-id>
    <url>http://www.howtoforge.com/how-to-patch-bind-to-avoid-cache-poisoning-debian-etch</url>
    <url-code nil="true"></url-code>
  </trick>
  <trick>
    <category-id type="integer">1</category-id>
    <comments type="integer"></comments>
    <content nil="true"></content>
    <content-bbcode nil="true"></content-bbcode>
    <content-format>Textile</content-format>
    <content-html nil="true"></content-html>
    <content-textile nil="true"></content-textile>
    <created-at type="datetime">2008-07-28T18:34:03+02:00</created-at>
    <creator-id type="integer">1</creator-id>
    <deleted-at type="datetime" nil="true"></deleted-at>
    <file nil="true"></file>
    <id type="integer">354</id>
    <lang-id type="integer" nil="true"></lang-id>
    <locale>en</locale>
    <nreports type="integer">0</nreports>
    <nvotes type="integer">3</nvotes>
    <permalink>patch_bind_to_avoid_cache_poisoning_fedora_centos</permalink>
    <published-at type="datetime">2008-08-04T17:40:34+02:00</published-at>
    <state>published</state>
    <summary>Dan Kaminsky earlier this month announced a massive, multi-vendor issue with DNS that could allow attackers to compromise any name server. Here you'll learn how to patch bind on Fedora/CentOS.</summary>
    <title>Patch BIND To Avoid Cache Poisoning (Fedora/CentOS)</title>
    <updated-at type="datetime">2008-08-04T19:40:35+02:00</updated-at>
    <updater-id type="integer">2</updater-id>
    <url>http://www.howtoforge.com/how-to-patch-bind-to-avoid-cache-poisoning-fedora-centos</url>
    <url-code nil="true"></url-code>
  </trick>
  <trick>
    <category-id type="integer">1</category-id>
    <comments type="integer"></comments>
    <content nil="true"></content>
    <content-bbcode nil="true"></content-bbcode>
    <content-format>Textile</content-format>
    <content-html nil="true"></content-html>
    <content-textile nil="true"></content-textile>
    <created-at type="datetime">2008-07-17T14:36:01+02:00</created-at>
    <creator-id type="integer">83</creator-id>
    <deleted-at type="datetime" nil="true"></deleted-at>
    <file nil="true"></file>
    <id type="integer">331</id>
    <lang-id type="integer" nil="true"></lang-id>
    <locale>en</locale>
    <nreports type="integer">0</nreports>
    <nvotes type="integer">2</nvotes>
    <permalink>dns_resolution_with_tor_and_dnsmasq_in_spanish</permalink>
    <published-at type="datetime" nil="true"></published-at>
    <state>queued</state>
    <summary>This explains hoe to setup the experimental version of tor and dnsmasq as a dns-cache pointing to it it will require a tap interface.</summary>
    <title>DNS resolution with Tor and Dnsmasq (in spanish)</title>
    <updated-at type="datetime">2008-07-17T22:12:46+02:00</updated-at>
    <updater-id type="integer">4</updater-id>
    <url>http://dclavijo.blogspot.com/2008/07/resolucion-de-dns-con-tor-y-dnsmasq.html</url>
    <url-code nil="true"></url-code>
  </trick>
  <trick>
    <category-id type="integer">1</category-id>
    <comments type="integer">#&lt;Comment:0x2b18841953a8&gt;</comments>
    <content>&lt;h2&gt;Check the &lt;span class=&quot;caps&quot;&gt;DNS&lt;/span&gt; Server&lt;/h2&gt;


	&lt;p&gt;Click on the right side of &lt;a href=&quot;http://www.doxpara.com/&quot;&gt;http://www.doxpara.com/&lt;/a&gt; on &amp;#8220;Check My &lt;span class=&quot;caps&quot;&gt;DNS&lt;/span&gt;&amp;#8221;.&lt;/p&gt;


	&lt;p&gt;After a few seconds you see a dialog like&lt;/p&gt;


&lt;pre&gt;&lt;code&gt;
Your name server, at 125.123.2.11, appears vulnerable to DNS Cache Poisoning.
All requests came from the following source port: 51491
&lt;/code&gt;&lt;/pre&gt;

	&lt;h2&gt;What shall I do if it is vulnerable&lt;/h2&gt;


	&lt;p&gt;If it is your own &lt;span class=&quot;caps&quot;&gt;DNS&lt;/span&gt; Server please apply the latest security fixes otherwise contact you &lt;span class=&quot;caps&quot;&gt;ISP&lt;/span&gt; Provider.&lt;/p&gt;</content>
    <content-bbcode nil="true"></content-bbcode>
    <content-format>Textile</content-format>
    <content-html nil="true"></content-html>
    <content-textile>h2. Check the DNS Server

p. Click on the right side of &quot;http://www.doxpara.com/&quot;:http://www.doxpara.com/ on &quot;Check My DNS&quot;.


p. After a few seconds you see a dialog like

&lt;pre&gt;&lt;code&gt;
Your name server, at 125.123.2.11, appears vulnerable to DNS Cache Poisoning.
All requests came from the following source port: 51491
&lt;/code&gt;&lt;/pre&gt;


h2. What shall I do if it is vulnerable

p. If it is your own DNS Server please apply the latest security fixes otherwise contact you ISP Provider.</content-textile>
    <created-at type="datetime">2008-07-09T13:39:38+02:00</created-at>
    <creator-id type="integer">4</creator-id>
    <deleted-at type="datetime" nil="true"></deleted-at>
    <file nil="true"></file>
    <id type="integer">319</id>
    <lang-id type="integer" nil="true"></lang-id>
    <locale>en</locale>
    <nreports type="integer">0</nreports>
    <nvotes type="integer">5</nvotes>
    <permalink>check_if_your_dns_server_is_vulnerable_against_dns_cache_poisoning</permalink>
    <published-at type="datetime">2008-07-09T12:51:48+02:00</published-at>
    <state>published</state>
    <summary>Check if your DNS Server is vulnerable against DNS Cache Poisoning</summary>
    <title>Check if your DNS Server is vulnerable against DNS Cache Poisoni</title>
    <updated-at type="datetime">2008-07-10T05:25:15+02:00</updated-at>
    <updater-id type="integer">69</updater-id>
    <url>http://www.doxpara.com/</url>
    <url-code nil="true"></url-code>
  </trick>
  <trick>
    <category-id type="integer">1</category-id>
    <comments type="integer"></comments>
    <content nil="true"></content>
    <content-bbcode nil="true"></content-bbcode>
    <content-format>Textile</content-format>
    <content-html nil="true"></content-html>
    <content-textile nil="true"></content-textile>
    <created-at type="datetime">2008-07-03T17:06:08+02:00</created-at>
    <creator-id type="integer">1</creator-id>
    <deleted-at type="datetime" nil="true"></deleted-at>
    <file nil="true"></file>
    <id type="integer">309</id>
    <lang-id type="integer" nil="true"></lang-id>
    <locale>en</locale>
    <nreports type="integer">0</nreports>
    <nvotes type="integer">3</nvotes>
    <permalink>an_introduction_to_the_kismet_packet_sniffer</permalink>
    <published-at type="datetime">2008-07-05T10:12:59+02:00</published-at>
    <state>published</state>
    <summary>Kismet is a wireless &quot;detector, sniffer, and intrusion detection system,&quot; and one of the growing list of essential open source tools for computer network security professionals. Kismet runs on any POSIX-compliant platform, including Windows, Mac OS X, and BSD, but Linux is the preferred platform because it has more unencumbered RFMON-capable drivers than any of the others.</summary>
    <title>An introduction to the Kismet packet sniffer</title>
    <updated-at type="datetime">2008-07-05T12:13:02+02:00</updated-at>
    <updater-id type="integer">4</updater-id>
    <url>http://www.linux.com/feature/139754</url>
    <url-code nil="true"></url-code>
  </trick>
  <trick>
    <category-id type="integer">4</category-id>
    <comments type="integer"></comments>
    <content nil="true"></content>
    <content-bbcode nil="true"></content-bbcode>
    <content-format>Textile</content-format>
    <content-html nil="true"></content-html>
    <content-textile nil="true"></content-textile>
    <created-at type="datetime">2008-06-23T13:19:36+02:00</created-at>
    <creator-id type="integer">81</creator-id>
    <deleted-at type="datetime" nil="true"></deleted-at>
    <file nil="true"></file>
    <id type="integer">287</id>
    <lang-id type="integer" nil="true"></lang-id>
    <locale>en</locale>
    <nreports type="integer">0</nreports>
    <nvotes type="integer">6</nvotes>
    <permalink>gentoo_booting_encrypted_system_from_usb_stick</permalink>
    <published-at type="datetime">2008-06-23T13:16:44+02:00</published-at>
    <state>published</state>
    <summary>A tutorial that shows you how to encrypt the entire hard drive with LUKS, partition it with LVM, and boot it from USB stick. All done manually, but it follows the KISS principle (tries to keep things as simple as possible). If you want a no-frills, do it yourself guide on how to encrypt your entire hard disk and boot it from an USB stick, this article may be of use to you.</summary>
    <title>Gentoo: Booting encrypted system from USB stick</title>
    <updated-at type="datetime">2008-09-25T19:54:38+02:00</updated-at>
    <updater-id type="integer">111</updater-id>
    <url>http://www.gentoo-wiki.com/Booting_encrypted_system_from_USB_stick</url>
    <url-code nil="true"></url-code>
  </trick>
  <trick>
    <category-id type="integer">14</category-id>
    <comments type="integer"></comments>
    <content nil="true"></content>
    <content-bbcode nil="true"></content-bbcode>
    <content-format>Textile</content-format>
    <content-html nil="true"></content-html>
    <content-textile nil="true"></content-textile>
    <created-at type="datetime">2008-06-22T18:45:55+02:00</created-at>
    <creator-id type="integer">1</creator-id>
    <deleted-at type="datetime" nil="true"></deleted-at>
    <file nil="true"></file>
    <id type="integer">281</id>
    <lang-id type="integer" nil="true"></lang-id>
    <locale>en</locale>
    <nreports type="integer">0</nreports>
    <nvotes type="integer">3</nvotes>
    <permalink>intrusion_detection_for_php_applications_with_phpids</permalink>
    <published-at type="datetime">2008-06-22T20:54:51+02:00</published-at>
    <state>published</state>
    <summary>This tutorial explains how to set up PHPIDS on a web server with Apache2 and PHP5. PHPIDS (PHP-Intrusion Detection System) is a simple to use, well structured, fast and state-of-the-art security layer for your PHP based web application. It recognizes when an attacker tries to break your site and reacts in exactly the way you want it to.</summary>
    <title>Intrusion Detection For PHP Applications With PHPIDS</title>
    <updated-at type="datetime">2008-06-22T22:54:51+02:00</updated-at>
    <updater-id type="integer">16</updater-id>
    <url>http://www.howtoforge.com/intrusion-detection-for-php-applications-with-phpids</url>
    <url-code nil="true"></url-code>
  </trick>
  <trick>
    <category-id type="integer">4</category-id>
    <comments type="integer">#&lt;Comment:0x2b1884166328&gt;</comments>
    <content>&lt;h2&gt;Install&lt;/h2&gt;


	&lt;p&gt;Gentoo users do&lt;/p&gt;


&lt;pre&gt;&lt;code&gt;emerge -av vlock&lt;/code&gt;&lt;/pre&gt;

Debian (and *buntu) users have to type
&lt;pre&gt;&lt;code&gt;aptitude install vlock&lt;/code&gt;&lt;/pre&gt;

	&lt;h2&gt;Usage&lt;/h2&gt;


Lock the current screen (useful if you only want to lock a root shell)
&lt;pre&gt;&lt;code&gt;vlock -c&lt;/code&gt;&lt;/pre&gt;

Lock all ttys with
&lt;pre&gt;&lt;code&gt;vlock -a&lt;/code&gt;&lt;/pre&gt;

for more information and options study
&lt;pre&gt;&lt;code&gt;man vlock&lt;/code&gt;&lt;/pre&gt; or
&lt;pre&gt;&lt;code&gt;vlock --help&lt;/code&gt;&lt;/pre&gt;

	&lt;p&gt;Have a nice and secure day.&lt;/p&gt;</content>
    <content-bbcode nil="true"></content-bbcode>
    <content-format>Textile</content-format>
    <content-html nil="true"></content-html>
    <content-textile>h2. Install

Gentoo users do

&lt;pre&gt;&lt;code&gt;emerge -av vlock&lt;/code&gt;&lt;/pre&gt;

Debian (and *buntu) users have to type
&lt;pre&gt;&lt;code&gt;aptitude install vlock&lt;/code&gt;&lt;/pre&gt;

h2. Usage

Lock the current screen (useful if you only want to lock a root shell)
&lt;pre&gt;&lt;code&gt;vlock -c&lt;/code&gt;&lt;/pre&gt;

Lock all ttys with
&lt;pre&gt;&lt;code&gt;vlock -a&lt;/code&gt;&lt;/pre&gt;

for more information and options study
&lt;pre&gt;&lt;code&gt;man vlock&lt;/code&gt;&lt;/pre&gt; or
&lt;pre&gt;&lt;code&gt;vlock --help&lt;/code&gt;&lt;/pre&gt;

Have a nice and secure day.</content-textile>
    <created-at type="datetime">2008-06-15T20:09:06+02:00</created-at>
    <creator-id type="integer">4</creator-id>
    <deleted-at type="datetime" nil="true"></deleted-at>
    <file nil="true"></file>
    <id type="integer">256</id>
    <lang-id type="integer" nil="true"></lang-id>
    <locale>en</locale>
    <nreports type="integer">0</nreports>
    <nvotes type="integer">4</nvotes>
    <permalink>vlock_lock_your_screen_while_you_are_away_from_your_desk</permalink>
    <published-at type="datetime">2008-06-15T23:05:33+02:00</published-at>
    <state>published</state>
    <summary>Simple tool to lock your ttys to prevent others to access your computer.</summary>
    <title>vlock: Lock your screen while you are away from your desk</title>
    <updated-at type="datetime">2008-06-16T01:46:18+02:00</updated-at>
    <updater-id type="integer">70</updater-id>
    <url nil="true"></url>
    <url-code nil="true"></url-code>
  </trick>
  <trick>
    <category-id type="integer">7</category-id>
    <comments type="integer"></comments>
    <content>&lt;h2&gt;How it works&lt;/h2&gt;


	&lt;p&gt;They keyword is stored on the server, so it is never revealed to the client. Processing is performed on the server-side via an &lt;span class=&quot;caps&quot;&gt;AJAX&lt;/span&gt; request and the decrypted redirect is returned to the client, opening a mail composer window&#8230; just like normal mailto link.&lt;/p&gt;


	&lt;h2&gt;Usage&lt;/h2&gt;


	&lt;p&gt;&lt;a href=&quot;http://howflow.com/trick/file/220/cipher_mail.zip&quot;&gt;Download the plugin from the file area&lt;/a&gt; of this trick (the original svn is gone) and install it in &lt;strong&gt;vendor/plugins&lt;/strong&gt;.&lt;/p&gt;


&lt;pre&gt;
&lt;code&gt;
&amp;lt;%= ciphermail_to &quot;John Smith&quot;, &quot;someone@somedomain.com&quot; %&amp;gt;
&lt;/code&gt;
&lt;/pre&gt;

	&lt;h2&gt;Copyright&lt;/h2&gt;


	&lt;p&gt;Copyright &#169; 2007 Michael Behan aka &amp;#8220;JabberWock&amp;#8221; (jabberwock /AT tenebrous /DOT com) Released under the &lt;span class=&quot;caps&quot;&gt;BSD&lt;/span&gt; license&lt;/p&gt;</content>
    <content-bbcode nil="true"></content-bbcode>
    <content-format>Textile</content-format>
    <content-html nil="true"></content-html>
    <content-textile>h2. How it works

p. They keyword is stored on the server, so it is never revealed to the client. Processing is performed on the server-side via an AJAX request and the decrypted redirect is returned to the client, opening a mail composer window&#8230; just like normal mailto link.


h2. Usage

p. &quot;Download the plugin from the file area&quot;:http://howflow.com/trick/file/220/cipher_mail.zip of this trick (the original svn is gone) and install it in *vendor/plugins*.


&lt;pre&gt;
&lt;code&gt;
&lt;%= ciphermail_to &quot;John Smith&quot;, &quot;someone@somedomain.com&quot; %&gt;
&lt;/code&gt;
&lt;/pre&gt;


h2. Copyright

p. Copyright &#169; 2007 Michael Behan aka &quot;JabberWock&quot; (jabberwock /AT tenebrous /DOT com) Released under the BSD license</content-textile>
    <created-at type="datetime">2008-06-02T11:00:53+02:00</created-at>
    <creator-id type="integer">1</creator-id>
    <deleted-at type="datetime" nil="true"></deleted-at>
    <file>/var/rails/howflow/public/trick/file/220/cipher_mail.zip</file>
    <id type="integer">220</id>
    <lang-id type="integer" nil="true"></lang-id>
    <locale>en</locale>
    <nreports type="integer">0</nreports>
    <nvotes type="integer">1</nvotes>
    <permalink>rails_plugin_ciphermail_backup_archive_from_svn</permalink>
    <published-at type="datetime" nil="true"></published-at>
    <state>queued</state>
    <summary>CipherMail provides a safe alternative to the mail_to helper by hiding mailto links from e-mail harvesting bots. The generated output is completely obfuscated by a 1024 bit random key.</summary>
    <title>Rails Plugin CipherMail (Backup Archive from svn)</title>
    <updated-at type="datetime">2008-06-02T11:02:17+02:00</updated-at>
    <updater-id type="integer">1</updater-id>
    <url nil="true"></url>
    <url-code nil="true"></url-code>
  </trick>
  <trick>
    <category-id type="integer">1</category-id>
    <comments type="integer"></comments>
    <content nil="true"></content>
    <content-bbcode nil="true"></content-bbcode>
    <content-format>Textile</content-format>
    <content-html nil="true"></content-html>
    <content-textile nil="true"></content-textile>
    <created-at type="datetime">2008-06-02T09:41:29+02:00</created-at>
    <creator-id type="integer">8</creator-id>
    <deleted-at type="datetime" nil="true"></deleted-at>
    <file nil="true"></file>
    <id type="integer">219</id>
    <lang-id type="integer" nil="true"></lang-id>
    <locale>en</locale>
    <nreports type="integer">0</nreports>
    <nvotes type="integer">1</nvotes>
    <permalink>deploying_a_content_filtering_proxy_server_with_safesquid</permalink>
    <published-at type="datetime" nil="true"></published-at>
    <state>queued</state>
    <summary>A content filtering proxy server, helps distribute Internet access while providing control to the administrators over the content delivered. It is usually used in organizations or schools to ensure that Internet usage conforms to the local acceptable use policy.</summary>
    <title>Deploying A Content Filtering Proxy Server With SafeSquid</title>
    <updated-at type="datetime">2008-06-02T09:42:10+02:00</updated-at>
    <updater-id type="integer">8</updater-id>
    <url>http://www.howtoforge.com/content-filtering-proxy-safesquid</url>
    <url-code nil="true"></url-code>
  </trick>
  <trick>
    <category-id type="integer">2</category-id>
    <comments type="integer">#&lt;Comment:0x2b188413bd08&gt;</comments>
    <content nil="true"></content>
    <content-bbcode nil="true"></content-bbcode>
    <content-format>Textile</content-format>
    <content-html nil="true"></content-html>
    <content-textile nil="true"></content-textile>
    <created-at type="datetime">2008-05-26T07:44:07+02:00</created-at>
    <creator-id type="integer">8</creator-id>
    <deleted-at type="datetime" nil="true"></deleted-at>
    <file nil="true"></file>
    <id type="integer">199</id>
    <lang-id type="integer" nil="true"></lang-id>
    <locale>en</locale>
    <nreports type="integer">1</nreports>
    <nvotes type="integer">5</nvotes>
    <permalink>how_to_gain_system_level_access_to_windows_vista</permalink>
    <published-at type="datetime" nil="true"></published-at>
    <state>queued</state>
    <summary>This video shows how to gain system-level access to Windows Vista. No login required. This comes in handy if you've lost your password. All you need is a Linux live CD called BackTrack.</summary>
    <title>How to Gain System-Level Access To Windows Vista</title>
    <updated-at type="datetime">2008-05-27T17:33:24+02:00</updated-at>
    <updater-id type="integer">37</updater-id>
    <url>http://www.offensive-security.com/movies/vistahack/vistahack.html</url>
    <url-code>317cc4d2ea452a77cdc8ffd1e13ed40581633ec8</url-code>
  </trick>
  <trick>
    <category-id type="integer">1</category-id>
    <comments type="integer"></comments>
    <content nil="true"></content>
    <content-bbcode nil="true"></content-bbcode>
    <content-format>Textile</content-format>
    <content-html nil="true"></content-html>
    <content-textile nil="true"></content-textile>
    <created-at type="datetime">2008-05-22T17:59:48+02:00</created-at>
    <creator-id type="integer">8</creator-id>
    <deleted-at type="datetime" nil="true"></deleted-at>
    <file nil="true"></file>
    <id type="integer">192</id>
    <lang-id type="integer" nil="true"></lang-id>
    <locale>en</locale>
    <nreports type="integer">0</nreports>
    <nvotes type="integer">4</nvotes>
    <permalink>intrusion_detection_system_with_ossec_hids_and_ubuntu_hardy</permalink>
    <published-at type="datetime">2008-05-23T20:20:54+02:00</published-at>
    <state>published</state>
    <summary>OSSEC-HIDS is a host based intrusion detection system. It offers rootkit detection, file system integrity checks, log file analysis, time based alerting and active responses. This howto will walk you through the very simple installation of the OSSEC-HIDS application.</summary>
    <title>Intrusion detection system with OSSEC-HIDS and Ubuntu Hardy</title>
    <updated-at type="datetime">2008-05-23T23:20:21+02:00</updated-at>
    <updater-id type="integer">3</updater-id>
    <url>http://boilinglinux.blogspot.com/2008/05/intrusion-detection-system-with-ossec.html</url>
    <url-code nil="true"></url-code>
  </trick>
  <trick>
    <category-id type="integer">1</category-id>
    <comments type="integer">#&lt;Comment:0x2b1884124810&gt;</comments>
    <content>&lt;span class=&quot;caps&quot;&gt;NOTE&lt;/span&gt;: since fail2ban &amp;gt;=0.8.1 there is allready a the action file &amp;#8217;/etc/fail2ban/action.d/iptables-allports.conf&amp;#8217;.
&lt;br&gt;
if you use a version &amp;gt;=0.8.1 you can skip point 1 and 2 and continue with 3.
&lt;br&gt;
&lt;br&gt;
	&lt;p&gt;You must create two new files in /etc/fail2ban.&lt;/p&gt;


	&lt;p&gt;1. create /etc/fail2ban/action.d/iptables-allports.conf&lt;/p&gt;


	&lt;p&gt;2. insert the text below&lt;/p&gt;


&lt;pre&gt;
&lt;code&gt;

# Fail2Ban configuration file
#
# Author: Cyril Jaquier
# Modified: Yaroslav O. Halchenko &amp;lt;debian@onerussian.com&amp;gt;
#             made active on all ports from original iptables.conf
#
# $Revision: 658 $
#

[Definition]

# Option:  actionstart
# Notes.:  command executed once at the start of Fail2Ban.
# Values:  CMD
#
actionstart = iptables -N fail2ban-&amp;lt;name&amp;gt;
              iptables -A fail2ban-&amp;lt;name&amp;gt; -j RETURN
              iptables -I INPUT -p &amp;lt;protocol&amp;gt; -j fail2ban-&amp;lt;name&amp;gt;

# Option:  actionstop
# Notes.:  command executed once at the end of Fail2Ban
# Values:  CMD
#
actionstop = iptables -D INPUT -p &amp;lt;protocol&amp;gt; -j fail2ban-&amp;lt;name&amp;gt;
             iptables -F fail2ban-&amp;lt;name&amp;gt;
             iptables -X fail2ban-&amp;lt;name&amp;gt;

# Option:  actioncheck
# Notes.:  command executed once before each actionban command
# Values:  CMD
#
actioncheck = iptables -n -L INPUT | grep -q fail2ban-&amp;lt;name&amp;gt;

# Option:  actionban
# Notes.:  command executed when banning an IP. Take care that the
#          command is executed with Fail2Ban user rights.
# Tags:    &amp;lt;ip&amp;gt;  IP address
#          &amp;lt;failures&amp;gt;  number of failures
#          &amp;lt;time&amp;gt;  unix timestamp of the ban time
# Values:  CMD
#
actionban = iptables -I fail2ban-&amp;lt;name&amp;gt; 1 -s &amp;lt;ip&amp;gt; -j DROP

# Option:  actionunban
# Notes.:  command executed when unbanning an IP. Take care that the
#          command is executed with Fail2Ban user rights.
# Tags:    &amp;lt;ip&amp;gt;  IP address
#          &amp;lt;failures&amp;gt;  number of failures
#          &amp;lt;time&amp;gt;  unix timestamp of the ban time
# Values:  CMD
#
actionunban = iptables -D fail2ban-&amp;lt;name&amp;gt; -s &amp;lt;ip&amp;gt; -j DROP

[Init]

# Defaut name of the chain
#
name = default

# Option:  protocol
# Notes.:  internally used by config reader for interpolations.
# Values:  [ tcp | udp | icmp | all ] Default: tcp
#
protocol = all

&lt;/code&gt;
&lt;/pre&gt;

	&lt;p&gt;3. create /etc/fail2ban/filter.d/apache-w00tw00t.conf&lt;/p&gt;


	&lt;p&gt;4. insert the text below
(NOTE: maybe you must change the regex if you have a other logformat! you can test your regex with fail2ban-regex &amp;lt;FILE&amp;gt; &amp;lt;REGEX&amp;gt;)&lt;/p&gt;


&lt;pre&gt;
&lt;code&gt;

#&amp;lt;HOST&amp;gt; - - [29/Apr/2008:22:54:08 +0200] &quot;GET /w00tw00t.at.ISC.SANS.DFind:) HTTP/1.1&quot; 400 326

[Definition]

# Option:  failregex
# Notes.:  regex to match the w00tw00t scan messages in the logfile. The
#          host must be matched by a group named &quot;host&quot;. The tag &quot;&amp;lt;HOST&amp;gt;&quot; can
#          be used for standard IP/hostname matching.
# Values:  TEXT
failregex = ^&amp;lt;HOST&amp;gt; -.*&quot;GET \/w00tw00t\.at\.ISC\.SANS\.DFind\:\).*&quot;.*

# Option:  ignoreregex
# Notes.:  regex to ignore. If this regex matches, the line is ignored.
# Values:  TEXT

ignoreregex =

&lt;/code&gt;
&lt;/pre&gt;

	&lt;p&gt;5. edit your /etc/fail2ban/jail.conf and insert the text below to the end of file or wherever you want.&lt;/p&gt;


&lt;pre&gt;
&lt;code&gt;

[apache-w00tw00t]
enabled  = true
filter   = apache-w00tw00t
action   = iptables-allports[name=w00tw00t]
           mail-whois[name=w00tw00t, dest=&amp;lt;YOURMAIL&amp;gt;]
logpath  = /var/log/apache2/access_log
maxretry = 1
bantime  = 86400

&lt;/code&gt;
&lt;/pre&gt;

	&lt;p&gt;6. restart your fail2ban and wait for new mail :D&lt;/p&gt;</content>
    <content-bbcode>you must create two new files in /etc/fail2ban.

1. create /etc/fail2ban/action.d/iptables-complete.conf

2. insert the text below

[code]
[Definition]

# Option:  actionstart
# Notes.:  command executed once at the start of Fail2Ban.
# Values:  CMD
#
actionstart = iptables -N fail2ban-
              iptables -A fail2ban- -j RETURN
              iptables -I INPUT -j fail2ban-

# Option:  actionend
# Notes.:  command executed once at the end of Fail2Ban
# Values:  CMD
#
actionstop = iptables -D INPUT -j fail2ban-
             iptables -F fail2ban-
             iptables -X fail2ban-

# Option:  actioncheck
# Notes.:  command executed once before each actionban command
# Values:  CMD
#
actioncheck = iptables -n -L INPUT | grep -q fail2ban-

# Option:  actionban
# Notes.:  command executed when banning an IP. Take care that the
#          command is executed with Fail2Ban user rights.
# Tags:      IP address
#            number of failures
#            unix timestamp of the ban time
# Values:  CMD
#
actionban = iptables -I fail2ban- 1 -s  -j DROP

# Option:  actionunban
# Notes.:  command executed when unbanning an IP. Take care that the
#          command is executed with Fail2Ban user rights.
# Tags:      IP address
#            number of failures
#            unix timestamp of the ban time
# Values:  CMD
#
actionunban = iptables -D fail2ban- -s  -j DROP

[Init]

# Defaut name of the chain
#
name = default

# Option:  port
# Notes.:  specifies port to monitor
# Values:  [ NUM | STRING ]  Default:
#
port = ssh

# Option:  protocol
# Notes.:  internally used by config reader for interpolations.
# Values:  [ tcp | udp | icmp | all ] Default: tcp
#
protocol = all
[/code]

3. create /etc/fail2ban/filter.d/apache-w00tw00t.conf
4. insert the text below (NOTE: maybe you must change the regex if you have a other logformat!)

[code]
# - - [29/Apr/2008:22:54:08 +0200] &quot;GET /w00tw00t.at.ISC.SANS.DFind:) HTTP/1.1&quot; 400 326

[Definition]

# Option:  failregex
# Notes.:  regex to match the w00tw00t scan messages in the logfile. The
#          host must be matched by a group named &quot;host&quot;. The tag &quot;&quot; can
#          be used for standard IP/hostname matching.
# Values:  TEXT
failregex = ^ -.*&quot;GET \/w00tw00t\.at\.ISC\.SANS\.DFind\:\).*&quot;.*

# Option:  ignoreregex
# Notes.:  regex to ignore. If this regex matches, the line is ignored.
# Values:  TEXT

ignoreregex =
[/code]

5. edit your /etc/fail2ban/jail.conf and insert the text below to the end of file or wherever you want.

[code]
[apache-w00tw00t]
enabled  = true
filter   = apache-w00tw00t
action   = iptables-complete[name=w00tw00t]
           mail-whois[name=w00tw00t, dest=&amp;lt;YOURMAIL&amp;gt;]
logpath  = /var/log/apache2/access_log
maxretry = 1
bantime  = 86400
[/code]

6. restart your fail2ban and wait for new mail :D</content-bbcode>
    <content-format>Textile</content-format>
    <content-html nil="true"></content-html>
    <content-textile>NOTE: since fail2ban &gt;=0.8.1 there is allready a the action file '/etc/fail2ban/action.d/iptables-allports.conf'.
&lt;br&gt;
if you use a version &gt;=0.8.1 you can skip point 1 and 2 and continue with 3.
&lt;br&gt;
&lt;br&gt;
p. You must create two new files in /etc/fail2ban.

p. 1. create /etc/fail2ban/action.d/iptables-allports.conf 


p. 2. insert the text below

&lt;pre&gt;
&lt;code&gt;

# Fail2Ban configuration file
#
# Author: Cyril Jaquier
# Modified: Yaroslav O. Halchenko &lt;debian@onerussian.com&gt;
# 			made active on all ports from original iptables.conf
#
# $Revision: 658 $
#
 
[Definition]
 
# Option:  actionstart
# Notes.:  command executed once at the start of Fail2Ban.
# Values:  CMD
#
actionstart = iptables -N fail2ban-&lt;name&gt;
              iptables -A fail2ban-&lt;name&gt; -j RETURN
              iptables -I INPUT -p &lt;protocol&gt; -j fail2ban-&lt;name&gt;
 
# Option:  actionstop
# Notes.:  command executed once at the end of Fail2Ban
# Values:  CMD
#
actionstop = iptables -D INPUT -p &lt;protocol&gt; -j fail2ban-&lt;name&gt;
             iptables -F fail2ban-&lt;name&gt;
             iptables -X fail2ban-&lt;name&gt;
 
# Option:  actioncheck
# Notes.:  command executed once before each actionban command
# Values:  CMD
#
actioncheck = iptables -n -L INPUT | grep -q fail2ban-&lt;name&gt;
 
# Option:  actionban
# Notes.:  command executed when banning an IP. Take care that the
#          command is executed with Fail2Ban user rights.
# Tags:    &lt;ip&gt;  IP address
#          &lt;failures&gt;  number of failures
#          &lt;time&gt;  unix timestamp of the ban time
# Values:  CMD
#
actionban = iptables -I fail2ban-&lt;name&gt; 1 -s &lt;ip&gt; -j DROP
 
# Option:  actionunban
# Notes.:  command executed when unbanning an IP. Take care that the
#          command is executed with Fail2Ban user rights.
# Tags:    &lt;ip&gt;  IP address
#          &lt;failures&gt;  number of failures
#          &lt;time&gt;  unix timestamp of the ban time
# Values:  CMD
#
actionunban = iptables -D fail2ban-&lt;name&gt; -s &lt;ip&gt; -j DROP
 
[Init]
 
# Defaut name of the chain
#
name = default
 
# Option:  protocol
# Notes.:  internally used by config reader for interpolations.
# Values:  [ tcp | udp | icmp | all ] Default: tcp
#
protocol = all

&lt;/code&gt;
&lt;/pre&gt;

p. 3. create /etc/fail2ban/filter.d/apache-w00tw00t.conf


p. 4. insert the text below
(NOTE: maybe you must change the regex if you have a other logformat! you can test your regex with fail2ban-regex &amp;lt;FILE&amp;gt; &amp;lt;REGEX&amp;gt;)


&lt;pre&gt;
&lt;code&gt;

#&lt;HOST&gt; - - [29/Apr/2008:22:54:08 +0200] &quot;GET /w00tw00t.at.ISC.SANS.DFind:) HTTP/1.1&quot; 400 326

[Definition]

# Option:  failregex
# Notes.:  regex to match the w00tw00t scan messages in the logfile. The
#          host must be matched by a group named &quot;host&quot;. The tag &quot;&lt;HOST&gt;&quot; can
#          be used for standard IP/hostname matching.
# Values:  TEXT
failregex = ^&lt;HOST&gt; -.*&quot;GET \/w00tw00t\.at\.ISC\.SANS\.DFind\:\).*&quot;.*

# Option:  ignoreregex
# Notes.:  regex to ignore. If this regex matches, the line is ignored.
# Values:  TEXT

ignoreregex =


&lt;/code&gt;
&lt;/pre&gt;

p. 5. edit your /etc/fail2ban/jail.conf and insert the text below to the end of file or wherever you want.


&lt;pre&gt;
&lt;code&gt;

[apache-w00tw00t]
enabled  = true
filter   = apache-w00tw00t
action   = iptables-allports[name=w00tw00t]
           mail-whois[name=w00tw00t, dest=&lt;YOURMAIL&gt;]
logpath  = /var/log/apache2/access_log
maxretry = 1
bantime  = 86400


&lt;/code&gt;
&lt;/pre&gt;


p. 6. restart your fail2ban and wait for new mail :D</content-textile>
    <created-at type="datetime">2008-05-01T23:09:24+02:00</created-at>
    <creator-id type="integer">20</creator-id>
    <deleted-at type="datetime" nil="true"></deleted-at>
    <file>/var/rails/howflow/public/trick/file/124/apache-w00tw00t.conf.txt</file>
    <id type="integer">124</id>
    <lang-id type="integer" nil="true"></lang-id>
    <locale>en</locale>
    <nreports type="integer">0</nreports>
    <nvotes type="integer">4</nvotes>
    <permalink>block_w00tw00t_scan_hosts_with_fail2ban</permalink>
    <published-at type="datetime">2008-05-01T21:14:45+02:00</published-at>
    <state>published</state>
    <summary>here i explain my solution to ban a host that scans my system with dfind/w00tw00t.
this solution requires a preinstalled fail2ban.</summary>
    <title>block w00tw00t scan-hosts with fail2ban</title>
    <updated-at type="datetime">2008-06-22T21:01:21+02:00</updated-at>
    <updater-id type="integer">20</updater-id>
    <url nil="true"></url>
    <url-code nil="true"></url-code>
  </trick>
  <trick>
    <category-id type="integer">5</category-id>
    <comments type="integer">#&lt;Comment:0x2b1884113d80&gt;</comments>
    <content>&lt;p&gt;&lt;strong&gt;Please &lt;span class=&quot;caps&quot;&gt;DO NOT&lt;/span&gt; do this on a hard drive with valuable data on it&lt;/strong&gt;&lt;/p&gt;


	&lt;p&gt;Boot your favorite Linux live CD and (given that your hard disk is called /dev/hda) enter&lt;/p&gt;


&lt;code&gt;
&lt;pre&gt;

  hdparm -I /dev/hda

&lt;/pre&gt;
&lt;/code&gt;

	&lt;p&gt;Have a look at the very last line. If you can see something like this, your drive has the necessary feature:&lt;/p&gt;


&lt;code&gt;
&lt;pre&gt;

  66min for SECURITY ERASE UNIT.

or

  66min for SECURITY ERASE UNIT. 66min for ENHANCED SECURITY ERASE UNIT.

&lt;/pre&gt;
&lt;/code&gt;

	&lt;p&gt;Now you can erase your data with one of the following commands:&lt;/p&gt;


&lt;code&gt;
&lt;pre&gt;

  hdparm --security-erase /dev/hda

or

  hdparm --security-erase-enhanced /dev/hda

&lt;/pre&gt;
&lt;/code&gt;

	&lt;p&gt;The advantage of this procedure is that it even overwrites bad blocks. &amp;#8220;Enhanced&amp;#8221; means, that it overwrites the data with a random pattern.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Please &lt;span class=&quot;caps&quot;&gt;DO NOT&lt;/span&gt; do this on a hard drive with valuable data on it&lt;/strong&gt; You have been warned!&lt;/p&gt;</content>
    <content-bbcode nil="true"></content-bbcode>
    <content-format>Textile</content-format>
    <content-html nil="true"></content-html>
    <content-textile>p. *Please DO NOT do this on a hard drive with valuable data on it*


p. Boot your favorite Linux live CD and (given that your hard disk is called /dev/hda) enter


&lt;code&gt;
&lt;pre&gt;

  hdparm -I /dev/hda

&lt;/pre&gt;
&lt;/code&gt;


p. Have a look at the very last line. If you can see something like this, your drive has the necessary feature:


&lt;code&gt;
&lt;pre&gt;

  66min for SECURITY ERASE UNIT.

or

  66min for SECURITY ERASE UNIT. 66min for ENHANCED SECURITY ERASE UNIT.

&lt;/pre&gt;
&lt;/code&gt;


p. Now you can erase your data with one of the following commands:


&lt;code&gt;
&lt;pre&gt;

  hdparm --security-erase /dev/hda

or

  hdparm --security-erase-enhanced /dev/hda

&lt;/pre&gt;
&lt;/code&gt;


p. The advantage of this procedure is that it even overwrites bad blocks. &quot;Enhanced&quot; means, that it overwrites the data with a random pattern.


p. *Please DO NOT do this on a hard drive with valuable data on it* You have been warned!</content-textile>
    <created-at type="datetime">2008-04-26T13:12:47+02:00</created-at>
    <creator-id type="integer">1</creator-id>
    <deleted-at type="datetime" nil="true"></deleted-at>
    <file nil="true"></file>
    <id type="integer">95</id>
    <lang-id type="integer" nil="true"></lang-id>
    <locale>en</locale>
    <nreports type="integer">0</nreports>
    <nvotes type="integer">5</nvotes>
    <permalink>secure_erase_how_to_erase_a_hard_drive</permalink>
    <published-at type="datetime">2008-04-26T14:58:00+02:00</published-at>
    <state>published</state>
    <summary>If you want to erase all your data from a hard drive, hdparm is the right tool for this job.</summary>
    <title>Secure Erase: How to erase a hard drive</title>
    <updated-at type="datetime">2008-11-24T10:45:18+01:00</updated-at>
    <updater-id type="integer">69</updater-id>
    <url nil="true"></url>
    <url-code nil="true"></url-code>
  </trick>
  <trick>
    <category-id type="integer">1</category-id>
    <comments type="integer">#&lt;Comment:0x2b1884102300&gt;</comments>
    <content>&lt;pre&gt;
&lt;code&gt;
  #!/bin/sh
  for ip in `cat /var/log/apache2/error_log | grep w00tw00t | awk '{print $8}' | sed 's/]//g' | sort -ug`; do
    countoff=$[$countoff+1]
    countwoot=$[$countwoot+1]
    iptables -I INPUT -s $ip -j DROP
    iptables -I OUTPUT -s $ip -j DROP
  done
&lt;/code&gt;
&lt;/pre&gt;</content>
    <content-bbcode nil="true"></content-bbcode>
    <content-format>Textile</content-format>
    <content-html nil="true"></content-html>
    <content-textile>&lt;pre&gt;
&lt;code&gt;
  #!/bin/sh
  for ip in `cat /var/log/apache2/error_log | grep w00tw00t | awk '{print $8}' | sed 's/]//g' | sort -ug`; do
    countoff=$[$countoff+1]
    countwoot=$[$countwoot+1]
    iptables -I INPUT -s $ip -j DROP
    iptables -I OUTPUT -s $ip -j DROP
  done
&lt;/code&gt;
&lt;/pre&gt;</content-textile>
    <created-at type="datetime">2008-04-25T23:45:42+02:00</created-at>
    <creator-id type="integer">1</creator-id>
    <deleted-at type="datetime" nil="true"></deleted-at>
    <file nil="true"></file>
    <id type="integer">92</id>
    <lang-id type="integer" nil="true"></lang-id>
    <locale>en</locale>
    <nreports type="integer">0</nreports>
    <nvotes type="integer">3</nvotes>
    <permalink>blocking_dfind_scans_w00tw00t_with_iptables</permalink>
    <published-at type="datetime">2008-04-26T00:34:23+02:00</published-at>
    <state>published</state>
    <summary>If you find a lot of &quot;w00tw00t&quot; entries in your web server log files, this little script might be useful for you.</summary>
    <title>Blocking DFind scans (w00tw00t) with iptables</title>
    <updated-at type="datetime">2008-05-01T19:00:10+02:00</updated-at>
    <updater-id type="integer">1</updater-id>
    <url nil="true"></url>
    <url-code nil="true"></url-code>
  </trick>
  <trick>
    <category-id type="integer">4</category-id>
    <comments type="integer"></comments>
    <content nil="true"></content>
    <content-bbcode nil="true"></content-bbcode>
    <content-format nil="true"></content-format>
    <content-html nil="true"></content-html>
    <content-textile nil="true"></content-textile>
    <created-at type="datetime">2008-04-20T21:20:24+02:00</created-at>
    <creator-id type="integer">1</creator-id>
    <deleted-at type="datetime" nil="true"></deleted-at>
    <file nil="true"></file>
    <id type="integer">63</id>
    <lang-id type="integer" nil="true"></lang-id>
    <locale>en</locale>
    <nreports type="integer">0</nreports>
    <nvotes type="integer">3</nvotes>
    <permalink>harden_the_ubuntu_linux_kernel_with_sysctl</permalink>
    <published-at type="datetime" nil="true"></published-at>
    <state>queued</state>
    <summary>I ran across a nice sysctl.conf file that will help secure your computer and prevent many different attacks on your computer like Man In the Middle Attacks, Syn attacks, source routing scans/attacks, spoofing protection/logging, and many others.</summary>
    <title>Harden the Ubuntu Linux Kernel with sysctl</title>
    <updated-at type="datetime">2008-05-03T13:37:43+02:00</updated-at>
    <updater-id type="integer">4</updater-id>
    <url>http://www.ubuntu-unleashed.com/2008/04/howto-harden-ubuntu-linux-kernel-with.html</url>
    <url-code nil="true"></url-code>
  </trick>
  <trick>
    <category-id type="integer">4</category-id>
    <comments type="integer">#&lt;Comment:0x2b18840e7a28&gt;</comments>
    <content>tr -cd &quot;[:graph:]&quot; &lt; /dev/urandom | head -c 7</content>
    <content-bbcode>tr -cd &quot;[:graph:]&quot; &lt; /dev/urandom | head -c 7</content-bbcode>
    <content-format>BBCode</content-format>
    <content-html nil="true"></content-html>
    <content-textile nil="true"></content-textile>
    <created-at type="datetime">2008-04-13T16:28:59+02:00</created-at>
    <creator-id type="integer">4</creator-id>
    <deleted-at type="datetime" nil="true"></deleted-at>
    <file nil="true"></file>
    <id type="integer">15</id>
    <lang-id type="integer" nil="true"></lang-id>
    <locale>en</locale>
    <nreports type="integer">0</nreports>
    <nvotes type="integer">5</nvotes>
    <permalink>generate_a_random_secure_password</permalink>
    <published-at type="datetime">2008-04-14T12:20:10+02:00</published-at>
    <state>published</state>
    <summary>tr -cd &quot;[:graph:]&quot; &lt; /dev/urandom | head -c 7</summary>
    <title>Generate a random secure Password</title>
    <updated-at type="datetime">2008-05-12T22:39:47+02:00</updated-at>
    <updater-id type="integer">27</updater-id>
    <url nil="true"></url>
    <url-code nil="true"></url-code>
  </trick>
</tricks>
