Re: Patch proposal: New hooks in the connection path - Mailing list pgsql-hackers

From Brindle, Joshua
Subject Re: Patch proposal: New hooks in the connection path
Date
Msg-id 10b14623-7a17-a9ad-c57f-6f84ac578f0d@amazon.com
Whole thread Raw
In response to Re: Patch proposal: New hooks in the connection path  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
List pgsql-hackers
On 6/30/22 5:23 AM, Bharath Rupireddy wrote:
> <snip>
> On the security aspect, we must ensure we don't leak any sensitive
> information such as password or SSH key to the new hook - if PGPORT
> has this information, maybe we need to mask that structure a bit
> before handing it off to the hook.

Can you elaborate more on why you see this as necessary? Extensions run 
in-process and have no real memory access limits, "masking", which 
really means copying data to another struct, is just extra work and 
overhead with no actual security gain, IMO.






pgsql-hackers by date:

Previous
From: Antonin Houska
Date:
Subject: Re: Temporary file access API
Next
From: Aleksander Alekseev
Date:
Subject: Re: POC: Lock updated tuples in tuple_update() and tuple_delete()