All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Brindle <jbrindle@tresys.com>
To: Ivan Gyurdiev <ivg2@cornell.edu>
Cc: Daniel J Walsh <dwalsh@redhat.com>,
	Stephen Smalley <sds@tycho.nsa.gov>,
	SELinux-dev@tresys.com, selinux@tycho.nsa.gov
Subject: Re: [ SEMANAGE ] Stub pserver backend
Date: Tue, 15 Nov 2005 10:59:01 -0500	[thread overview]
Message-ID: <437A05C5.4080505@tresys.com> (raw)
In-Reply-To: <437A0749.5060407@cornell.edu>

Ivan Gyurdiev wrote:
> 
>> Giving me the tools in libsemanage to build the manipulation of ports, 
> 
> Okay, will work on that..
> 
>> seusers 
> 
> The seuser APIs are already available, and should work in libsemanage.
> Although MLS validation is not happening, the modification should work, 
> and should verify that the SElinux user exists.
> Not sure if python bindings are currently available.

the swig wrappers don't currently have any write (transaction) 
functionality, nor are the seuser keys and create functions wrapped, 
these will need to be done.
> 
>> and potentially
>> user modules (local.pp) from python.
> 
> Same for user APIs. Those things do not go into modules currently - 
> they're written back out into flat files. Why do we want those into a 
> module? I think Stephen also mentioned a while ago that modules cannot 
> yet support all of the objects that we are managing. Is this still the 
> case?
> 

We don't want users in modules, it isn't even supported with MLS. The 
flat file implementations are already working, we just need to wrap the 
interfaces to write the python utilities.


--
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:[~2005-11-15 15:59 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-14 21:55 [ SEMANAGE ] Stub pserver backend Ivan Gyurdiev
2005-11-15 11:29 ` Stephen Smalley
2005-11-15 11:58   ` Stephen Smalley
2005-11-15 13:38     ` Daniel J Walsh
2005-11-15 14:12       ` Stephen Smalley
2005-11-15 14:25         ` Policy mods in last nights refpolicy Daniel J Walsh
2005-11-15 15:52           ` Christopher J. PeBenito
2005-11-16  0:55             ` Daniel J Walsh
2005-11-16 14:38               ` Christopher J. PeBenito
2005-11-16 13:48             ` Stephen Smalley
2005-11-16 14:18               ` Stephen Smalley
2005-11-16 14:46                 ` Joshua Brindle
2005-11-15 14:38         ` [ SEMANAGE ] Stub pserver backend Daniel J Walsh
2005-11-15 16:02           ` Chad Sellers
2005-11-15 16:05       ` Ivan Gyurdiev
2005-11-15 15:59         ` Joshua Brindle [this message]
2005-11-15 16:25           ` Ivan Gyurdiev
2005-11-15 16:15             ` Joshua Brindle
2005-11-15 16:42               ` Ivan Gyurdiev
2005-11-15 16:05         ` Stephen Smalley
2005-11-15 13:47     ` Stephen Smalley
2005-11-15 15:54     ` Ivan Gyurdiev
2005-11-15 15:55       ` Joshua Brindle
2005-11-15 16:30         ` Ivan Gyurdiev
2005-11-16  1:01         ` Daniel J Walsh
2005-11-16  0:58       ` 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=437A05C5.4080505@tresys.com \
    --to=jbrindle@tresys.com \
    --cc=SELinux-dev@tresys.com \
    --cc=dwalsh@redhat.com \
    --cc=ivg2@cornell.edu \
    --cc=sds@tycho.nsa.gov \
    --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.