From: Colin Walters <walters@verbum.org>
To: linux-kernel@vger.kernel.org
Cc: luto@amacapital.net
Subject: linux-user-chroot 2012.2
Date: Fri, 10 Aug 2012 16:58:02 -0400 [thread overview]
Message-ID: <1344632282.9131.5.camel@lenny> (raw)
Hi,
This is the release of linux-user-chroot 2012.2. The major change now
is that it makes use of Andy's new PR_SET_NO_NEW_PRIVS. This doesn't
close any security hole I'm aware of - our previous use of the MS_NOSUID
bind mount over / should work - but, belt and suspenders as they say.
The code:
http://git.gnome.org/browse/linux-user-chroot/commit/?id=515c714471d0b5923f6633ef44a2270b23656ee9
As for how linux-user-chroot and PR_SET_NO_NEW_PRIVS relate, see this
thread:
http://thread.gmane.org/gmane.linux.kernel.lsm/15339
Summary
-------
This tool allows regular (non-root) users to call chroot(2), create
Linux bind mounts, and use some Linux container features. It's
primarily intended for use by build systems.
Project information
-------------------
There's no web page yet; send patches to
Colin Walters <walters@verbum.org>
next reply other threads:[~2012-08-10 20:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 20:58 Colin Walters [this message]
2012-08-13 18:10 ` Andy Lutomirski
2012-09-09 21:24 ` Jan Engelhardt
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=1344632282.9131.5.camel@lenny \
--to=walters@verbum.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome