, 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
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)
simple fork bomb?
2005-03-17
Anonymous (1 replies)
Anonymous (1 replies)
simple fork bomb?
2005-03-17
Jason V. Miller (Author) (1 replies)
Jason V. Miller (Author) (1 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)

You either have to train users to tweak the limits for their environment, or to set them in the first place. I agree that you want to set certain parameters out of the box, but I think it's more complex than just picking a number out of thin air and applying it as a limit. Besides process limits are not as much of a concern to those running servers that only administrators log in to, or, likewise, desktop users. You don't want to antagonize the bulk of your customers by creating restrictions that may cause them problems.
[ reply ]
Link to this comment: http://www.securityfocus.com/comments/columns/308/30966#30966