linux-um archives
 help / color / mirror / Atom feed
From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Hardening hostfs
Date: Sat, 18 Oct 2003 15:22:31 +0200	[thread overview]
Message-ID: <200310181522.31529.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <Pine.LNX.4.44.0310180026300.22559-100000@filer.marasystems.com>

Alle 00:35, sabato 18 ottobre 2003, Henrik Nordstrom ha scritto:
> On Thu, 16 Oct 2003, Doug Dumitru wrote:
> > 1.  If hostfs is compiled in as a module, then the hostfs=...
> > command-line arguments are not used.  Thus, trying to restrict access
> > with this does not appear to be effective.
>
> There should be a module argument in this case.. but it seems there is no
> module arguments for the hostfs options..
As noted by Steve Schmidtke, in answer to a patch I posted about a different 
problem, you cannot make this an option for the module. If inside the Uml you 
have root access, you can even omit the option when you load the module(and 
to call mount you must be root anyway). So, the only right behaviour is to 
make the module read the option supplied at boot time.

IIRC, in the approaching 2.6 mainline kernel there is something for this 
purpose(I remember an article on LWN about module infrastructure changes), 
but I only have a very vague idea.

One solution which would work even now is to move the __uml_setup code 
somewhere else, and to make it conditional to CONFIG_HOSTFS(or whatever name 
it has): the macro is defined both if it's compiled as a module and if it's 
compiled statically. Then the actual module would read the external variable.
-- 
cat <<EOSIGN
Paolo Giarrusso, aka Blaisorblade
Linux Kernel 2.4.21/2.6.0-test on an i686; Linux registered user n. 292729
EOSIGN



-------------------------------------------------------
This SF.net email sponsored by: Enterprise Linux Forum Conference & Expo
The Event For Linux Datacenter Solutions & Strategies in The Enterprise 
Linux in the Boardroom; in the Front Office; & in the Server Room 
http://www.enterpriselinuxforum.com
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2003-10-18 13:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-17  5:20 [uml-devel] Hardening hostfs Doug Dumitru
2003-10-17  5:52 ` Russell Coker
2003-10-17  6:09 ` Peter
2003-10-17  8:26   ` Geert Uytterhoeven
2003-10-16  1:48     ` Jeff Dike
2003-10-17 22:35 ` Henrik Nordstrom
2003-10-18 13:22   ` BlaisorBlade [this message]
2003-10-18 21:56     ` Henrik Nordstrom
2003-10-24 14:41 ` Michael Richardson

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=200310181522.31529.blaisorblade_spam@yahoo.it \
    --to=blaisorblade_spam@yahoo.it \
    --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