Dear Sir
I am forwarding one patch related with fork bombing attack.
actually ulimit helps to prevent fork bombing attack.
1) when i searched for the code which actually prevents
fork bombing attack in kernel/fork.c file, it took lot of time to
search for the code.
2) when we set the ulimit in /etc/security/limits.conf file
for guest account and then try fork bombing attack using guest
account. ulimit prevents fork bombing attack but administrator/root
user wont come to know that somebody is trying fork bombing attack on
his machine.
Due to this two reasons i tried to create a patch which will solve
above mentioned problems.
1) Commented Code in my patch will Definitely Help Developer to get
the prevention code for Fork bombing Attack very easily.
2) Printk message in my patch will definitely help Administrator/Root
User to detect which particular user is trying fork bombing attack on
his machine by looking at /var/log/messages or dmesg . he can take
action against that particular user and kill his processes.
Regards,
Anand
Attachment:
fork.patch~
Description: Binary data
- Follow-Ups:
- Re: Patch related with Fork Bombing Atack
- From: Jens Axboe <[email protected]>
- Re: Patch related with Fork Bombing Atack
- Prev by Date: Re: Add INPUT support to toshiba_acpi
- Next by Date: Re: Patch related with Fork Bombing Atack
- Previous by thread: [PATCH] x86: Document the hotplug code is incompatible with x86 irq handling
- Next by thread: Re: Patch related with Fork Bombing Atack
- Index(es):
 |