| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | Rizwan Shaukat <rizwan(dot)shaukat(at)hotmail(dot)com> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: how to secure pg_hba.conf |
| Date: | 2022-12-01 18:38:27 |
| Message-ID: | 6D2D4FDC-CCB3-41A3-9B76-D12BB5D43C83@thebuild.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On Dec 1, 2022, at 05:45, Rizwan Shaukat <rizwan(dot)shaukat(at)hotmail(dot)com> wrote:
> we hv requiremnt from security to secure pg_hba.conf file was encryption or password protected on server to protect ip visibilty because these server access by application n thy can amend as well. how we can achive it pls
The only practical way of securing pg_hba.conf is to secure access to the Linux user that PostgreSQL is running as (assuming you are on Linux, of course). That user will need to open and read the file, so there's no way of securing it against that user.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron | 2022-12-01 18:44:54 | Re: how to secure pg_hba.conf |
| Previous Message | Adrian Klaver | 2022-12-01 17:41:17 | Re: Stored procedure code no longer stored in v14 and v15, changed behaviour |