lkml.org 
[lkml]   [2007]   [Jun]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    SubjectRe: Patch related with Fork Bombing Atack
    Date
    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.

    DRH

    (I hate having to explain the obvious)
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2007-06-01 09:27    [W:2.204 / U:0.688 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site