public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: jesse <jesse@wirex.com>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.2.18pre21
Date: Sat, 18 Nov 2000 11:07:56 +0100 (MET)	[thread overview]
Message-ID: <200011181007.LAA12901@cave.bitwizard.nl> (raw)
In-Reply-To: <E13wWlX-0008Oh-00@the-village.bc.nu> from Alan Cox at "Nov 16, 2000 09:40:18 pm"

Alan Cox wrote:
> > It's simply not good enough to close all directory file descriptors before chrooting.
> > 
> > If calling chroot once you're already in a chroot jail was disallowed, it would stop
> > this attack.
 
> I think the problem here is that some people have the idea that
> chroot is some kind of magical security device. Thats not true at
> all. You can build an environment like that if you wish by closing
> other directory handles and having no suitably priviledged code in
> the chroot area and stuff.

I read about the BSD Jail stuff a while ago. 

It's a nice "operating system class lab project". Estimated time
needed: 40 hours.

This IS the magical security device. 

				Roger. 
-- 
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
*       Common sense is the collection of                                *
******  prejudices acquired by age eighteen.   -- Albert Einstein ********
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-18 10:38 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-10  3:07 Linux 2.2.18pre21 Alan Cox
2000-11-10  3:44 ` David S. Miller
2000-11-10 11:35   ` Benjamin Herrenschmidt
2000-11-10 15:42     ` Tom Rini
2000-11-10 15:34       ` David S. Miller
2000-11-10 10:59 ` Arnaud S . Launay
2000-11-10 10:52   ` David S. Miller
2000-11-16 14:07 ` Matthias Andree
2000-11-16 16:16   ` Andrea Arcangeli
2000-11-16 19:52     ` jesse
2000-11-16 20:02       ` chroot [Was: Re: Linux 2.2.18pre21] Kurt Roeckx
2000-11-16 21:40       ` Linux 2.2.18pre21 Alan Cox
2000-11-18 10:07         ` Rogier Wolff [this message]
2000-11-18 17:32           ` kuznet
2000-11-18 17:34             ` Rogier Wolff
2000-11-18 17:47               ` kuznet
2000-11-18 17:51                 ` Rogier Wolff
2000-11-16 22:56       ` Matthias Andree
2000-11-17  6:30       ` Peter Samuelson
2000-11-17  6:40         ` H. Peter Anvin
2000-11-17 11:22           ` Peter Samuelson
2000-11-17 17:35             ` H. Peter Anvin
2000-11-17 11:34           ` Matthias Andree
2000-11-17 19:23         ` jesse
2000-11-18 20:44           ` Pavel Machek
2000-11-18  1:38         ` Nix
2000-11-21  4:19           ` Peter Samuelson
  -- strict thread matches above, loose matches on Subject: below --
2000-11-10  9:28 willy tarreau
2000-11-10  9:44 ` Matti Aarnio
2000-11-10  9:57   ` Constantine Gavrilov
2000-11-10 10:14     ` Matti Aarnio
2000-11-10 10:22       ` Constantine Gavrilov
2000-11-10 10:51         ` Matti Aarnio
2000-11-10 19:11           ` Thomas Davis
2000-11-10 10:18 ` Constantine Gavrilov
2000-11-10 10:40 willy tarreau
2000-11-10 10:49 willy tarreau
2000-11-10 11:21 willy tarreau
2000-11-13  7:00 willy tarreau
2000-11-13  9:47 willy tarreau

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=200011181007.LAA12901@cave.bitwizard.nl \
    --to=r.e.wolff@bitwizard.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jesse@wirex.com \
    --cc=linux-kernel@vger.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