<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Books on Inliniac</title>
    <link>https://inliniac.net/blog/category/books/</link>
    <description>Recent content in Books on Inliniac</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 31 Mar 2010 13:15:38 +0000</lastBuildDate>
    <atom:link href="https://inliniac.net/blog/category/books/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Book review: Magnus Mischel - ModSecurity 2.5</title>
      <link>https://inliniac.net/blog/2010/03/31/book-review-magnus-mischel-modsecurity-2-5/</link>
      <pubDate>Wed, 31 Mar 2010 13:15:38 +0000</pubDate>
      <guid>https://inliniac.net/blog/2010/03/31/book-review-magnus-mischel-modsecurity-2-5/</guid>
      <description>&lt;p&gt;It&amp;rsquo;s been quite a while since I received my review copy of Magnus Mischel&amp;rsquo;s ModSecurity book titled &amp;ldquo;ModSecurity 2.5&amp;rdquo; but I finally found the time to read it and write up my review. As the title suggest it&amp;rsquo;s a book about the ModSecurity Web Application Firewall (WAF) module for Apache and about version 2.5 of it specifically. There are some books about the 1.x series of ModSecurity. It&amp;rsquo;s great that there is a book about the 2.x ModSecurity series now as ModSecurity 2.x is very different from the 1.x series.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Setting up Subversion for Snort_inline</title>
      <link>https://inliniac.net/blog/2007/01/17/setting-up-subversion-for-snort_inline/</link>
      <pubDate>Wed, 17 Jan 2007 11:02:31 +0000</pubDate>
      <guid>https://inliniac.net/blog/2007/01/17/setting-up-subversion-for-snort_inline/</guid>
      <description>&lt;p&gt;A reason for the slow development of Snort_inline is that we still weren&amp;rsquo;t using a version control system. Being sick of this, I decided to setup a private Subversion server to see how we could best use it. One thing that complicates the use of such a system is the fact that we maintain a patch on top of source code not maintained by ourselves. So the system must be able to deal with upstream sourcecode updates.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Books: Preventing Webattacks with Apache</title>
      <link>https://inliniac.net/blog/2006/07/10/books-preventing-webattacks-with-apache/</link>
      <pubDate>Mon, 10 Jul 2006 21:54:51 +0000</pubDate>
      <guid>https://inliniac.net/blog/2006/07/10/books-preventing-webattacks-with-apache/</guid>
      <description>&lt;p&gt;I just finished Preventing Webattacks with Apache by Ryan C. Barnett. Even though the title says it is about Apache it is really mostly about Mod_Security, and this is why i really love the book.&lt;/p&gt;&#xA;&lt;p&gt;Especially cool is the part of the book where the author challenges the user to setup his &amp;lsquo;Buggy Bank&amp;rsquo; example application to play with the vulnarebilities and with the possible counter measures.&lt;/p&gt;&#xA;&lt;p&gt;This book got me even more exited about Mod_Security, which I use already to protect one webserver. I plan to check out setting up a reverse filtering web proxy soon.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
