, 2005-03-16
It's a sad day when an ancient fork bomb attack can still take down most of the latest Linux distributions.
Expand all |
Post comment
silly article
2005-03-17
Anonymous (4 replies)
Anonymous (4 replies)
silly article
2005-03-18
Anonymous (1 replies)
Anonymous (1 replies)
Linux Kernel Security, Again
2005-03-17
Karyl Stein (1 replies)
Karyl Stein (1 replies)
Linux Kernel Security, Again
2005-03-17
Anonymous (3 replies)
Anonymous (3 replies)
Linux Kernel Security, Again
2005-03-17
Jason V. Miller (Author) (3 replies)
Jason V. Miller (Author) (3 replies)
Linux Kernel Security, Again
2005-03-17
mrsad (1 replies)
mrsad (1 replies)
Linux Kernel Security, Again
2005-03-17
Jason V. Miller (Author) (1 replies)
Jason V. Miller (Author) (1 replies)
Linux Kernel Security, Again
2005-03-18
Anonymous (2 replies)
Anonymous (2 replies)
simple fork bomb?
2005-03-17
Anonymous (1 replies)
Anonymous (1 replies)
simple fork bomb?
2005-03-17
Jason V. Miller (Author) (3 replies)
Jason V. Miller (Author) (3 replies)
Intended use dictates the limits
2005-03-17
Erik Keller (1 replies)
Erik Keller (1 replies)
Intended use dictates the limits
2005-03-17
Jason V. Miller (Author) (4 replies)
Jason V. Miller (Author) (4 replies)
Linux Kernel Security, Again
2005-03-17
Anonymous (2 replies)
Anonymous (2 replies)
Linux Kernel Security, Again
2005-03-18
Anonymous (1 replies)
Anonymous (1 replies)
Linux Kernel Security, Again
2005-03-18
Gentoo User (1 replies)
Gentoo User (1 replies)
Linux Kernel Security, Again
2005-03-18
Another Gentoo User (2 replies)
Another Gentoo User (2 replies)
Debian IS vulnerable!
2005-03-18
Anonymous (2 replies)
Anonymous (2 replies)
Linux only? perhaps across the board problem? Conflict of interest?
2005-03-18
glotfeltys@gmail.com (1 replies)
glotfeltys@gmail.com (1 replies)
Jason's opinion is too biased
2005-03-18
Anonymous (2 replies)
Anonymous (2 replies)
Take the first step author.
2005-03-18
EG (2 replies)
EG (2 replies)

Similarly, limits that seemed reasonable on my P2 might have people complainig about arbitrary limits on the P4. Although it's a bit of a no-win situation for a distribution maker, I still agree that they have to come up with SOME sort of limit -- but that also requires clearly documenting how to change those limits when the prove to be unreasonably low (or high).
Something else that I'd point out is that preventing a local DOS is a lot harder than preventing a remote DOS -- especially if you want to avoid arbitrary limits on legitimate work. If we block forkbombing today, I'm sure we're going to see somebody 5 years down the road screaming about 'only' being allowed 2000 processes on the default build.
[ reply ]
Link to this comment: http://www.securityfocus.com/comments/columns/308/31052#31052