<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Server on Inliniac</title>
    <link>https://inliniac.net/blog/tag/server/</link>
    <description>Recent content in Server on Inliniac</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 04 Jul 2007 21:10:36 +0000</lastBuildDate>
    <atom:link href="https://inliniac.net/blog/tag/server/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Migrating a Sguil server from 0.6.1 to 0.7.0 (CVS)</title>
      <link>https://inliniac.net/blog/2007/07/04/migrating-a-sguil-server-from-061-to-070-cvs/</link>
      <pubDate>Wed, 04 Jul 2007 21:10:36 +0000</pubDate>
      <guid>https://inliniac.net/blog/2007/07/04/migrating-a-sguil-server-from-061-to-070-cvs/</guid>
      <description>&lt;p&gt;Today I finally restored my server that used to host my blog, mail server and sguil server. The sguil server was still at 0.6.1 so this was a good time to see how a migration procedure would work (the earlier 0.7.0 test were done with a newly setup server). I haven&amp;rsquo;t been able to find documentation about this procedure, but it looks very straightforward, so I think I did it all right.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Sguil 0.7 CVS installation on Debian Etch</title>
      <link>https://inliniac.net/blog/2007/06/12/sguil-07-cvs-installation-on-debian-etch/</link>
      <pubDate>Tue, 12 Jun 2007 21:58:51 +0000</pubDate>
      <guid>https://inliniac.net/blog/2007/06/12/sguil-07-cvs-installation-on-debian-etch/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;http://sguil.sourceforge.net/&#34;&gt;Sguil&lt;/a&gt; 0.7 is getting shape quite nicely. One of the most interesting new features is the splitting up of different types of agents and the option to create &amp;rsquo;net groups&amp;rsquo;. This are groups of agents that Sguil considers part of the same network. You can use this to spread the agents over multiple servers, but still use it from Sguil as if it was one single sensor. For example, this way you can easily create a Snort sensor and a separate full content logging capture server. When you request the full content for a Snort event in Sguil, it will know that it needs to request the packet data from the capture server. This way you can also have multiple Snort agents without the need for capturing the same sancp and full content data over and over again.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
