From: Ivan Gyurdiev <ivg2@cornell.edu>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: selinux@tycho.nsa.gov
Subject: Re: [ SEMANAGE ] Fix record handlers, add status codes
Date: Wed, 21 Sep 2005 11:19:34 -0400 [thread overview]
Message-ID: <43317A06.7080208@cornell.edu> (raw)
In-Reply-To: <1127313768.2550.29.camel@moss-spartans.epoch.ncsc.mil>
>Thanks, merged.
>
>What do you view as still undecided for the debug system?
>
>
I need to determine what's necessary for me to introduce error reporting
in future semanage code. In particular:
- I need to pass down the semanage handle (which does not exist yet)
down for state. That's pending Joshua's patch.
- I need to decide whether to use write_error, or DEBUG, and put the
appropriate debug system in debug.h
- If (write_error) -> needs to be modified to support multiple error
messages
- If (DEBUG) -> needs to be modified to support state, and provide a
buffering callback
- Independently, I still might need to reduce the number and placement
of error messages to make the error message more suitable for the end user.
Basically, error messages a constant PITA, that I'd rather ignore for
the moment, partly because of the lack of handle object. There's more
important things to take care of... such as the justification for adding
a database-like engine in the first place. I think this will be easier
to justify once I add an avrule record, to allow policy rules to be
parsed and loaded into policy (only avtab rules, no booleans, and no
m4). This will also need some code moved (at least duplicated for now...
) from checkpolicy into sepol. The idea of this engine thing is to allow
handling of any text file that looks like a collection of records in a
consistent manner, with 90% of all code being shared (everything minus
the parsing of a single record). It should be trivial to add new
structured files, and write arbitrary handlers in C, otherwise the
objective is not accomplished.
--
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:[~2005-09-21 15:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-20 8:59 [ SEMANAGE ] Stub record handlers Ivan Gyurdiev
2005-09-20 9:22 ` [ SEMANAGE ] Fix record handlers, add status codes Ivan Gyurdiev
2005-09-21 14:42 ` Stephen Smalley
2005-09-21 15:19 ` Ivan Gyurdiev [this message]
2005-09-21 15:36 ` Stephen Smalley
2005-09-21 14:41 ` [ SEMANAGE ] Stub record handlers Stephen Smalley
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=43317A06.7080208@cornell.edu \
--to=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.