From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Karl Chen <quarl@cs.berkeley.edu>
Subject: Re: [uml-devel] hostfs permissions
Date: Fri, 10 Jun 2005 18:03:20 +0200 [thread overview]
Message-ID: <200506101803.21108.blaisorblade@yahoo.it> (raw)
In-Reply-To: <quack.20050609T2234.87is0msrl6@meow.quarl.org>
On Friday 10 June 2005 07:34, Karl Chen wrote:
> Hi, I'm doing some large-scale security experiments on Debian
> security. I'm using UML to do the whole thing on a cluster.
> Hostfs seems to make everything owned by root -- even files
> created by non-root users.
So you are running uml as root?
Or you are running UML as non-root but with hostfs as root filesystem? In this
case you're possibly seeing the result of a trick made to make it work
well... but I don't know if that trick is present in the UML version you're
using.
> I'm currently using 2.4.26-3 (Debian
> package).
Hmm, in that case
> I found a few posts via Google mentioning a patch to
> fix this, but no other information. What is the modified behavior
> of hostfs permissions? Has this been integrated into a newer
> version, or is it in cvs, or if not, are there plans to?
Well, there are:
1) HUMFS, implementing the ideal behaviour below
2) a patch posted by somebody for when UML is run by root, to allow created
files to get the UID of the process creating it inside UML.
> [I think the ideal behavior, if UML is running as non-root, would
> be if there were a temporary mapping of ownership (e.g. so chown
> works) -- but that would be a lot of work to implement.]
Well, this work has been started but is currently stalled because of other
ongoing work, however I hope we'll resurrect that shortly.
> I would be happy if there were uid and gid mount options as many
> other fs types have -- to treat all files in the entire mount as
> owned by a particular user/group.
Well, I'm going to add those options to UML 2.6 but I'll be able to work on
this only next week... However this should not be too much work.
--
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade
___________________________________
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB
http://mail.yahoo.it
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-06-10 16:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-10 5:34 [uml-devel] hostfs permissions Karl Chen
2005-06-10 16:03 ` Blaisorblade [this message]
2005-06-10 20:14 ` Karl Chen
2005-06-10 22:26 ` Blaisorblade
2005-06-11 0:48 ` Karl Chen
2005-06-11 2:33 ` Blaisorblade
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=200506101803.21108.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=quarl@cs.berkeley.edu \
--cc=user-mode-linux-devel@lists.sourceforge.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