From: KaiGai Kohei <kaigai@ak.jp.nec.com>
To: SELinux <selinux@tycho.nsa.gov>
Subject: SE-PostgreSQL documentation
Date: Thu, 06 Nov 2008 19:51:52 +0900 [thread overview]
Message-ID: <4912CC48.80405@ak.jp.nec.com> (raw)
Nowaday, I'm working to revise the documentation of SE-PostgreSQL at:
http://wiki.postgresql.org/wiki/SEPostgreSQL
The SE-PostgreSQL feature is now under reviewing for the upstreamed
PostgreSQL v8.4.x development cycle.
A PostgreSQL folks told me a comprehensive documentation is desirable
while the series of discussion. In addition, it should be on the wiki
due to its maintenancibility.
At the past, I provided "The SE-PostgreSQL Security Guide" as a PDF
document, but some of them got legacy now, so I thought it's a good
time to revise it.
If you can comment anything, please feel free to notice them.
As I'm not a native English user, it's unclear for me the descriptions
are enough correct/simple to understand.
Thanks,
--
OSS Platform Development Division, NEC
KaiGai Kohei <kaigai@ak.jp.nec.com>
--
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.
reply other threads:[~2008-11-06 10:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4912CC48.80405@ak.jp.nec.com \
--to=kaigai@ak.jp.nec.com \
--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.