From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Michael Richardson <mcr@sandelman.ottawa.on.ca>
Subject: Re: [uml-devel] T-mode processes
Date: Mon, 4 Oct 2004 20:57:18 +0200 [thread overview]
Message-ID: <200410042057.19226.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <29485.1096825447@marajade.sandelman.ottawa.on.ca>
On Sunday 03 October 2004 19:44, Michael Richardson wrote:
> >>>>> "BlaisorBlade" == BlaisorBlade <blaisorblade_spam@yahoo.it> writes:
> >> We also continue to have an issue with the /proc/PID/environ file
> >> not being owned by the process involved.
>
> BlaisorBlade> I'm looking at the permission in your listing and in
> BlaisorBlade> my linux, and I don't see anything strange. Plus, I
> BlaisorBlade> don't understand what you mean with "a file owned by a
> BlaisorBlade> certain process".
>
> BlaisorBlade> Do you mean "I start the process with uid build and
> BlaisorBlade> /proc/PID/* has uid root while it should have uid
> BlaisorBlade> build"?
>
> Yes.
>
> BlaisorBlade> If you mean this, the answer is that you seem to be
> BlaisorBlade> starting UML with one id and making it run with
> BlaisorBlade> another UID. At least, I see this permission situation
> BlaisorBlade> with the X Font Server:
> No, this is not the case.
> It runs as "build" and that is all.
> The problem is that the use of mm confuses the proc-permission system
> into thinking that the process is setuid. I wandered through this last
> year, when we first noticed this problem.
> This seems to be due to how mm->dumpable is initalized.
> (see task_dumpable in fs/proc/base.c)
> I tried to change it, but I was not successful. I can dig up my
> attempts, but they are on the list.
Oh, ok... this can be fixed, I guess, with these infos... I'll come back to
this when I have time.
Actually, what I should do is to set the "mm->dumpable" flag to 1 inside
mm/proc_mm.c (after mm_alloc(), it is 0). The situation is clear. However, to
write a good patch, I want to study well the "mm->dumpable" flag use (when
it's set, when not...) otherwise I could open a security hole (even because
there are people using UML setuid to root, for the mlock() patch).
Bye
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
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:[~2004-10-04 19:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-03 0:26 [uml-devel] T-mode processes Michael Richardson
2004-10-03 10:41 ` Henrik Nordstrom
2004-10-03 17:26 ` Michael Richardson
2004-10-03 17:55 ` Henrik Nordstrom
2004-10-03 18:39 ` Michael Richardson
2004-10-04 18:22 ` BlaisorBlade
2004-10-04 22:40 ` Michael Richardson
2004-10-03 15:04 ` BlaisorBlade
2004-10-03 17:44 ` Michael Richardson
2004-10-04 18:57 ` BlaisorBlade [this message]
2004-10-04 20:25 ` Henrik Nordstrom
2004-10-05 18:51 ` BlaisorBlade
2004-10-06 0:00 ` Henrik Nordstrom
2004-10-06 19:45 ` BlaisorBlade
2004-10-14 16:46 ` 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=200410042057.19226.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--cc=mcr@sandelman.ottawa.on.ca \
--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