On Mon, 2009-03-09 at 20:05 -0400, Tom Lane wrote:
> "Joshua D. Drake" <jd@commandprompt.com> writes:
> > Is there any possibility of having it be enabled at compile time?
>
> That's been assumed right along (unless you think it's okay for Postgres
> to stop working on every non-SELinux platform).
Good point.
> The problem here is
> mostly about whether we have enough confidence in the code to put our
> project name on it.
This patch has been bandied about for what, two years? There is a known
fork of our project that runs with it. It has a live googlecode site:
http://code.google.com/p/sepgsql/
Which has lots of documentation.
I also appears to be active within the SE community:
http://www.nsa.gov/applications/search/index.cfm?q=se-postgresql
It is also part of the Secure OS project out of Japan (as far as I can
tell).
I know we are a little uncomfortable here but KaiGai-San (forgive me if
I type that wrong) has proven to be a contributor in his own right,
jumping over every hurdle we have presented him. He is obviously
sticking around for a while.
If we accept this code, we lose a fork of our project (good) and we pull
those people into our project (better) and hopefully they will help us
mature the project over time (best).
Sincerely,
Joshua D. Drake
>
> regards, tom lane
>
--
PostgreSQL - XMPP: jdrake@jabber.postgresql.org Consulting, Development, Support, Training 503-667-4564 -
http://www.commandprompt.com/ The PostgreSQL Company, serving since 1997
