Hi,
Personally, I have no time for idle speculation as to the abilities
of the admin.
Given the workload this computer was under, it is reasonable to expect the
admin has some skills.
I note, on a political correctness point, we do not know the
sex of the admin - so label the person as "the admin", not "guy".
The real point of "Linux woes" is quite different to what has been
discussed so far.
The point is:
a)Why did the box get hacked
b)What software has to be fixed
c)What can we do to prevent similar things to my box at home
Further,
throwaway comments on "just read www.slashdot.org" to find the answer
are pointless.
I am not about to go away and spend days trying to decipher some weird
instructions with a faulty install script.
I want to reduce the chance of this happening to my linux box.
I want to use my linux box to write code, which benefits opensource.
I am not interested in spending days doing sysadmin work.
What packages are there that reliably work to stop this hacking - reliably ?????
Derek.
===========================================================
On Thu, 14 Aug 2003, Carl Cerecke wrote:
> [EMAIL PROTECTED] wrote:
> > So the guys was either running unknown binaries as root, compiling
> > unknown source as root or running some daemon as root, so what? Every
> > newbie knows that doing so is simply asking for trouble, even though
> > most do it. A production server shouldn't anyway be running unknown
> > software.
>
> Do you have any idea how know-it-all this sounds?
> I know the guy, and he's not some pimply faced geek teenager who knows
> just enough to be dangerous. He knows his stuff.
>
> Cheers,
> Carl.
>
>
>
>
--
Derek Smithies Ph.D.
IndraNet Technologies Ltd.
Email: [EMAIL PROTECTED]
ph +64 3 365 6485
Web: http://www.indranet-technologies.com/
