On Wed, Dec 18, 2002 at 01:13:16AM -0500, Michael H. Warfield wrote:
>       The rpm app itself doesn't have to be compromised.
> 
>       I know of several worms that installed their kits and updates
> using rpm.  ...

Yeh, that's true.  I guess I'd be a minimalist cracker--but then, most of
the cracks I've seen aren't crafted, skilled attacks--they're cast-iron
skillets over the head.

> ...need trusted utilities from a trusted source (i.e. read only media
> as in one of the bootable business cards) and an off line copy of the
> rpm database.  Even if you can trust rpm (which you can't on the system
> but you can from a BBC) you still can't trust the database on the system.

Abso-effin-lutely.

>       Cleaning out a system is both time consuming and highly educational.
> Highly recommended (in the shits and giggles sense of "recommended") if you
> have the time and inclination.

Heh.

> 90 to 120 minutes is optimistic depending on the skill of the
> attacker, if they installed a GOOD root kit (or not), and if you
> have off-line trusted databases and utilities (or not).  Time goes up
> from there...

I've got over 20 years in Unix, almost 10 in Linux, and am professionally
paranoid, so I had set the system up with a full system backup off-line
but mountable, and the first time took 90 minutes.  Yeah, it can take
longer--although nothing I saw was surprising, it's tedious ferreting out
all the little changes.  Fortunately, they don't know about hyperspace
links or black-hole mountpoints.  (Hmm...FTM, I have to check to see if
hyperspace links even work under Linux...)

Oh, and another useful ditty--a truly paranoid bi-directional set of
firewall blocking rules.  And off-machine logging.

Cheers,
-- 
        Dave Ihnat
        [EMAIL PROTECTED]



-- 
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to