From: "Oliver Pitzeier" <o.pitzeier@uptime.at>
To: "'Olaf Titz'" <olaf@bigred.inka.de>,
linux-kernel@vger.kernel.org,
"'Herbert Potzl'" <herbert@13thfloor.at>
Subject: RE: chroot() breaks syslog() ?
Date: Wed, 6 Aug 2003 10:42:40 +0200 [thread overview]
Message-ID: <000701c35bf6$b370ea70$020b10ac@pitzeier.priv.at> (raw)
In-Reply-To:
> > IMHO, devfs in chroot environment, is defeating the purpose
> > because if you have access to raw devices, like the device
> > your chroot dir is on,
> > you can easily mount that device again, and voila you have
> > access to
> > the full tree, if you
>
> You need to be root to mount the device, and as root you can
> also create the device special file. A chroot environment
> does not reliably guard against root breaking out of it.
That's not completly wrong nor is it completly true. :)
You _CAN_ guard yourself from root's breaking out of some chroot environment.
Using grsec (www.grsecurity.net). Denying double-chroots, creation of special
files within chroot-environments and if you like it... Deny mounting within
chroot. :)
There are many options provided - just use 'em. :)
Best regards,
Oliver
next reply other threads:[~2003-08-06 8:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 8:42 Oliver Pitzeier [this message]
2003-08-06 11:08 ` Herbert Pötzl
-- strict thread matches above, loose matches on Subject: below --
2003-08-06 13:34 Oliver Pitzeier
2003-08-04 7:30 Steven Micallef
2003-08-04 5:49 Steven Micallef
2003-08-04 5:34 ` Ben Collins
2003-08-04 6:12 ` David Lang
2003-08-04 8:40 ` Wichert Akkerman
2003-08-04 13:33 ` Herbert Pötzl
2003-08-04 20:19 ` Olaf Titz
2003-08-04 5:27 Steven Micallef
2003-08-04 5:19 ` Ben Collins
2003-08-04 7:23 ` Torsten Foertsch
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='000701c35bf6$b370ea70$020b10ac@pitzeier.priv.at' \
--to=o.pitzeier@uptime.at \
--cc=herbert@13thfloor.at \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@bigred.inka.de \
/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
all inboxes | Powered by JetHome®