On Thu, May 29, 2025 at 02:15:22PM -0400, Tom Lane wrote:
> Feike Steenbergen <feikesteenbergen@gmail.com> writes:
> > pg_restore may have issues though, as it will run these functions
> > for GENERATED STORED columns?
>
> pg_restore is already fairly exposed, as it will run tables' CHECK
> constraints, index expressions, etc. I don't think GENERATED STORED
> makes that picture much worse.
>
> As Robert said upthread, it would be nice to make all this more
> secure. But it'd presumably involve user-visible semantics changes
> along with the performance worries I mentioned. It's a dauntingly
> large task...
I spent some time thinking about the above email. First, this is on the
public hackers list, so it explains known security deficiencies. Do we
document these somewhere? I don't see them in the pg_dump or pg_restore
manual pages.
Second, I agree adding a SELECT security deficiency is certainly worse,
but how are we expecting people to restore databases securely with these
known deficiencies?
Effectively, what good is our security system if it is just delaying
someone from getting superuser privileges in case of a dump/restore?
(Yeah, that's me, Mr. Sunshine. ;-) )
--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EDB https://enterprisedb.com
Do not let urgent matters crowd out time for investment in the future.
