From: Andries.Brouwer@cwi.nl
To: Andries.Brouwer@cwi.nl, alan@lxorguk.ukuu.org.uk
Cc: andrewm@uow.edu.au, linux-kernel@vger.kernel.org,
torvalds@transmeta.com, tytso@mit.edu
Subject: Re: [PATCH] more SAK stuff
Date: Mon, 2 Jul 2001 14:49:11 +0200 (MET DST) [thread overview]
Message-ID: <UTC200107021249.OAA495880.aeb@vlet.cwi.nl> (raw)
>> (a) It does less, namely will not kill processes with uid 0.
>> Ted, any objections?
Alan:
> That breaks the security guarantee. Suppose I use a setuid app to confuse
> you into doing something ?
You confuse me? Unlikely :-)
Indeed, discussion is possible. I think my version is more secure
and more useful, but if you disagree, delete the lines
/* do not kill root processes */
if (p->uid == 0)
continue;
Andries
next reply other threads:[~2001-07-02 12:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-02 12:49 Andries.Brouwer [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-02 13:03 [PATCH] more SAK stuff Andries.Brouwer
2001-07-02 12:16 Andries.Brouwer
2001-07-02 12:33 ` Alan Cox
2001-07-02 19:10 ` Hua Zhong
2001-07-03 22:00 ` Rob Landley
2001-07-06 1:45 ` Albert D. Cahalan
2001-07-02 18:57 ` Kain
2001-07-06 22:02 ` David Wagner
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=UTC200107021249.OAA495880.aeb@vlet.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrewm@uow.edu.au \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=tytso@mit.edu \
/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