Josh Berkus wrote:
KaiGai Kohei wrote:
On the WiKi of CommitFest:Sep,
http://wiki.postgresql.org/wiki/CommitFest:2008-09
The entry of SE-PostgreSQL points a message when I submitted older
version
of our patch set. But the latest ones are listed on another message.
Please add a link to the
KaiGai Kohei wrote:
On the WiKi of CommitFest:Sep,
http://wiki.postgresql.org/wiki/CommitFest:2008-09
The entry of SE-PostgreSQL points a message when I submitted older version
of our patch set. But the latest ones are listed on another message.
Please add a link to the following message for
On the WiKi of CommitFest:Sep,
http://wiki.postgresql.org/wiki/CommitFest:2008-09
The entry of SE-PostgreSQL points a message when I submitted older version
of our patch set. But the latest ones are listed on another message.
Please add a link to the following message for our convenience:
ht
Hello,
The following patches are updated ones of SE-PostgreSQL toward the HEAD of CVS.
[1/4]
http://sepgsql.googlecode.com/files/sepostgresql-sepgsql-8.4devel-3-r958.patch
[2/4]
http://sepgsql.googlecode.com/files/sepostgresql-pg_dump-8.4devel-3-r958.patch
[3/4]
http://sepgsql.googlecode.com/
At 2008-07-11 19:10:16 +0900, [EMAIL PROTECTED] wrote:
>
> And I have a question. Is it legal to use a pointer value as a
> condition, like `while (!pointer) ...' ?
Yes, it's fine.
-- ams
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
Hi,
I updated the series of patches, as follows:
[1/4] Core facilities of PGACE/SE-PostgreSQL
http://sepgsql.googlecode.com/files/sepostgresql-sepgsql-8.4devel-3-r953.patch
[2/4] "--security-context" option of pg_dump/pg_dumpall
http://sepgsql.googlecode.com/files/sepostgresql-pg_dump
All,
> > The pgace_* scheme is an attractive idea, although the server process
> > has to provide a bit more hints (like the name of security system column
> > and the kind of objects exported with security attribute) pg_dump to
> > support various kind of security features with smallest implement
KaiGai Kohei wrote:
Might want to change the option name --enable-selinux to something
like --security-context.
In general, we might want to not name things selinux_* but instead
sepostgresql_* or security_* or security_context_*. Or maybe PGACE?
The pgace_* scheme is an attractive idea, alt
Thanks for your reviewing.
Peter Eisentraut wrote:
Am Donnerstag, 26. Juni 2008 schrieb KaiGai Kohei:
The following patch set (r926) are updated one toward the latest CVS head,
and contains some fixes in security policy and documentation.
OK, I have quickly read through these patches. They l
Peter,
Are there any comments yet from the (Trusted)Solaris people that wanted to
evaluate this approach for compatibility with their approach?
In case they're not paying attention, a month ago the Trusted Solaris
folks said the general approach was fine, but that they would likely
want to e
Am Donnerstag, 26. Juni 2008 schrieb KaiGai Kohei:
> The following patch set (r926) are updated one toward the latest CVS head,
> and contains some fixes in security policy and documentation.
OK, I have quickly read through these patches. They look very nice, so I am
optimistic we can get throug
Hi,
The following patch set (r926) are updated one toward the latest CVS head,
and contains some fixes in security policy and documentation.
I want to push them for the reviewing queue of CommitFest:Jul.
[1/4] Core facilities of PGACE/SE-PostgreSQL
http://sepgsql.googlecode.com/files/sepost
Hi,
The following patch set is our second proposals of SE-PostgreSQL.
It contains many of fixes and improvements from the previous version.
Please add them a reviwing queue of the next commit fest.
Thanks,
List of Patches
===
[1/4] Core facilities of PGACE/SE-PostgreSQL
http:/
13 matches
Mail list logo
