On 10/9/05, Robert Citek <[EMAIL PROTECTED]> wrote:
>
> On Oct 9, 2005, at 7:05 PM, Jon Drews wrote:
> > So it looks like a fork bomb.
>
> Bingo!
>
> > Hopefully Robert will expalin the syntax.
>
> Here are some variants:
>
> foo(){ foo|foo&}; foo
> foo(){ foo&foo;}; foo
> foo(){ foo&}; foo
>You guys should be setting your user limits so these fork bombs don't disrupt your Linux computers. This is easy to do: From: http://www.pantz.org/os/linux/security/debhard/ch4.en.html#s-user-limits EXCERPT: 4.10.2 Limiting resource usage: the limits.conf file You should really take a serious look into this file. Here you can define user resource limits. If you use PAM, the file /etc/limits.conf is ignored and you should use /etc/security/limits.conf instead. If you do not restrict resource usage, any user with a valid shell in your system (or even an intruder who compromised the system through a service) can use up as much CPU, memory, stack, etc. as the system can provide. This resource exhaustion problem can only be fixed by the use of PAM. Note that there is a way to add resource limits to some shells (for example, bash has ulimit, see bash(1)), but since not all of them provide the same limits and since the user can change shells (see chsh(1)) it is better to place the limits on the PAM modules. For more information read: * PAM configuration article. * Seifried's Securing Linux Step by Step on the Limiting users overview section. * LASG in the Limiting and monitoring users section. _______________________________________________ CWE-LUG mailing list [email protected] http://www.cwelug.org/ http://www.cwelug.org/archives/ http://www.cwelug.org/mailinglist/
