Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nD3ut-0003w9-6T for pgsql-admin@arkaria.postgresql.org; Thu, 27 Jan 2022 12:30:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nD3ur-0007AE-5J for pgsql-admin@arkaria.postgresql.org; Thu, 27 Jan 2022 12:30:17 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nCxgB-00028M-Op for pgsql-admin@lists.postgresql.org; Thu, 27 Jan 2022 05:50:43 +0000 Received: from mail-pl1-x636.google.com ([2607:f8b0:4864:20::636]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nCxg9-0000QG-9J for pgsql-admin@lists.postgresql.org; Thu, 27 Jan 2022 05:50:42 +0000 Received: by mail-pl1-x636.google.com with SMTP id c3so1599278pls.5 for ; Wed, 26 Jan 2022 21:50:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version; bh=WCJAmV87wKraAt5xyJyuQR9ijzWHrYyigw8uDMRExts=; b=P7rWcXss7T29ivqTqyDRdgPgrz+IhLuD9Uh5Ag9+9HFJCIBmyTxYo5hwz8KmdsU1US sXsWb7mz4wvIS8eqn8i+bZeljCxPNVAR9nhECOlMafTVRg8NOn62D78VZ0bo8CVrmD5r Z3cCFBzyOas9EnQd/AI68rJfW7hCAMfvLj0CPHeBQQ+STSOhGgfcniw00W9UY5qoBO9B 0KKe2aZkOMVpvXx8nv9oIWZJflOUzRj30+y/p5O8Hbm+r3YAaOQKTFUEbu3BRB5ONM+3 3FEwN+zVOfM0aCNLdVtN0hxlBl61SIaK1H1ncGfxtZJW+hN+8fYOwh/PYj612brnMFbz 6R9Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:message-id:in-reply-to :references:subject:mime-version; bh=WCJAmV87wKraAt5xyJyuQR9ijzWHrYyigw8uDMRExts=; b=f7p233pjAK6Ob6QyYaZ0WvdwQdyzTbdHWx5nl24UEiOHqPD5DoD77Kfbd1cHBjovsW DNUU75pY4jTTw0JDXDXM1i46SNKYaS1FkLES/SDVHbQtO+9D3ST9U1a3Vhh8bq3PkYHe s/YvLWP7ODc100YGmIkM9HeQjji3kJfoLBFB1ZdPKb4oQQbGBYlTxpuMInuBo3noXFOl iGbYd7ogmAA8x2ji0Gt2Bf1C1E+Eqaxkp1mLskb8XCdcNhHxvYuQDX4StIhUXgfd+fNq tWa3h2W8lu9o/kzwmtBHQURE188GlAYtY9eArOgoxNjCcQS4vYjD67OMR5GS2It6KNKY SIbQ== X-Gm-Message-State: AOAM531pdu9+wl+O3MG8wY6UjHjBVltch9bhoeJr63YLFt9/ZESM4g4p kMXvNltz5ndfYLwcBhh5cQ8= X-Google-Smtp-Source: ABdhPJzxg/M4af6k+AzQ226t1NLaNAf9QFoGratWM1215/PpYLGrWDKcPfFi55IIAX1Tn68q4nu77w== X-Received: by 2002:a17:90a:970a:: with SMTP id x10mr2573373pjo.41.1643262640015; Wed, 26 Jan 2022 21:50:40 -0800 (PST) Received: from [192.168.1.162] ([103.211.52.175]) by smtp.gmail.com with ESMTPSA id q9sm4076826pfj.113.2022.01.26.21.50.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Jan 2022 21:50:39 -0800 (PST) Date: Thu, 27 Jan 2022 11:20:23 +0530 From: Imran Haider To: Tom Lane , pramod kg Cc: "=?utf-8?Q?pgsql-admin=40lists.postgresql.org?=" Message-ID: In-Reply-To: References: <2536077.1643261557@sss.pgh.pa.us> Subject: Re: Is PG CE is FIPS Aware? X-Readdle-Message-ID: f35c335c-5b39-4307-8761-c29811488a19@Spark MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="61f232a9_229b25f3_7abe" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --61f232a9_229b25f3_7abe Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline https://www.stigviewer.com/stig/postgresql=5F9.x/ Regards, Imran Haider On 27 Jan 2022, 11:18 +0530, pramod kg , wrote: > Thanks Tom for your quick response. > > I executed query. Got output. > > postgres=3D=23 SELECT md5('foo'); > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0md5 > ---------------------------------- > =C2=A0acbd18db4cc2f85cedef654fccc4a4d8 > (1 row) > > > Do we have official documentation=C2=A0or any blogs which guides us to = make PG installation =46IPS Compliant=3F Also, is it achievable=C2=A0via = RPM based installation=3F Or do we need to compile libraries=3F > > > > > > > On Thu, Jan 27, 2022 at 11:02 AM Tom Lane wrote: > > pramod kg writes: > > > How to determine whether PG installed in a server is =46IPS aware o= r not(=46IPS > > > 140-2 compliant)=3F We are doing RPM based installation. > > > > If =22SELECT md5('foo')=22 fails, then =46IPS restrictions are active= . > > > > =C2=A0=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0regards, tom lane --61f232a9_229b25f3_7abe Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
https://www.stigviewer.com/stig/postgresql=5F9.x/

Regards,
Imran Haider
On 27 Jan 2022, 11:18 +0530, pramod kg <pramod11= 287=40gmail.com>, wrote:
Thanks Tom for your quick response.

I executed query. Got output.

postgres=3D=23 SELECT md5('foo');
&=23160; &=23160; &=23160; &=23160; &=23160; &=23160; &=23160; &=23160;md= 5
----------------------------------
&=23160;acbd18db4cc2f85cedef654fccc4a4d8
(1 row)


Do we have official documentation&=23160;or any blogs which guides us to = make PG installation =46IPS Compliant=3F Also, is it achievable&=23160;vi= a RPM based installation=3F Or do we need to compile libraries=3F&=23160;=






On Thu, Jan 27, 2022 at 11:02 AM Tom Lane <tgl=40sss.pgh.pa.us&g= t; wrote:
pramod kg <pramod11287=40gmail.com<= /a>> writes:
> How to determine whether PG installed in a server is =46IPS aware or= not(=46IPS
> 140-2 compliant)=3F We are doing RPM based installation.

If =22SELECT md5('foo')=22 fails, then =46IPS restrictions are active.
&=23160;&=23160; &=23160; &=23160; &=23160; &=23160; &=23160; &=23160; &=23= 160; &=23160; &=23160; &=23160; &=23160;regards, tom lane
--61f232a9_229b25f3_7abe--