From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: Karl MacMillan <kmacmillan@tresys.com>
Cc: Daniel J Walsh <dwalsh@redhat.com>, SELinux <selinux@tycho.nsa.gov>
Subject: Re: refpolicy is missing on lots of hits with audit2allow -R.
Date: Tue, 20 Apr 2010 14:09:37 -0400 [thread overview]
Message-ID: <1271786977.32279.29.camel@gorn> (raw)
In-Reply-To: <l2s10143821004200737t683832efu28214c95b3e156c@mail.gmail.com>
On Tue, 2010-04-20 at 10:37 -0400, Karl MacMillan wrote:
> On Mon, Apr 19, 2010 at 11:53 AM, Karl MacMillan
> <karlwmacmillan@gmail.com> wrote:
> > On Mon, Apr 19, 2010 at 10:33 AM, Daniel J Walsh <dwalsh@redhat.com> wrote:
> >>
> >> If you look at the interface userdom_read_home_certs.
> >>
> >> [InterfaceVector userdom_read_home_certs $1:source ]
> >> $1,home_cert_t,file,read,lock,getattr,open,ioctl
> >> $1,home_cert_t,dir,ioctl,search,read,lock,open,getattr
> >> $1,home_cert_t,lnk_file,read,getattr
> >> $1,home_root_t,dir,getattr,open,search
> >> $1,home_root_t,lnk_file,read,getattr
> >> $1,user_home_dir_t,dir,getattr,open,search
> >> $1,user_home_dir_t,lnk_file,read,getattr
> >>
> >> A domain that is allowed to search the homedir is always going to
> >> generate an AVC that is a long way off.
> >>
> >
> > Seems to me that the problem is that the read / getattr on
> > user_home_dir_t directories and files is adding too much distance.
> >
>
> I looked at this a bit more - there are a few interesting issues:
>
> 1. The open permissions have not been added to the perm_map file
> (patch attached to fix that). When there is no perm map then we weight
> the permission at 5 and assume read and write. Since we heavily
> penalize providing a write interface for a read access request, this
> causes the return of a large distance (as I believe that it should).
> I'd like to find a long term home for the perm map file that increases
> it's likelihood of being updated with new permissions (Chris - what do
> you think of including this with reference policy?).
I'm fine with it, just as long as the output perm map file has a
agreed-upon standard format. It looks like sepolgen has the same format
as setools, so that probably won't be a problem (unless there are other
tools with perm maps that I am unaware of).
--
Chris PeBenito
Tresys Technology, LLC
(410) 290-1411 x150
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2010-04-20 18:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 14:33 refpolicy is missing on lots of hits with audit2allow -R Daniel J Walsh
2010-04-19 15:53 ` Karl MacMillan
2010-04-20 14:37 ` Karl MacMillan
2010-04-20 18:09 ` Christopher J. PeBenito [this message]
2010-04-21 14:04 ` Daniel J Walsh
2010-04-22 1:53 ` Karl MacMillan
2010-04-22 13:04 ` Daniel J Walsh
2010-04-22 14:25 ` Karl MacMillan
2010-04-22 13:38 ` Daniel J Walsh
2010-04-22 14:29 ` Karl MacMillan
2010-04-22 19:16 ` Karl MacMillan
2010-04-23 15:09 ` Daniel J Walsh
2010-04-28 14:25 ` Karl MacMillan
2010-04-28 15:34 ` Daniel J Walsh
2010-04-28 15:34 ` Daniel J Walsh
2010-04-28 17:53 ` Karl MacMillan
2010-04-28 18:12 ` Joshua Brindle
2010-04-28 18:36 ` Daniel J Walsh
2010-04-28 18:47 ` Joshua Brindle
2010-04-28 19:01 ` Daniel J Walsh
2010-04-28 18:42 ` Karl MacMillan
2010-05-13 19:37 ` Stephen Smalley
2010-04-20 14:46 ` Daniel J Walsh
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=1271786977.32279.29.camel@gorn \
--to=cpebenito@tresys.com \
--cc=dwalsh@redhat.com \
--cc=kmacmillan@tresys.com \
--cc=selinux@tycho.nsa.gov \
/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.