From: Joshua Brindle <method@manicmethod.com>
To: Joe Nall <joe@nall.com>
Cc: Paul Moore <paul.moore@hp.com>,
Daniel J Walsh <dwalsh@redhat.com>,
Chad Hanson <chanson@TrustedCS.com>,
SE Linux <selinux@tycho.nsa.gov>,
Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: releasibility in mcstransd
Date: Tue, 08 Jul 2008 13:22:50 -0400 [thread overview]
Message-ID: <4873A26A.1040400@manicmethod.com> (raw)
In-Reply-To: <90C62997-D6C9-4E64-A89F-A5569943DE67@nall.com>
Joe Nall wrote:
>
> On Jun 27, 2008, at 1:56 PM, Joshua Brindle wrote:
>
>> Paul Moore wrote:
>>> On Friday 27 June 2008 9:42:48 am Joshua Brindle wrote:
>>>> I think for the time being we should not be importing the updated
>>>> mcstrans into fedora. There are still some unanswered questions about
>>>> the implementation. We are talking about some of these offline.
>>>
>>> Any particular reason why the discussion isn't online? Granted I'm not
>>> sure I would have much useful to contribute but I do like hearing about
>>> what is going on and the discussion behind the decisions ...
>>>
>>
>> Oops, I misspoke. The unanswered questions were on list, how to deal
>> with the use of private libsepol types, duplicated functions and
>> missing ebitmap functionality in the library.
>
> Any progress or thoughts on this?
>
Not over here. I do have someone trying to use the updated server so I'll hopefully hear any comments or concerns back from them.
On the technical issues above, I don't think Steve wanted the functionality pushed into the library but without either doing that or encapsulating all these types the server will always have to be statically linked against libsepol, which I'd like to avoid.
I'll change my mind if it comes down to this server needs more information about the level than we can reasonably give via encapsulation.
--
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:[~2008-07-08 17:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-09 20:25 releasibility in mcstransd Joshua Brindle
2008-06-09 20:50 ` Paul Moore
2008-06-09 21:04 ` Chad Hanson
2008-06-11 3:04 ` Joe Nall
2008-06-11 14:11 ` Daniel J Walsh
2008-06-20 15:37 ` Joshua Brindle
2008-06-20 18:14 ` Joe Nall
2008-06-20 18:26 ` Joshua Brindle
2008-06-20 18:34 ` Joe Nall
2008-06-27 11:51 ` Daniel J Walsh
2008-06-27 13:42 ` Joshua Brindle
2008-06-27 18:41 ` Paul Moore
2008-06-27 18:56 ` Joshua Brindle
2008-07-08 15:54 ` Joe Nall
2008-07-08 17:11 ` Stephen Smalley
2008-07-08 17:22 ` Joshua Brindle [this message]
2008-06-20 18:41 ` Joe Nall
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=4873A26A.1040400@manicmethod.com \
--to=method@manicmethod.com \
--cc=chanson@TrustedCS.com \
--cc=dwalsh@redhat.com \
--cc=joe@nall.com \
--cc=paul.moore@hp.com \
--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.