| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, martin(dot)nguyen(at)oracle(dot)com |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18350: Modifying predefined roles' unlimited connections for VA STIG cybersecurity checklist |
| Date: | 2024-02-19 01:02:50 |
| Message-ID: | 09e60516-24cf-7d5a-a0b8-d64e1581994b@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2024-02-16 Fr 16:35, Tom Lane wrote:
> PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
>> We have identified an issue where predefined roles are not modifiable,
>> however a Dept. of VA security checklist requires that no roles have
>> unlimited connections. The Predefined roles have unlimited connections, is
>> there a way to modify these?
> Solution 1: explain to your compliance department that it's pointless
> to worry about the connection limit for a role that can't log in.
>
> Solution 2: do a manual UPDATE on pg_authid. This would have to
> be done over after any major-version upgrade, though.
>
>
Also note that this is not by any stretch of the imagination a bug.
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tender Wang | 2024-02-19 08:21:11 | Re: BUG #18344: Pruning tables partitioned by bool range fails with invalid strategy |
| Previous Message | David Rowley | 2024-02-18 23:49:11 | Re: BUG #18344: Pruning tables partitioned by bool range fails with invalid strategy |