| To: | linux-xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: XFS tree for Red Hat should be moved to at least kernel-2.4.20-20 |
| From: | Ethan Benson <erbenson@xxxxxxxxxx> |
| Date: | Tue, 16 Sep 2003 10:41:57 -0800 |
| In-reply-to: | <46483.213.173.165.140.1063724939.squirrel@xxxxxxxxxxxxxxxxxxxxxxx> |
| Mail-copies-to: | nobody |
| Mail-followup-to: | linux-xfs@xxxxxxxxxxx |
| References: | <Pine.LNX.4.44.0309140958220.17784-100000@xxxxxxxxxxxxxxxxxxxxxx> <Pine.LNX.4.44.0309141045391.15430-100000@xxxxxxxxxxxxxxxxxxxxxxxxx> <20030914214745.GD827@xxxxxxxxxxxxxxx> <46483.213.173.165.140.1063724939.squirrel@xxxxxxxxxxxxxxxxxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.3.28i |
On Tue, Sep 16, 2003 at 05:08:59PM +0200, Simon Matter wrote: > No please. There are better solutions than mkfs in most situations. Why > being so afraid about kernel modules and rootkit binaries? Boot from a CD > like knoppix or similar. Then mount all filesystems and examine the > system. First check whether your rpm database has been touched. A recent > backup may help here. Then rpm is your friend by finding out which files no its not, an attacker can modify the rpmdb. -- Ethan Benson http://www.alaska.net/~erbenson/
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS 1.3.0 RPMS for Red Hat 7.3 (was XFS 1.3.0pre4 ...), Axel Thimm |
|---|---|
| Next by Date: | TAKE 899755 - tweak inode flags, Nathan Scott |
| Previous by Thread: | Re: XFS tree for Red Hat should be moved to at least kernel-2.4.20-20, Ethan Benson |
| Next by Thread: | XFS 1.3.0 for latest RH errata and rawhide (was: XFS tree for Red Hat should be moved to at least kernel-2.4.20-20), Axel Thimm |
| Indexes: | [Date] [Thread] [Top] [All Lists] |