On 10/11/2009, John Horne (john.ho...@plymouth.ac.uk) wrote:
> At that time the Linux os_specific test did just the one test, so
> disabling 'os_specific' was valid at that time.
Gotcha... thanks again...
--
Come build wi
On Sun, 2009-10-11 at 18:00 -0400, Tanstaafl wrote:
> On 10/11/2009 5:30 PM, John Horne wrote:
> >> I found a recommendation to disable the 'os_specific' check in
> >> DISABLED_TESTS in rkhunter.conf to fix this
>
> > The config file provided by us makes no such recommendation.
>
> Sorry, I was n
On 10/11/2009 5:30 PM, John Horne wrote:
>> I found a recommendation to disable the 'os_specific' check in
>> DISABLED_TESTS in rkhunter.conf to fix this
> The config file provided by us makes no such recommendation.
Sorry, I was not clear... the recommendation I found was while googling...
Heh
On Sun, 2009-10-11 at 16:37 -0400, Tanstaafl wrote:
>
> I found a recommendation to disable the 'os_specific' check in
> DISABLED_TESTS in rkhunter.conf to fix this
>
The config file provided by us makes no such recommendation.
> , but, what other tests/checks are being disabled by this? Or is it
Hello,
New to rkhunter, just installed 1.3.4 and had a question.
On the first run I had some of the normal false positives and fixed them
(whitelisted the 3 commands that are replaced by scripts on my system
(normal), and whitelisted the hidden .udev directory), but I want to be
sure about what d