pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jan Bilek <jan.bilek@eftlab.com.au>
To: Christophe Pettus <xof@thebuild.com>
Cc: pgsql-general@postgresql.org <pgsql-general@postgresql.org>
Subject: Re: PCI:SSF - Safe SQL Query & operators filter
Date: Tue, 8 Nov 2022 01:43:02 +0000
Message-ID: <33a762ed-a045-c1e5-a042-cd4903f7de4b@eftlab.com.au> (raw)
In-Reply-To: <23C450AB-9333-40CB-8ED1-F15D15BED878@thebuild.com>
References: <e3cb6a78-8ff2-dcf1-2fdd-26e3093d3106@eftlab.com.au>
	<23C450AB-9333-40CB-8ED1-F15D15BED878@thebuild.com>

On 11/8/22 11:29, Christophe Pettus wrote:
>
>> 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 a different, non-superuser role, including schema migrations.
Well, superuser (our App) is already logged in and as it is designed 
very much as an "appliance" it simply does that job - manages its 
database. There might be a way to explore whether we can use internally 
another (limited) user just for reporting queries on a different 
connection session. But I am getting (security related) headaches just 
thinking about it.
>
>> 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 bypass PostgreSQL's role system.  If anyone could create functions in it, anyone could bypass roles.

Yes, agreed. Any ideas?

-- 
Jan Bilek - CTO at EFTlab Pty Ltd.



view thread (10+ messages)  latest in thread

Message-ID: <33a762ed-a045-c1e5-a042-cd4903f7de4b@eftlab.com.au>
Permalink:  ../33a762ed-a045-c1e5-a042-cd4903f7de4b@eftlab.com.au/
Also on:    postgresql.org/message-id/33a762ed-a045-c1e5-a042-cd4903f7de4b@eftlab.com.au

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: jan.bilek@eftlab.com.au, xof@thebuild.com
  Subject: Re: PCI:SSF - Safe SQL Query & operators filter
  In-Reply-To: <33a762ed-a045-c1e5-a042-cd4903f7de4b@eftlab.com.au>
  References: <e3cb6a78-8ff2-dcf1-2fdd-26e3093d3106@eftlab.com.au> <23C450AB-9333-40CB-8ED1-F15D15BED878@thebuild.com> <33a762ed-a045-c1e5-a042-cd4903f7de4b@eftlab.com.au>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox