From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Rob Landley <rob@landley.net>
Subject: Re: [uml-devel] The source to that firmware-uml thing is now up...
Date: Sun, 1 May 2005 13:06:38 +0200 [thread overview]
Message-ID: <200505011306.39277.blaisorblade@yahoo.it> (raw)
In-Reply-To: <200504281938.45043.rob@landley.net>
On Friday 29 April 2005 01:38, Rob Landley wrote:
> On Friday 29 April 2005 03:16 pm, Blaisorblade wrote:
> > > Hmmm... I suppose I could always have a wrapper script
> >
> > which can't be setuid if in bash, could if in Perl and perlsuid is
> > installed.
>
> Actually you can run bash setuid with the -p option. From bash's
> "flags.c":
>
> /* Non-zero means that this shell is running in `privileged' mode. This
> is required if the shell is to run setuid. If the `-p' option is
> not supplied at startup, and the real and effective uids or gids
> differ, disable_priv_mode is called to relinquish setuid status. */
> int privileged_mode = 0;
>
> (That said, if you do use -p to get get a setuid bash, there's several
> other things you should do to make this marginally less dangerous. And I
> wouldn't trust myself to remember them all off the top of my head...)
No, I'm not saying that a setuid bash won't work because of the bash special
code.
I'm saying that setuid script plain don't work (the kernel ignores the setuid
bit). Except for perl, which has a special mechanism to make them work
anyway.
> That said, I wasn't thinking of using bash for the wrapper but either
> python or C. It's just easier to secure them...
Ok, for C no problem. No idea if python supports a similar trick.
> Okay, the disgusting way to do this:
>
> Mount a ramfs somewhere. CD into it, make subdirectories and bind mount in
> enough of the parent environment to run UML and open the memory file. Run
> UML. Have UML create a new file in the ramfs to signal when it's up enough
> that the host filesystem can go away. The parent program detects the
> file's creation, unmounts all the directories, deletes the empty
> directories, remounts the ramfs read-only, and then does a lazy unmount of
> the ramfs.
>
> I can come up with a _more_ disgusting way to do this if necessary. :)
No, I don't even think _this_ way is disgusting. It's nice IMHO.
--
Paolo Giarrusso, aka Blaisorblade
Skype user "PaoloGiarrusso"
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit 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-05-01 10:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-20 10:06 [uml-devel] The source to that firmware-uml thing is now up Rob Landley
2005-04-23 12:57 ` Blaisorblade
2005-04-27 1:23 ` Rob Landley
2005-04-29 19:16 ` Blaisorblade
2005-04-28 23:38 ` Rob Landley
2005-05-01 11:06 ` Blaisorblade [this message]
2005-05-02 5:14 ` Rob Landley
2005-05-02 19:38 ` Blaisorblade
2005-04-24 23:20 ` Henrik Nordstrom
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=200505011306.39277.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=rob@landley.net \
--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