public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mitchell Blank Jr <mitch@sfgoth.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] relinquish_fs() syscall
Date: Tue, 30 Nov 2004 06:12:04 -0800	[thread overview]
Message-ID: <20041130141204.GE63669@gaz.sfgoth.com> (raw)
In-Reply-To: <1101822273.2640.52.camel@laptop.fenrus.org>

Arjan van de Ven wrote:
> > Can you really do that on normal file descriptors?  Weird.  I'd have thought
> > you'd need to open /dev/hd* to do that.
> 
> inb/outb after iopl.

That was already discussed earlier in the thread.

> > Is AF_UNIX in a separate namespace?  My understanding (from reading
> > unix_find_other()) is that unless you can create a UNIX socket in your
> > filesystem you're going to have trouble creating new UNIX sockets.
> 
> iirc there are anonymous unix sockets...

Ah, I see now -- the sun_path[0]=='\0' code.  I'll have to take a look
at that; probably just need to add a check to prevent jailed processes
from using those sockets (since they're supposed to be in a "null"
namespace)  Will investigate later this week.

It looks like this is also a weakness in code that currently uses
chroot("/var/empty")  It's not the end of the world since it still
requires a cooperating unjailed process on the same host as the jailed
one to pass in a fd which is quite an obstacle in most scenarios.  Still,
it's something that should be protected against.

-Mitch

  reply	other threads:[~2004-11-30 14:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-29 11:43 [RFC] relinquish_fs() syscall Mitchell Blank Jr
2004-11-29 11:51 ` Alan Cox
2004-11-29 13:55   ` Mitchell Blank Jr
2004-11-29 15:17     ` Alan Cox
2004-11-30 13:27       ` Mitchell Blank Jr
2004-11-30 13:44         ` Arjan van de Ven
2004-11-30 14:12           ` Mitchell Blank Jr [this message]
2004-11-30 13:43             ` Alan Cox
2004-12-05  0:14               ` Rob Landley
2004-11-30 12:29     ` Helge Hafting
2004-11-30 13:48       ` Mitchell Blank Jr

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=20041130141204.GE63669@gaz.sfgoth.com \
    --to=mitch@sfgoth.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arjan@infradead.org \
    --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