I was reading this on SecurityFocus.com and they mention that RedHat, Gentoo, and Mandrake all crashed.
I then proceeded to fork bomb every Unix machine I could get my hands on. My FreeBSD server at home shrugged it off (even after inviting other connected users to try), as did my OpenBSD gateway. This, too, is exactly what I expected to happen.
Next, I asked several my associates who use Linux to try it out on their machines, and we didn't have to go far to find more Linux distributions that succumbed to the same painfully effective fork bomb attack. Both Gentoo and Red Hat followed in the footsteps of Mandrake, and each died quicker than you can say "unreasonable default settings." I'll quickly mention here that Debian did not suffer the same fate as the others; congrats to the Debian development team.
For those who are not aware, let me briefly explain the cause of fork bombing. First, the shell must be configured to operate with what I consider to be unreasonable limits. This itself has nothing to do with the kernel. Second, the kernel must allow many more processes to be created than should be. Since shells often default to the maximum number of processes supported by the kernel, together we have a problem.
WAL*BORG - Resistance is futile. You WILL shop here.
This topic has been discussed here.
The gist of it is Arch would not survive a fork bomb and we need to look into ways to secure Arch form this type of attack.
I have nothing to say, and I am saying it.
Last I heard there was goign to be a 'system-wide-id' setup, where forks are systematically discriminated against and arrested, and only good middle class spoons run free in the kernel.
What about sporks?
If you develop an ear for sounds that are musical it is like developing an ego. You begin to refuse sounds that are not musical and that way cut yourself off from a good deal of experience.
- John Cage
What about sporks?
Probably get away with deportation.