public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: fede2@fuerzag.ulatina.ac.cr (Alvaro Figueroa Cabezas)
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] chroot USE flag?
Date: Fri, 18 Jul 2003 08:08:26 +0600	[thread overview]
Message-ID: <20030718020826.GB3876@fuerzag.ulatina.ac.cr> (raw)
In-Reply-To: <200307180743.20823.tdickenson@devmail.geminidataloggers.co.uk>

Without having read a lot of systrace... I'm gonna risk and answer.

On Jul 18 07:43, Toby Dickenson wrote:

> I have recently adopted systrace as a "better chroot". I find it is easier to 
> set up a new service under systrace than both chroot and selinux. Unlike 
> chroot, it is easy to disable systrace briefly if you suspect the security 
> hardening may be causing a problem.

I found systrace and chroot as tools for diferent porpuses, not that one
can replace the other. By creating a chroot you are preemtively cutting
down the amount of damage a user can do if it passes down the security
of the application. I still need to break out of the chroot.

People has the idea that chroots are imposible to break out of. I know
that some of the guys in my LUG have succesfully (kinda like) gotten of
of it by inserting into the broken application, enough code to create a
device (as in mknod) and to mount that device inside the chroot.

By using capabilities (go out and fetch a 2.6 kernel!), the whole
concept of an all migthy root is obsoleted. You create a user with has
certain capabilities to do things, and that is all.

But hey, lets keep the discussion out of the thread on the dev mailing
list. I hope that this small enlightenment/clarification won't upset
anyone.

-- 
Alvaro Figueroa


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-07-18 14:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-18  5:15 [gentoo-dev] chroot USE flag? Brandon Hale
2003-07-17 12:52 ` Alvaro Figueroa Cabezas
2003-07-18  6:44   ` Brandon Hale
2003-07-18  6:54   ` Brandon Hale
2003-07-18  3:08     ` Ned Ludd
2003-07-18  6:43     ` Toby Dickenson
2003-07-18  2:08       ` Alvaro Figueroa Cabezas [this message]
2003-07-18  0:49 ` Matt Rickard
2003-07-18  1:25   ` Christian Axelsson

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=20030718020826.GB3876@fuerzag.ulatina.ac.cr \
    --to=fede2@fuerzag.ulatina.ac.cr \
    --cc=gentoo-dev@gentoo.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