Skip site navigation (1) Skip section navigation (2)

Re: [0/4] Proposal of SE-PostgreSQL patches

From: Kohei KaiGai <kaigai(at)ak(dot)jp(dot)nec(dot)com>
To: pgsql-patches(at)postgresql(dot)org
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [0/4] Proposal of SE-PostgreSQL patches
Date: 2008-03-17 05:24:17
Message-ID: 47DE0081.1010001@ak.jp.nec.com (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
It seems to me some of SE-PostgreSQL patches are not delivered yet,
although [3/4] and [4/4] were already done.

Does anti-spam system caught my previous three messages?
If necessary, I will send them again.

Thanks,

Kohei KaiGai wrote:
> The series of patches are the proposal of Security-Enhanced PostgreSQL
> (SE-PostgreSQL) for the upstreamed PostgreSQL 8.4 development cycle.
> 
>  [1/4] sepostgresql-pgace-8.4devel-3.patch
>          provides PGACE (PostgreSQL Access Control Extension) framework
>  [2/4] sepostgresql-sepgsql-8.4devel-3.patch
>          provides SE-PostgreSQL feature, based on PGACE framework.
>  [3/4] sepostgresql-pg_dump-8.4devel-3.patch
>          enables pg_dump to dump database with security attribute.
>  [4/4] sepostgresql-policy-8.4devel-3.patch
>          provides the default security policy for SE-PostgreSQL.
 - snip -

-- 
OSS Platform Development Division, NEC
KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>

In response to

Responses

pgsql-hackers by date

Next:From: Zdenek KotalaDate: 2008-03-17 06:53:27
Subject: Re: [0/4] Proposal of SE-PostgreSQL patches
Previous:From: Tom LaneDate: 2008-03-17 04:45:39
Subject: Re: Single table forcing sequential scans on query plans

pgsql-patches by date

Next:From: Zdenek KotalaDate: 2008-03-17 06:53:27
Subject: Re: [0/4] Proposal of SE-PostgreSQL patches
Previous:From: Kohei KaiGaiDate: 2008-03-17 04:31:06
Subject: [4/4] Proposal of SE-PostgreSQL patches

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group