From: antoine <antoine@nagafix.co.uk>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [Fwd: Re: [uml-devel] 2.6.12-rc6-mm1 patches testing]
Date: Thu, 09 Jun 2005 23:24:46 +0100 [thread overview]
Message-ID: <1118355886.10190.158.camel@localhost> (raw)
-------- Forwarded Message --------
> From: Stephen Smalley <sds@tycho.nsa.gov>
> To: antoine <antoine@nagafix.co.uk>
> Cc: SELinux <selinux@tycho.nsa.gov>, Blaisorblade
> <blaisorblade@yahoo.it>
> Subject: Re: [uml-devel] 2.6.12-rc6-mm1 patches testing
> Date: Thu, 09 Jun 2005 15:45:49 -0400
> On Thu, 2005-06-09 at 19:04 +0100, antoine wrote:
> > > UML needs simply to mmap (PROT_EXEC) datas from the /tmp/vm_XXXXXX file to
> > > work, and so it tries doing this very early, to give the user a hint on what
> > > happens. On a fs mounted noexec this is forbidden, so possibly it's forbidden
> > > also by SELinux; however, it would be nicer if SELinux could simply allow
> > > mmap()ing with PROT_EXEC without allowing file execution...; allowing mmap()
> > > does not put a big hole inside protections while allowing file execution
> > > does...means that if the user can supply a program to execute, that program
> > > can be written to mmap() and execute code from /tmp, but at that point the
> > > intruder could simply execute his code.
> >
> > Can anyone answer this for us please?
> > I am trying to workaround this:
> > audit(1117846877.640:0): avc: denied { execute } for pid=29031 comm=um-kernel path=/tmp/vm_file-NnIm5X (deleted) dev=md7 ino=3965039 scontext=root:sysadm_r:um_kernel_t tcontext=root:object_r:um_tmp_t tclass=file
> > Without giving uml execute access to its tmp directory.
>
> Possibly the UML folks could elaborate on what UML is trying to do here?
> In the long term, I'd advise changing its behavior if possible, as
> allowing execution of arbitrary code is obviously undesirable and use
> of /tmp will break noexec /tmp mounts as noted above regardless of what
> SELinux does.
>
> In the short term, you naturally have the option of adding:
> allow um_kernel_t um_tmp_t:file execute;
> to your policy as a workaround. This shouldn't actually allow direct
> execve() of such files, as that would also trigger another check
> (execute_no_trans if staying in the same domain or entrypoint
> otherwise), but would allow indirect execution via ld.so (if staying in
> the same domain).
-------------------------------------------------------
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 reply other threads:[~2005-06-09 22:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-09 22:24 antoine [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-10 15:15 [Fwd: Re: [uml-devel] 2.6.12-rc6-mm1 patches testing] antoine
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=1118355886.10190.158.camel@localhost \
--to=antoine@nagafix.co.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.