From: | <ertan(dot)kucukoglu(at)1nar(dot)com(dot)tr> |
---|---|
To: | <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: pg_dump problem with postgres user |
Date: | 2023-02-12 21:10:38 |
Message-ID: | 001601d93f26$75663540$60329fc0$@1nar.com.tr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello,
My service provider spam filter just blocked your message and so I send a
separate one.
Your suspicion seems like correct. Postgres user is no more a superuser.
Seems like they added postgresql_user and made it superuser.
I thought I only allow access with certificate to the database.
OS access is limited to single IP. Probably this is the weak point.
I should read more about security in general.
postgres=> \du+
List of roles
Role name | Attributes | Member
of | Description
-----------------+-------------------------------------------------+--------
---+-------------
postgres | Create role, Create DB, Replication, Bypass RLS | {}
|
postgresql_user | Superuser | {}
|
postgres=>
Is it possible to put everything back to normal?
Can I use single user mode to change passwords and permissions?
Thanks & Regards,
Ertan
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2023-02-12 21:15:05 | Re: pg_dump problem with postgres user |
Previous Message | Rob Sargent | 2023-02-12 18:58:28 | Re: psql "\d" no longer working |