Re: Proposal: Role Sandboxing for Secure Impersonation - Mailing list pgsql-hackers

From Jelte Fennema-Nio
Subject Re: Proposal: Role Sandboxing for Secure Impersonation
Date
Msg-id CAGECzQTCLyv064H_BSqRyQb_GFf3mbAZgu=RZhLkPP413-A02w@mail.gmail.com
Whole thread Raw
In response to Re: Proposal: Role Sandboxing for Secure Impersonation  (Wolfgang Walther <walther@technowledgy.de>)
List pgsql-hackers
On Thu, 5 Dec 2024 at 09:47, Wolfgang Walther <walther@technowledgy.de> wrote:
> Right, I should have clarified: My proposal wasn't mean to be taken
> literally as an SQL command. Passwords should not be sent as plain text,
> no question. This needs to happen on the protocol level.

Thanks for clarifying.

> I don't want to give any privileges to the connection pooler /
> application and I don't want to outsource authentication.

I understand the security consideration and I think it's valid. But
I'd like to call out for completeness that such an approach (when
using scram) would require two roundtrips, instead of just one like
for option e). So for an admin this is a tradeoff (security vs perf),
not simply better.



pgsql-hackers by date:

Previous
From: vignesh C
Date:
Subject: Re: SQL:2011 application time
Next
From: Amit Kapila
Date:
Subject: Re: Disallow UPDATE/DELETE on table with unpublished generated column as REPLICA IDENTITY