From: dtdevore64@yahoo.com (Dan)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] refpolicy interface help
Date: Mon, 14 Dec 2015 21:56:24 -0500 [thread overview]
Message-ID: <566F8158.7000407@yahoo.com> (raw)
In-Reply-To: <566ED8D9.1060803@tresys.com>
Yes I labeled everything correctly, my .emacs.d directory and everything
underneath it is labeled emacs_home_t and I have labeled my emacs binary
with the emacs_exec_t.
On 12/14/2015 09:57 AM, Christopher J. PeBenito wrote:
> On 12/13/2015 12:38 AM, Dan wrote:
>> Hello all, I am confining the application emacs using the selinux
>> refpolicy and I seem to be stuck on one little part. I get this one
>> audit2allow rule that says allow emacs_t user_home_t:file { rename write
>> create read open };
>>
>> Now my problem with that rule is that I don't want my application to
>> write or create files with the user_home_t, so I decided to use an
>> interface. The interfaces I used are these below:
>>
>> userdom_user_home_dir_filetrans(emacs_t, emacs_home_t, dir, ".emacs.d")
>>
>> userdom_user_home_content_filetrans(emacs_t, emacs_home_t, { file dir
>> lnk_file })
>>
>>
>>
>> But the problem is when I added these into my policy and when trying to
>> to an audit2allow on the most recent time and date the denial was still
>> there for some odd reason and I don't know what interface, macro, or
>> whatever to use to get rid of the denial allow emacs_t user_home_t:file
>> { rename write create read open }; Any help would be much appreciated.
>
> Did you relabel the existing files and directories? Adding a filetrans
> will only affect the label of new files/dirs being created.
>
prev parent reply other threads:[~2015-12-15 2:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-13 5:38 [refpolicy] refpolicy interface help Dan
2015-12-13 13:28 ` Lukas Vrabec
2015-12-13 22:13 ` Dan
2015-12-14 11:55 ` Lukas Vrabec
2015-12-14 14:29 ` Dan
2015-12-14 15:00 ` Lukas Vrabec
2015-12-14 15:17 ` Dominick Grift
2015-12-15 3:20 ` Dan
2015-12-19 10:24 ` Dominick Grift
2015-12-14 14:57 ` Christopher J. PeBenito
2015-12-15 2:56 ` Dan [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=566F8158.7000407@yahoo.com \
--to=dtdevore64@yahoo.com \
--cc=refpolicy@oss.tresys.com \
/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.