Cool, now that we got that out, I have another questions for ya. If you've already been attacked by that damned ssh crc 32 crap, and all the memory got used up and your box was locked up and you hit the on/off switch to reboot, and it fscked when it started again and then you reboot and then logon and root can not ls, rm, mv, chown, chgrp, rpm etc (shows fatal local crc 32 in the logs) then what? Is it a root kit on that sucker or are there some corupted inode files , and how would one remove or check for that rootkit and how would one fix the bad inodes? The box is running but it seems root has no control. On Wednesday 21 November 2001 06:56 am, you wrote:
Is it nit picking time already? Didn't know that, OMG! ;)
While we're at it, if you're running SSH protocol version 2 (in any implementation) *and* a vulnerable SSH protocol 1 demon, with a fallback to V1 for compatibilty with the lame old ssh1, you're vulnerable too, congratulations.
Boris Lorenz
---