> kles koe wrote:
>
> > why don't you just ask the author of rkhunter to update the hashes
> > for these packges?
> > i think i did once and it was fixed within a few days.
>
> I said I already reported this issue twice, but so far I haven't
> received any reaction and the latest version of t
kles koe wrote:
why don't you just ask the author of rkhunter to update the hashes
for these packges?
i think i did once and it was fixed within a few days.
I said I already reported this issue twice, but so far I haven't
received any reaction and the latest version of the hashes still
d
Nils Breunese (Lemonbit Internet) wrote:
> Max Pyziur wrote:
>
>>> I have an FC2 system which rkhunter reports some suspicious
>>> files. In particular, during the MD5 hash scan, it reports
>>>
>>> /bin/dmesg
>>> /bin/kill
>>> /bin/login
>>> /bin/mount
>>> /usr/bin/kill
>>
>>
>
why don't you just ask the author of rkhunter to update the hashes for these
packges?
i think i did once and it was fixed within a few days.
From: "Nils Breunese (Lemonbit Internet)" <[EMAIL PROTECTED]>
Reply-To: Discussion of the Fedora Legacy Project
To: Discussion of the Fedora Legacy P
taharka wrote:
Howdy,
On Wed, 2006-04-12 at 13:36 -0500, Mike McCarty wrote:
Jeff Sheltren wrote:
On Apr 10, 2006, at 12:29 AM, Mike McCarty wrote:
If things get to the point where I feel I *must* replace my load,
I'm switching to Debian.
Mike
Mike, I thought you had already stopped u
Howdy,
On Wed, 2006-04-12 at 13:36 -0500, Mike McCarty wrote:
> Jeff Sheltren wrote:
> >
> > On Apr 10, 2006, at 12:29 AM, Mike McCarty wrote:
> >
> >> If things get to the point where I feel I *must* replace my load,
> >> I'm switching to Debian.
> >>
> >> Mike
> >
> >
> > Mike, I thought you
Max Pyziur wrote:
I have an FC2 system which rkhunter reports some suspicious
files. In particular, during the MD5 hash scan, it reports
/bin/dmesg
/bin/kill
/bin/login
/bin/mount
/usr/bin/kill
I run FC2 and have a similar issue. I've run rkhunter --up
> Hi,
>
> I have an FC2 system which rkhunter reports some suspicious
> files. In particular, during the MD5 hash scan, it reports
>
> /bin/dmesg
> /bin/kill
> /bin/login
> /bin/mount
> /usr/bin/kill
I run FC2 and have a similar issue. I've run rkhunter --update many
Jeff Sheltren wrote:
On Apr 10, 2006, at 12:29 AM, Mike McCarty wrote:
If things get to the point where I feel I *must* replace my load,
I'm switching to Debian.
Mike
Mike, I thought you had already stopped using Legacy. If so, I'm not
sure how this affects you.
I'm referring to your
On Wed, 12 Apr 2006, Nils Breunese (Lemonbit Internet) wrote:
But Red Hat maintained packages will probably be updated, while the legacy
packages may not. The question is whether legacy should do update the FL
maintained package or say: "This has nothing to do with security so we won't
fix it".
Hi,
I have an FC2 system which rkhunter reports some suspicious
files. In particular, during the MD5 hash scan, it reports
/bin/dmesg
/bin/kill
/bin/login
/bin/mount
/usr/bin/kill
as having unknown/incorrect hashes, and comments that this can
be caused by
Kevin Kofler wrote:
This isn't quite a legacy-specific issue. The FC5 whois reacts the
same way.
Passing -h whois.eu on the command line works around this, just
like your
config file edit.
But Red Hat maintained packages will probably be updated, while the
legacy packages may not. The qu
12 matches
Mail list logo
