Re: PCI:SSF - Safe SQL Query & operators filter

Поиск
Список
Период
Сортировка
От Christophe Pettus
Тема Re: PCI:SSF - Safe SQL Query & operators filter
Дата
Msg-id 23C450AB-9333-40CB-8ED1-F15D15BED878@thebuild.com
обсуждение исходный текст
Ответ на PCI:SSF - Safe SQL Query & operators filter  (Jan Bilek <jan.bilek@eftlab.com.au>)
Ответы Re: PCI:SSF - Safe SQL Query & operators filter  (Jan Bilek <jan.bilek@eftlab.com.au>)
Список pgsql-general

> On Nov 7, 2022, at 17:24, Jan Bilek <jan.bilek@eftlab.com.au> wrote:
> Would there be any way to go around this?

The typical configuration is to not permit the PostgreSQL superuser to log in remotely.  The database can be managed by
adifferent, non-superuser role, including schema migrations. 

> CREATE OR REPLACE LANGUAGE plpython3u;
> HINT:  Must be superuser to create this extension.

The reason only a superuser can create this extension is the "u" at the end of the name: It is an untrusted PL that can
bypassPostgreSQL's role system.  If anyone could create functions in it, anyone could bypass roles. 


В списке pgsql-general по дате отправления:

Предыдущее
От: Jan Bilek
Дата:
Сообщение: PCI:SSF - Safe SQL Query & operators filter
Следующее
От: Jan Bilek
Дата:
Сообщение: Re: PCI:SSF - Safe SQL Query & operators filter