<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugs.gentoo.org/bugzilla.dtd">

<bugzilla version="2.22.7"
          urlbase="http://bugs.gentoo.org/"
          maintainer="bugzilla@gentoo.org"
>

    <bug>
          <bug_id>73432</bug_id>
          
          <creation_ts>2004-12-05 04:08 0000</creation_ts>
          <short_desc>rkhunter cronjob script</short_desc>
          <delta_ts>2004-12-07 10:29:32 0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Gentoo Linux</product>
          <component>Ebuilds</component>
          <version>unspecified</version>
          <rep_platform>All</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          
          <priority>P2</priority>
          <bug_severity>enhancement</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>smouge@hotpop.com</reporter>
          <assigned_to>ka0ttic@gentoo.org</assigned_to>
          

      

      
          <long_desc isprivate="0">
            <who>smouge@hotpop.com</who>
            <bug_when>2004-12-05 04:08:56 0000</bug_when>
            <thetext>Regarding created file /etc/cron.daily/rkhunter

A couple of very small requests:

Would be nice to add to the cronjob script a line to update the rkhunter database like:

# first update the database
/usr/bin/rkhunter --update &amp;&gt; /dev/null

In this way the database gets updated everyday. Else wise the database never gets updated?

Also would be nice to add the creation of a logfile to the cron job settings:

RKHUNTER_EXEC=&quot;/usr/bin/rkhunter&quot;
RKHUNTER_OPTS=&quot;--checkall --cronjob --skip-keypress --createlogfile&quot;


Reproducible: Always
Steps to Reproduce:
1.
2.
3.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>ka0ttic@gentoo.org</who>
            <bug_when>2004-12-05 11:04:48 0000</bug_when>
            <thetext>Why, that&apos;s a great idea ;)

Especially the logfile, because if a user doesn&apos;t have a MTA setup, he&apos;ll never know the output of rkhunter...

I&apos;ll take care of this either some time today or first thing in the morning.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>ka0ttic@gentoo.org</who>
            <bug_when>2004-12-07 02:22:18 0000</bug_when>
            <thetext>Ok, since I&apos;m at least 10x more knowledgable wrt scripting than I was when I first wrote that cron job, I decided to rewrite it ;p

In addition to the stuff you have requested, I decided to add a couple other features (and even went as far as patching rkhunter&apos;s --createlogfile to accept an optional filename argument for specifying an alternate log file location).

I also added a SAVE_OLD_LOGS config option, so that old logs dont get overwritten every time rkhunter runs.  I&apos;ve also added a LOGFILE_PERMS option, in case the user would like different permissions (it&apos;s world readable by default).

rkhunter-1.1.8-r1 is in CVS.  Please test (mainly the cron script) if you could be so kind, and reopen this bug, if necessary.

Thanks for request; in addition to motivating me to provide a more enhanced cron script, you also gave me something to do at work last night ;)

Cheers.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>smouge@hotpop.com</who>
            <bug_when>2004-12-07 10:29:32 0000</bug_when>
            <thetext>Worked like a charm.

Many thanks. I also liked that you have placed the output of the update routine in the report mail.

</thetext>
          </long_desc>
      
    </bug>

</bugzilla>