From: Daniel J Walsh <dwalsh@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Joshua Brindle <jbrindle@tresys.com>,
Chad Hanson <chanson@TrustedCS.com>,
russell@coker.com.au, SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: libsetrans and libselinux
Date: Tue, 03 Jan 2006 13:31:37 -0500 [thread overview]
Message-ID: <43BAC309.8000507@redhat.com> (raw)
In-Reply-To: <1136312534.27632.146.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
> On Tue, 2006-01-03 at 13:12 -0500, Daniel J Walsh wrote:
>
>> There has been some thought to making it daemon based. And allow
>> libsetrans setup a
>> unix_domain_socket to talk across. This would allow us to implement a
>> daemon and eliminate
>> the reprocessing of the file each time an application starts. Then you
>> could just replace the daemon.
>>
>
> Right, at that point, one might want to just fold it into libselinux.
>
>
I would wish to move to this new framework before we suck it in.
>>> MITRE also thought it possible that their translation library could be
>>> open sourced, if that would help. Not sure how long it would take to
>>> gain approval though...
>>>
>>>
>>>
>> I thought there might be classification problems in there also?
>>
>
> Not for the library itself IIUC. Just specific configuration files that
> might be used.
>
>
--
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.
prev parent reply other threads:[~2006-01-03 18:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-03 3:11 libsetrans and libselinux Russell Coker
2006-01-03 4:16 ` Daniel J Walsh
2006-01-03 5:55 ` Joshua Brindle
2006-01-03 17:06 ` Stephen Smalley
2006-01-03 18:12 ` Daniel J Walsh
2006-01-03 18:22 ` Stephen Smalley
2006-01-03 18:31 ` Daniel J Walsh [this message]
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=43BAC309.8000507@redhat.com \
--to=dwalsh@redhat.com \
--cc=chanson@TrustedCS.com \
--cc=jbrindle@tresys.com \
--cc=russell@coker.com.au \
--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.