From: Jens Axboe <jens.axboe@oracle.com>
To: Daniel Hazelton <dhazelton@enter.net>
Cc: Anand Jahagirdar <anandjigar@gmail.com>,
security@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Patch related with Fork Bombing Atack
Date: Fri, 1 Jun 2007 09:30:20 +0200 [thread overview]
Message-ID: <20070601073020.GL32105@kernel.dk> (raw)
In-Reply-To: <200706010325.23185.dhazelton@enter.net>
On Fri, Jun 01 2007, Daniel Hazelton wrote:
> On Friday 01 June 2007 02:48:59 Anand Jahagirdar wrote:
> > On 5/31/07, Jens Axboe <jens.axboe@oracle.com> wrote:
> > > On Thu, May 31 2007, Anand Jahagirdar wrote:
> > > > 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.
> > >
> > > You just opened a DoS possibility for any user, they can now flood the
> > > syslog instead.
> >
> > Jens Axboe
> >
> > 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.
> >
> > am i missing something??
> >
> > anand
>
> Most definately. Each printk() call outputs to syslog - which means
> that every time your code outputs its message there is another line in
> the logs. It then becomes possible to use that to flood the syslog.
I think Anand is assuming that because syslog may coalesce identical
messages into "repeated foo times" in the messages file, that it's not a
dos. That is of course wrong.
--
Jens Axboe
next prev parent reply other threads:[~2007-06-01 7:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 13:45 Patch related with Fork Bombing Atack 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 [this message]
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
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=20070601073020.GL32105@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=anandjigar@gmail.com \
--cc=dhazelton@enter.net \
--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