From: Joshua Brindle <jbrindle@tresys.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: SELinux List <SELinux@tycho.nsa.gov>
Subject: Re: [PATCH] libsemanage/semanage - permission check for semanage
Date: Fri, 27 Jan 2006 10:17:03 -0500 [thread overview]
Message-ID: <43DA396F.307@tresys.com> (raw)
In-Reply-To: <1138374734.13075.317.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
> On Thu, 2006-01-26 at 15:40 -0500, Joshua Brindle wrote:
>
>>This patch adds semanage_set_create_store which is callable by the
>>client to create the store. Set to 1 by semodule when called with -b.
>>Otherwise the same access checks as before are done.
>>
>>Also adds semanage_is_connected to avoid an assertion failure in
>>semodule if an error occurs before connecting.
>
>
> Merged as of libsemanage 1.5.17 and policycoreutils 1.29.13, with the
> following modifications:
> - swigify/pywrap rebuild to pick up additional interfaces,
> - dropped binary policy directory writability check,
ah, sorry, I meant to remove that
> - replaced obsolete semanage_store_writable prototype with
> semanage_store_access_check prototype.
>
> Also added a distclean target to the libsemanage top Makefile, and made
> the relabel target apply restorecon to the .so file like the other
> library Makefiles.
>
Thanks
--
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:[~2006-01-27 15:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 21:45 [PATCH] libsemanage/semanage - permission check for semanage Joshua Brindle
2006-01-19 22:45 ` Ivan Gyurdiev
2006-01-20 1:38 ` Joshua Brindle
2006-01-20 2:11 ` Ivan Gyurdiev
2006-01-20 2:19 ` Joshua Brindle
2006-01-20 13:54 ` Stephen Smalley
2006-01-20 14:00 ` Joshua Brindle
2006-01-20 14:24 ` Stephen Smalley
2006-01-20 14:09 ` Stephen Smalley
2006-01-20 14:04 ` Joshua Brindle
2006-01-20 15:20 ` Stephen Smalley
2006-01-20 19:14 ` Joshua Brindle
2006-01-20 20:49 ` Stephen Smalley
2006-01-20 21:25 ` Joshua Brindle
2006-01-23 14:36 ` Stephen Smalley
2006-01-23 14:51 ` Joshua Brindle
2006-01-23 15:29 ` Stephen Smalley
2006-01-23 15:40 ` Joshua Brindle
2006-01-23 15:59 ` Stephen Smalley
2006-01-23 16:05 ` Joshua Brindle
2006-01-23 16:18 ` Stephen Smalley
2006-01-26 20:40 ` Joshua Brindle
2006-01-27 15:12 ` Stephen Smalley
2006-01-27 15:17 ` Joshua Brindle [this message]
2006-01-23 16:33 ` Joshua Brindle
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=43DA396F.307@tresys.com \
--to=jbrindle@tresys.com \
--cc=SELinux@tycho.nsa.gov \
--cc=sds@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.