| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp> |
| Cc: | Yeb Havinga <yebhavinga(at)gmail(dot)com>, PgHacker <pgsql-hackers(at)postgresql(dot)org>, Joshua Brindle <jbrindle(at)tresys(dot)com> |
| Subject: | Re: [v9.2] Add GUC sepgsql.client_label |
| Date: | 2012-03-12 15:01:02 |
| Message-ID: | CA+TgmoYNFhOKCW55KHj1q9UujGXbeVdVXkVBr4R6UGs96Jd7kw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Mar 12, 2012 at 10:58 AM, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp> wrote:
> It is a practical reason. In case when httpd open the connection to PG and
> set a suitable security label according to the given credential prior to launch
> of user application, then keep this connection for upcoming request, it is
> worthwhile to reset security label of the client.
But wait a minute - how is that any good? That allows the client to
pretty trivially circumvent the security restriction that we were
trying to impose by doing sepgsql_setcon() in the first place. It
doesn't matter how convenient it is if it's flagrantly insecure.
Am I missing something here?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2012-03-12 15:11:38 | Re: psql COPY vs. ON_ERROR_ROLLBACK, multi-command strings |
| Previous Message | Robert Haas | 2012-03-12 14:59:39 | Re: [v9.2] Add GUC sepgsql.client_label |