From: | Thomas Poty <thomas(dot)poty(at)gmail(dot)com> |
---|---|
To: | Charlin Barak <charlinbarak(at)gmail(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org >> PG-General Mailing List" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Using the public schema |
Date: | 2018-04-23 19:16:06 |
Message-ID: | CAN_ctni6gs57eCMNV1imwa3qSgADYedJK58LgVSRNEan2+AtyQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi charlin,
I invite you to read this doc it explains very well the security issue
with the public schéma :
https://wiki.postgresql.org/wiki/A_Guide_to_CVE-2018-1058:_Protect_Your_Search_Path
The main problem with the public schéma is the default privileges (execute)
granted to all users able to connect.
Personally, each time i create a database, i remove the public schema
Regards
Thomas
Le lun. 23 avr. 2018 à 17:00, Charlin Barak <charlinbarak(at)gmail(dot)com> a
écrit :
> Hi,
> We will be developing three new applications in PostgreSQL, each having
> its own database instance running on different hosts. We will only have one
> schema per Postgres instance. The data is read-write only by one
> application/schema in the DB instance and the data is published to other
> applications via API calls.
>
> In such a standalone database configuration, are there any security
> implications or any downsides to creating the application in the public
> schema?
>
> Thanks.
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Farber | 2018-04-23 19:47:26 | Re: Adding AVG to a JOIN |
Previous Message | Andrew Edenburn | 2018-04-23 18:09:43 | Postgres PAF setup |