From: Andreas Hartmann <andihartmann@freenet.de>
To: "Christian Bornträger" <linux-kernel@borntraeger.net>
Cc: Rik van Riel <riel@conectiva.com.br>,
Roy Sigurd Karlsbakk <roy@karlsbakk.net>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Kernel-Mailingliste <linux-kernel@vger.kernel.org>
Subject: Re: [2.4.18] Security: Process-Killer if machine get's out of memory
Date: Sun, 24 Mar 2002 19:37:20 +0100 [thread overview]
Message-ID: <3C9E1CE0.3000609@freenet.de> (raw)
In-Reply-To: <Pine.LNX.4.44L.0203241444560.18660-100000@imladris.surriel.com> <200203241757.SAA20700@piggy.rz.tu-ilmenau.de>
Christian Bornträger wrote:
> Rik van Riel wrote:
>
>>On Sun, 24 Mar 2002, Roy Sigurd Karlsbakk wrote:
>>
>>>Would it hard to do some memory allocation statistics, so if some
>>>process at one point (as rsync did) goes crazy eating all memory, that
>>>would be detected?
>>
>>No. What I doubt however is whether it would be worth it,
>>since most machines never run OOM.
>
>
> Well, I think could be worth in terms of security, because a local user could
> use a bad memory-eating program to produce an Denial of Service of other
> processes.
That's what I fear.
Take the actual example. You've running a server on which people can
connect with rsync. Somebody breaks off rsync - and the rsync-process on
the server is getting crazy - that's the situation, I described at the
beginning.
Now, the httpd-process on the server is killed, the named, ... .
It's a perfect DOS-attack.
Regards,
Andreas Hartmann
next prev parent reply other threads:[~2002-03-24 18:36 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-24 12:09 [2.4.18] Security: Process-Killer if machine get's out of memory andreas
[not found] ` <3C9DC6D0.3080606@wanadoo.fr>
2002-03-24 13:24 ` Andreas Hartmann
[not found] ` <3C9DD653.8090701@wanadoo.fr>
2002-03-24 13:36 ` Andreas Hartmann
2002-03-24 13:30 ` Rik van Riel
2002-03-24 14:08 ` Andreas Hartmann
2002-03-24 16:54 ` Alan Cox
2002-03-24 16:59 ` Andreas Hartmann
[not found] ` <3C9E48B8.9080707@ngforever.de>
2002-03-24 22:23 ` Andreas Hartmann
2002-03-24 15:58 ` Chris Swiedler
2002-03-24 16:57 ` Alan Cox
2002-03-24 16:59 ` Roy Sigurd Karlsbakk
2002-03-24 17:45 ` Rik van Riel
2002-03-24 17:57 ` Christian Bornträger
2002-03-24 18:01 ` Rik van Riel
2002-03-24 18:03 ` Bernd Petrovitsch
2002-03-24 18:23 ` Alan Cox
2002-03-24 18:37 ` Andreas Hartmann [this message]
2002-03-24 18:20 ` Alan Cox
2002-03-24 19:20 ` Itai Nahshon
2002-03-24 17:24 ` Andreas Hartmann
2002-03-24 18:22 ` Alan Cox
2002-03-24 18:23 ` Mr. James W. Laferriere
2002-03-24 19:49 ` Alan Cox
2002-03-24 19:48 ` Mr. James W. Laferriere
2002-03-24 20:39 ` Alan Cox
2002-03-24 18:32 ` Andreas Hartmann
2002-03-24 19:50 ` Alan Cox
2002-03-24 20:43 ` Paul P Komkoff Jr
2002-03-25 15:09 ` Rok Papež
2002-03-26 20:24 ` dean gaudet
2002-03-26 23:47 ` Alan Cox
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=3C9E1CE0.3000609@freenet.de \
--to=andihartmann@freenet.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@borntraeger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=roy@karlsbakk.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.