mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Anand Jahagirdar" <anandjigar@gmail.com>
To: "Jiri Kosina" <jikos@jikos.cz>
Cc: "Jens Axboe" <jens.axboe@oracle.com>,
	security@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Patch related with Fork Bombing Atack
Date: Fri, 1 Jun 2007 19:59:49 +0530	[thread overview]
Message-ID: <25ae38200706010729t10d68b99v10dcd9b5a190f4f0@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706011032490.29896@twin.jikos.cz>

Hello All

                I totally agree with all of you, but my idea behind
this patch is that administrator/root user must be able to know that
there is fork bombing attack on his machine and he should be able take
action agianst that particular user and kill all his processes.

can anybody please tell me how can we achive this??

Regards
Anand

On 6/1/07, Jiri Kosina <jikos@jikos.cz> wrote:
> On Fri, 1 Jun 2007, Anand Jahagirdar wrote:
>
> >     when they try to flood the syslog using fork bombing attack, their
> > messge will be printed only once in syslog and it will show how many
> > times it has repeated. due to this he will not able to flood the
> > syslog.and i am using only one single variable in my printk messge so it
> > is quite not possible to flood the syslog.
>
> Your argument is flawed - if the kernel provides more than one possibility
> to flood the syslogd, the is free to invoke the events interleaved. This
> trivially prevents syslogd from grouping identical reports together.
>
> --
> Jiri Kosina
>

      reply	other threads:[~2007-06-01 14:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-31 13:45 Anand Jahagirdar
2007-05-31 13:46 ` Jens Axboe
2007-06-01  6:48   ` Anand Jahagirdar
2007-06-01  7:25     ` Daniel Hazelton
2007-06-01  7:30       ` Jens Axboe
2007-06-01  8:00         ` Daniel Hazelton
2007-06-01  8:02           ` Jens Axboe
2007-06-03 23:01         ` Nix
2007-06-04  1:29           ` Daniel Hazelton
2007-06-04 14:49             ` Anand Jahagirdar
2007-06-04 14:58               ` Jiri Kosina
2007-06-04 15:28                 ` Daniel Hazelton
2007-06-05 14:20                   ` Anand Jahagirdar
2007-06-01  8:38     ` Jiri Kosina
2007-06-01 14:29       ` Anand Jahagirdar [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=25ae38200706010729t10d68b99v10dcd9b5a190f4f0@mail.gmail.com \
    --to=anandjigar@gmail.com \
    --cc=jens.axboe@oracle.com \
    --cc=jikos@jikos.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=security@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®