<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Naxsi on iMil.net</title>
    <link>http://imil.net/blog/tags/naxsi/</link>
    <description>Recent content in Naxsi on iMil.net</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 12 Jan 2013 16:37:36 +0000</lastBuildDate>
    <atom:link href="http://imil.net/blog/tags/naxsi/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Lazy learning</title>
      <link>http://imil.net/blog/posts/2013/lazy-learning/</link>
      <pubDate>Sat, 12 Jan 2013 16:37:36 +0000</pubDate>
      <guid>http://imil.net/blog/posts/2013/lazy-learning/</guid>
      <description>&lt;p&gt;So you want to use &lt;a href=&#34;http://code.google.com/p/naxsi/&#34;&gt;Naxsi&lt;/a&gt; but you&amp;rsquo;re too lazy to analyze your &lt;em&gt;nginx&lt;/em&gt;&amp;rsquo;s error log in order to write your own whitelists, and you&amp;rsquo;re definitely not brave enough to run a &lt;em&gt;learning mode&lt;/em&gt; for a week. Relax, they&amp;rsquo;ve got something for you too. &lt;em&gt;Rendez-vous&lt;/em&gt; in the &lt;a href=&#34;http://code.google.com/p/naxsi/downloads/list&#34;&gt;Downloads&lt;/a&gt; area of Naxsi&amp;rsquo;s website and retrieve latest &lt;em&gt;naxsi-ui&lt;/em&gt; archive. Within that tarball, you will only need 2 &lt;em&gt;python&lt;/em&gt; scripts, &lt;code&gt;nx_intercept.py&lt;/code&gt; and &lt;code&gt;nx_extract.py&lt;/code&gt;. The first one will read and record all Naxsi matches from the error log, while the second will generate the whitelist.&#xA;In order to make those scripts work, you will need &lt;em&gt;python-twisted&lt;/em&gt;, which is available for pretty much every decent UNIX-like I&amp;rsquo;m aware of. Default configuration file, &lt;code&gt;naxsi-ui.conf&lt;/code&gt;, will do the job as it is.&#xA;Here&amp;rsquo;s a tiny piece of script which reads all of your log files, pass them to the &lt;code&gt;nx_*&lt;/code&gt; scripts and will display all the associated whitelist rules to &lt;code&gt;stdout&lt;/code&gt;:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Wordpress 3.5 and Naxsi (update 7, now in production)</title>
      <link>http://imil.net/blog/posts/2012/wordpress-3-5-and-naxsi/</link>
      <pubDate>Sun, 30 Dec 2012 23:17:33 +0000</pubDate>
      <guid>http://imil.net/blog/posts/2012/wordpress-3-5-and-naxsi/</guid>
      <description>&lt;p&gt;&lt;em&gt;&lt;strong&gt;Update&lt;/strong&gt;: This setup is now in production, you are actually reading this blog through a Naxsi protected WordPress !&lt;/em&gt;&#xA;&lt;em&gt;&lt;strong&gt;Update 2&lt;/strong&gt;: This setup is also in production on &lt;a href=&#34;http://www.gcu-squad.org/2013/02/come-at-me-bro/&#34;&gt;GCU-Squad&lt;/a&gt;&amp;rsquo;s Website.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;!-- raw HTML omitted --&gt;I&amp;rsquo;m slowly preparing iMil.net migration to a new server. Yeah, it&amp;rsquo;s a bit confusing to be the CTO of a hosting company and having my personnal website elsewhere, but you know, time and stuff&amp;hellip; anyway, it&amp;rsquo;s coming.&lt;!-- raw HTML omitted --&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Ça va pas être possible avec vos baskets</title>
      <link>http://imil.net/blog/posts/2012/ca-va-pas-etre-possible-avec-vos-baskets/</link>
      <pubDate>Sun, 22 Apr 2012 10:42:57 +0000</pubDate>
      <guid>http://imil.net/blog/posts/2012/ca-va-pas-etre-possible-avec-vos-baskets/</guid>
      <description>&lt;p&gt;Dans &lt;a href=&#34;http://www.nbs-system.com&#34;&gt;ma boîte&lt;/a&gt;, l&amp;rsquo;équipe sécurité a publié voila quelques mois de cela un module pour &lt;a href=&#34;http://wiki.nginx.org/Main&#34;&gt;nginx&lt;/a&gt;: un firewall applicatif du nom de &lt;a href=&#34;http://code.google.com/p/naxsi/&#34;&gt;naxsi&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Ce module, sous licence GPLv2, je viens de le publier dans &lt;em&gt;pkgsrc current&lt;/em&gt; sous la forme d&amp;rsquo;une option de &lt;code&gt;www/nginx&lt;/code&gt;. Je me propose de vous montrer ici comment sécuriser simplement votre serveur web / proxy inverse &lt;em&gt;nginx&lt;/em&gt; grâce à &lt;em&gt;naxsi&lt;/em&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Premièrement, si comme moi (et comme il se doit) vous utilisez une branche stable de &lt;em&gt;pkgsrc&lt;/em&gt;, mettez simplement à jour &lt;code&gt;www/nginx&lt;/code&gt; comme ceci:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
