From: Miroslav Grepl <mgrepl@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>,
w.chimiak@ieee.org,
"selinux@tycho.nsa.gov" <selinux@tycho.nsa.gov>
Subject: Re: Linux sandbox and the -i option
Date: Thu, 3 Mar 2016 13:52:01 +0100 [thread overview]
Message-ID: <56D83371.8060509@redhat.com> (raw)
In-Reply-To: <56D6F06B.2070904@tycho.nsa.gov>
On 03/02/2016 02:53 PM, Stephen Smalley wrote:
> On 03/01/2016 08:31 AM, Bill wrote:
>> Is anyone else having issues with the
>> % sandbox -i [path]
>> not working? What happens is the context is incorrectly done.
>>
>> %ls -Zd /tmp/.sandbox_home_[whatever]
>> gives
>> unconfined_u:object_r:sandbox_file_t:s0:cxx,cyyy .
>> BUT
>> %ls -Z [path] is
>> gives
>> unconfined_u:object_r:mozilla_home_t:s0 [path]
>>
>> This causes all sorts of read/write issues.
>>
>> I guess I can write a script to do the
>> chcon, but that is a bit painful and you have to hunt
>> for the correct sandbox directory (not optimal at all).
>>
>> Any suggestions?
>
> I think this is really a question for the fedora selinux list and/or a
> redhat bugzilla, but regardless, you need to provide more information
> (e.g. distro version, package version, etc).
Yes, could you please ask on selinux@lists.fedoraproject.org with
package details?
Thank you.
>
>
> _______________________________________________
> Selinux mailing list
> Selinux@tycho.nsa.gov
> To unsubscribe, send email to Selinux-leave@tycho.nsa.gov.
> To get help, send an email containing "help" to
> Selinux-request@tycho.nsa.gov.
--
Miroslav Grepl
Senior Software Engineer, SELinux Solutions
Red Hat, Inc.
prev parent reply other threads:[~2016-03-03 12:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 13:31 Linux sandbox and the -i option Bill
2016-03-02 13:53 ` Stephen Smalley
2016-03-03 12:52 ` Miroslav Grepl [this message]
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=56D83371.8060509@redhat.com \
--to=mgrepl@redhat.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=w.chimiak@ieee.org \
/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.