Thanks Laurenz. That works.
On Tue, Apr 24, 2018 at 4:00 PM, Laurenz Albe
wrote:
> Charlin Barak wrote:
>
> > 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 inst
Charlin Barak wrote:
> 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
Erratum :
The main problem with the public schéma is the default privileges (*create*)
granted to all users able to connect.
Le lun. 23 avr. 2018 à 21:16, Thomas Poty a écrit :
> Hi charlin,
> I invite you to read this doc it explains very well the security issue
> with the public schéma :
>
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
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
applicati
