From: Christopher Pardy <cpardy@redhat.com>
To: selinux@tycho.nsa.gov
Subject: adding human understandable, and translatable description support to selinux
Date: Mon, 20 Jul 2009 10:34:29 -0400 [thread overview]
Message-ID: <4A648075.3090402@redhat.com> (raw)
I'm currently working on improving the gui tools for managing selinux(the ones that ship with fedora). One of the things that has already come up is a need for more plain English descriptions of various policy components. Currently this capability exists in the policy.xml for booleans however this file is not rebuilt at policy compile time so changes and even the installation of modules is not reflected in this. I'd like to propose that a documentation section be added to each policy directory, "/etc/selinux/<policyname>/docs/". This would contain locale specific documentation files that would store information in key-value pairs. ie: {users.guest_u:"A guest user who can only (etc)"}. An interface to this store would be built for libselinux and support for setting and getting documentation would be added to some of the command line tools or given it's own tool. Additionally a method would need to be created for policy authors to define descriptions in there policy (similar to
the policy.xml method)
Before I get started on this I wanted to see what the general opinion on both the need and the best implementation would be. So what do you guys think?
Christopher Pardy <cpardy@redhat.com>
--
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 reply other threads:[~2009-07-20 14:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 14:34 Christopher Pardy [this message]
2009-07-20 17:04 ` adding human understandable, and translatable description support to selinux Remmolt G. Zwartsenberg
2009-07-20 17:27 ` Christopher J. PeBenito
[not found] ` <4A64ADA3.6020105@redhat.com>
[not found] ` <1248114027.23783.725.camel@gorn>
2009-07-20 18:26 ` Christopher Pardy
2009-07-20 19:30 ` Daniel J Walsh
2009-07-21 17:55 ` 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=4A648075.3090402@redhat.com \
--to=cpardy@redhat.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.