From: Ivan Gyurdiev <ivg2@cornell.edu>
To: SELinux List <SELinux@tycho.nsa.gov>, Daniel J Walsh <dwalsh@redhat.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
Joshua Brindle <jbrindle@tresys.com>
Subject: Re: Genhomedircon - C or Python?
Date: Sat, 18 Feb 2006 10:23:16 -0500 [thread overview]
Message-ID: <43F73BE4.7090206@cornell.edu> (raw)
In-Reply-To: <43F56179.3080008@cornell.edu>
Hmm...the reason I don't have HOME_ROOT working yet is more fundamental
- the algorithm currently operates only on seuser-keyed expansion
contexts (group of variables that are expanded together, not in
Cartesian product).
If there's interest in this functionality, try #2 of this patch could
generalize this to things not keyed on seusers... like HOME_ROOT. Then
we could add new expansion types that are not seuser related.
========
The function expand_symbol should take arguments:
- a symbol to expand (this will be the regexp, or the context (if there
is one))
- a context (some data structure of unknown type, possibly polymorphic,
containing the expansion data)
- a function ( (context, name) -> expanded_name)
- a list of names to look for:
Seuser context: USER, SELINUX_USER, ROLE, HOME_DIR
Home root context: HOME_ROOT
Fstab context (example): MOUNT_PT, FS_TYPE...etc
Should return:
- the expanded symbol
=========
Really, there's a lot of things that could be improved about
genhomedircon. I think the whole process of defining new expansions
could be made configurable, as opposed to hardcoding functionality to
USER, ROLE, HOME_DIR...
--
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-02-18 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 5:39 Genhomedircon - C or Python? Ivan Gyurdiev
2006-02-18 15:23 ` Ivan Gyurdiev [this message]
2006-02-18 15:27 ` Ivan Gyurdiev
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=43F73BE4.7090206@cornell.edu \
--to=ivg2@cornell.edu \
--cc=SELinux@tycho.nsa.gov \
--cc=dwalsh@redhat.com \
--cc=jbrindle@tresys.com \
--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.