All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eamon Walsh <ewalsh@tycho.nsa.gov>
To: "Christopher J. PeBenito" <cpebenito@tresys.com>
Cc: SELinux List <selinux@tycho.nsa.gov>
Subject: Re: selection labeling
Date: Tue, 18 Mar 2008 15:45:54 -0400	[thread overview]
Message-ID: <47E01BF2.80200@tycho.nsa.gov> (raw)
In-Reply-To: <1205849784.16113.11.camel@gorn>

Christopher J. PeBenito wrote:
> I ran into an interesting denial:
>
> avc:  denied  { setattr setattr } for request=X11:SetSelectionOwner
> comm=dbus-launch
> selection=_DBUS_SESSION_BUS_SELECTION_root_3c39a16f05862d57c3d6ef0047356754
> scontext=root:staff_r:staff_t
> tcontext=system_u:object_r:xselection_t
> tclass=x_selection
>
> Other than the double setattr in the permissions, trying to label this
> selection for anything but the default doesn't seem possible.  It seems
> that this should be type_transitioned, but it didn't seem to work.
>   

Whoops, I know why the double setattr is there.  I'll get that fixed, 
ignore that for now.

We probably need to have wildcarding in the X label support, like the 
way filenames work.  Do you agree?

But I don't have a clue why D-BUS is creating selections with those 
insane names.  It looks like abuse of the selection mechanism to me.  
Selections are used for IPC, hence they're supposed to have fixed, 
standard names.  Actually it doesn't make sense to me that D-BUS is 
using selections at all.

-- 
Eamon Walsh <ewalsh@tycho.nsa.gov>
National Security Agency


--
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.

       reply	other threads:[~2008-03-18 19:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1205849784.16113.11.camel@gorn>
2008-03-18 19:45 ` Eamon Walsh [this message]
2008-03-18 20:18   ` selection labeling James Carter
2008-03-19 12:27   ` Christopher J. PeBenito
2008-03-20  3:11     ` Eamon 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=47E01BF2.80200@tycho.nsa.gov \
    --to=ewalsh@tycho.nsa.gov \
    --cc=cpebenito@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.