<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: File Baselining in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/file-baselining/m-p/3844644#M738962</link>
    <description>Tripwire has been ported to HPUX.  I believe that is an HPUX distribution - check out software.hp.com.</description>
    <pubDate>Wed, 16 Aug 2006 11:03:48 GMT</pubDate>
    <dc:creator>TwoProc</dc:creator>
    <dc:date>2006-08-16T11:03:48Z</dc:date>
    <item>
      <title>File Baselining</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-baselining/m-p/3844643#M738961</link>
      <description>We have been using a tool that is now no longer supported to run file baselines in order to identify files that have been changed. I understand that there are some native HP utilities that can checksum files and therefore perform the same functionality - is anyone doing anything similar and if so what tool(s) are you using</description>
      <pubDate>Wed, 16 Aug 2006 10:58:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-baselining/m-p/3844643#M738961</guid>
      <dc:creator>doubletake</dc:creator>
      <dc:date>2006-08-16T10:58:20Z</dc:date>
    </item>
    <item>
      <title>Re: File Baselining</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-baselining/m-p/3844644#M738962</link>
      <description>Tripwire has been ported to HPUX.  I believe that is an HPUX distribution - check out software.hp.com.</description>
      <pubDate>Wed, 16 Aug 2006 11:03:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-baselining/m-p/3844644#M738962</guid>
      <dc:creator>TwoProc</dc:creator>
      <dc:date>2006-08-16T11:03:48Z</dc:date>
    </item>
    <item>
      <title>Re: File Baselining</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-baselining/m-p/3844645#M738963</link>
      <description>Tripwire will do it or you can do a homegrown solution built around cksum. The idea is that create a database (which might be a flat file) that contains the pathname, time of last modication, file size, mode, owner, group, and a cksum. You then periodically check the files listed in the database against their current versions. I done a homemade solution in Perl that satifies my SOX guys but then again I had been doing that for years before SOX was even thought of.&lt;BR /&gt;</description>
      <pubDate>Wed, 16 Aug 2006 11:11:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-baselining/m-p/3844645#M738963</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2006-08-16T11:11:51Z</dc:date>
    </item>
    <item>
      <title>Re: File Baselining</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/file-baselining/m-p/3844646#M738964</link>
      <description>HP's IDS9000 is still out there.  It will ( or at least used to ) monitor critical files for changes.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 16 Aug 2006 13:21:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/file-baselining/m-p/3844646#M738964</guid>
      <dc:creator>Tim Nelson</dc:creator>
      <dc:date>2006-08-16T13:21:22Z</dc:date>
    </item>
  </channel>
</rss>

