From: | Imran Haider <ihaiderk(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pramod kg <pramod11287(at)gmail(dot)com> |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Is PG CE is FIPS Aware? |
Date: | 2022-01-27 05:50:23 |
Message-ID: | f35c335c-5b39-4307-8761-c29811488a19@Spark |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
https://www.stigviewer.com/stig/postgresql_9.x/
Regards,
Imran Haider
On 27 Jan 2022, 11:18 +0530, pramod kg <pramod11287(at)gmail(dot)com>, wrote:
> Thanks Tom for your quick response.
>
> I executed query. Got output.
>
> postgres=# SELECT md5('foo');
> md5
> ----------------------------------
> acbd18db4cc2f85cedef654fccc4a4d8
> (1 row)
>
>
> Do we have official documentation or any blogs which guides us to make PG installation FIPS Compliant? Also, is it achievable via RPM based installation? Or do we need to compile libraries?
>
>
>
>
>
>
> On Thu, Jan 27, 2022 at 11:02 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > pramod kg <pramod11287(at)gmail(dot)com> writes:
> > > How to determine whether PG installed in a server is FIPS aware or not(FIPS
> > > 140-2 compliant)? We are doing RPM based installation.
> >
> > If "SELECT md5('foo')" fails, then FIPS restrictions are active.
> >
> > regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-01-27 06:15:28 | Re: Is PG CE is FIPS Aware? |
Previous Message | pramod kg | 2022-01-27 05:44:41 | Re: Is PG CE is FIPS Aware? |