From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: let's disallow ALTER ROLE bootstrap_superuser NOSUPERUSER |
Date: | 2022-07-21 17:27:26 |
Message-ID: | 20220721172726.GA3779763@nathanxps13 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jul 21, 2022 at 01:02:50PM -0400, Tom Lane wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> ... if
>> we want to regard no-superusers as a supported configuration, we
>> probably need to tighten that up. I think it's kind of hopeless,
>
> Yeah, I agree. At least, I'm uninterested in spending any of my
> own time trying to make that usefully-more-secure than it is today.
> If somebody else is interested enough to do the legwork, we can
> look at what they come up with.
Given the current assumptions the code makes about the bootstrap superuser,
I think it makes sense to disallow removing its superuser attribute (at
least via ALTER ROLE NOSUPERUSER). It seems like there is much work to do
before a no-superuser configuration could be formally supported. If/when
such support materializes, it might be possible to remove the restriction
that Robert is proposing.
--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com
From | Date | Subject | |
---|---|---|---|
Next Message | Martin Kalcher | 2022-07-21 17:29:12 | Re: [PATCH] Introduce array_shuffle() and array_sample() |
Previous Message | Alvaro Herrera | 2022-07-21 17:12:35 | Re: PG 15 (and to a smaller degree 14) regression due to ExprEvalStep size |