All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: Xavier Toth <txtoth@gmail.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
	SE Linux <selinux@tycho.nsa.gov>,
	Eamon Walsh <ewalsh@tycho.nsa.gov>
Subject: Re: copy&paste security_compute_av from python
Date: Thu, 10 Apr 2008 12:52:08 -0400	[thread overview]
Message-ID: <47FE45B8.20909@redhat.com> (raw)
In-Reply-To: <cadfc0e40804091304p6812fca9i132c36bb4c49e9b1@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Xavier Toth wrote:
> On Wed, Apr 9, 2008 at 1:28 PM, Stephen Smalley <sds@tycho.nsa.gov> wrote:
>>  On Wed, 2008-04-09 at 14:13 -0400, Eamon Walsh wrote:
>>  > Xavier Toth wrote:
>>  > > Also what about the mlsconstrain(s):
>>  > >
>>  > > #
>>  > > # MLS policy for the x_application_data class
>>  > > #
>>  > > mlsconstrain x_application_data { paste_after_confirm }
>>  > >     (( l1 eq l2 ) or
>>  > >      (( t1 == mlsxwinwritetoclr ) and ( h1 dom l2 ) and ( l1 domby l2 )) or
>>  > >      ( t1 == mlsxwinwrite ));
>>  > >
>>  > >
>>  > > ??
>>  > >
>>  >
>>  > I dunno.  Configure to suit your environment.  This is for write-downs,
>>  > correct?  If so then you probably don't want any constraints, since
>>  > regular "paste" should succeed in the write-up case (in which case no
>>  > confirmation is required), and the point of this permission is to allow
>>  > write downs.
>>  >
>>  > >
>>  > > On Tue, Apr 8, 2008 at 1:50 PM, Xavier Toth <txtoth@gmail.com> wrote:
>>  > >
>>  > >> I'd prefer copy instead cut.
>>  > >>
>>  >
>>  > This is fine.
>>  >
>>  > My work on the XCB Python binding is coming along OK.  I see that you
>>  > are working on Python bindings for the userspace AVC.  That's fine, but
>>  > you could probably get away with not using the AVC in the selection
>>  > manager.  You could simply look up the permission and class values in
>>  > /selinux, then use security_compute_create for permission checking.
>>  > Since the selection manager is driven by user clicking, performance
>>  > shouldn't be that big of a deal.
>>
>>  security_compute_av().
>>  But then he loses out on the libselinux infrastructure for things like
>>  permissive mode, mapping the class/perm values internally for him, etc.
>>  I think using the AVC interface is best whenever possible.
>>
>>
> 
> This is what I'd prefer also and I was hoping Dan would add the avc
> header so that the avc interface bindings would get built into
> _selinux.so.
> 
>>  --
>>  Stephen Smalley
>>  National Security Agency
>>
>>
Most of the avc.h will not work without a lot of work.  Which interfaces
do you need?  If the interfaces take a struct, we probably would need to
write a lot of binding code.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkf+RbgACgkQrlYvE4MpobOwlgCggooBGCaUN1IHv54VdDhrYSxe
HokAoMGbjUvRsoFdGVOgVcUkBw0r+6NW
=ssmU
-----END PGP SIGNATURE-----

--
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-04-10 16:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cadfc0e40803311235h3e3440fbn395dd55b8ab0e534@mail.gmail.com>
2008-04-01  0:42 ` copy&paste security_compute_av from python Eamon Walsh
2008-04-01 11:43   ` Stephen Smalley
2008-04-01 18:18     ` Eamon Walsh
     [not found]       ` <47F28FEB.9000901@tycho.nsa.gov>
     [not found]         ` <cadfc0e40804081150k336ff301i1a382b117a4d44e2@mail.gmail.com>
     [not found]           ` <cadfc0e40804081222g6fe8fed0xda16c1923a0ee6fe@mail.gmail.com>
     [not found]             ` <47FD0731.2030202@tycho.nsa.gov>
     [not found]               ` <1207765707.21223.523.camel@moss-spartans.epoch.ncsc.mil>
2008-04-09 20:04                 ` Xavier Toth
2008-04-10 16:52                   ` Daniel J Walsh [this message]
2008-04-10 16:58                     ` Xavier Toth

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=47FE45B8.20909@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=ewalsh@tycho.nsa.gov \
    --cc=sds@tycho.nsa.gov \
    --cc=selinux@tycho.nsa.gov \
    --cc=txtoth@gmail.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.