Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fvLn5-0002W7-EV for pgsql-admin@arkaria.postgresql.org; Thu, 30 Aug 2018 12:11:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fvLn2-0004Dm-U2 for pgsql-admin@arkaria.postgresql.org; Thu, 30 Aug 2018 12:11:08 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fvHo4-0000Ua-Mu for pgsql-admin@lists.postgresql.org; Thu, 30 Aug 2018 07:55:56 +0000 Received: from asp-level3-out1.belnet.be ([2001:6a8:3c80::154]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fvHo1-0000U2-So for pgsql-admin@lists.postgresql.org; Thu, 30 Aug 2018 07:55:56 +0000 Received: from BERENS.int.ucll.be (berens.ucll.be [193.190.138.15]) by asp-level3-out1.belnet.be (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id w7U7togL004683 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 30 Aug 2018 09:55:51 +0200 Received: from VAMP.int.ucll.be (10.21.7.31) by webmail.ucll.be (193.190.138.15) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Thu, 30 Aug 2018 09:55:50 +0200 Received: from ROLLING.int.ucll.be (10.21.7.30) by VAMP.int.ucll.be (10.21.7.31) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Thu, 30 Aug 2018 09:55:49 +0200 Received: from ROLLING.int.ucll.be ([fe80::f93b:729:9ace:3688]) by ROLLING.int.ucll.be ([fe80::f93b:729:9ace:3688%14]) with mapi id 15.00.1293.006; Thu, 30 Aug 2018 09:55:49 +0200 From: Wim Bertels To: Mark Williams , "'Tim Cross'" CC: "pgsql-admin@lists.postgresql.org" , "s.dunand@sirap.fr" Subject: Re: FW: Setting up SSL for postgre Thread-Topic: FW: Setting up SSL for postgre Thread-Index: AQJ64nPKQfAewiPZ9t7gQ7SiT+1fnwIMhi/1AcD6KUcCiXXq5QDWmBXZAZlEObIB3ICezALgGU7vAsAuaGQBRyWFQgGcI70louoxBqCAAzjJwIAAHLUAgAFcjwCAAo3wkA== Date: Thu, 30 Aug 2018 07:55:49 +0000 Message-ID: <1535615748971.37236@ucll.be> References: <032401d43326$6c275d80$44761880$@gmail.com> <034901d4333f$d2aa7650$77ff62f0$@gmail.com> <076401d43883$89ec6830$9dc53890$@gmail.com> <000e01d43e32$f35aad40$da1007c0$@gmail.com> <87efejihy9.fsf@gmail.com>,<013b01d43f00$527caf80$f7760e80$@gmail.com> In-Reply-To: <013b01d43f00$527caf80$f7760e80$@gmail.com> Accept-Language: nl-BE, en-GB, en-US Content-Language: nl-BE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.16.6.35] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Spam-Score: undef - relay 193.190.138.15 marked with skip_spam_scan X-CanIt-Geo: ip=193.190.138.15; country=BE; region=Flanders; city=Leuven; latitude=50.8833; longitude=4.7000; http://maps.google.com/maps?q=50.8833,4.7000&z=6 X-CanItPRO-Stream: ucll-out:out (inherits from ucll-out:default,ucll-in:default,advanced:default,base:default) X-Canit-Stats-ID: Bayes signature not available X-Scanned-By: CanIt (www . roaringpenguin . com) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hallo Mark,=0A= =0A= in your pg_hha.conf you have used=0A= =0A= cert=0A= =0A= as authentication,=0A= which is authorization using a certificate=0A= (not a password)=0A= (as mailed before with documentation links)=0A= =0A= did you test pgadmin and firedac from the same client machine?=0A= =0A= hth,=0A= Wim =0A= ________________________________________=0A= Van: Mark Williams =0A= Verzonden: dinsdag 28 augustus 2018 20:52=0A= Aan: 'Tim Cross'=0A= CC: pgsql-admin@lists.postgresql.org; s.dunand@sirap.fr; Wim Bertels=0A= Onderwerp: RE: FW: Setting up SSL for postgre=0A= =0A= Hi Tim,=0A= =0A= Thanks for the reply.=0A= =0A= Unfortunately, I don't know what private certificate authorisation is. I=0A= assume this is different to SSL and is not the same as a self signed cert. = I=0A= have created my certificate with OpenSSL so I assume I am not in the arena= =0A= of private certificate authorisation.=0A= =0A= Thanks for the tip re Debian, but sadly client and server are all Windows= =0A= machines.=0A= =0A= I think I will put a plea out there to anyone who uses FireDAC and has=0A= managed to get SSL working with Postgre. Absent anything useful there, I=0A= will give up on Postgre.=0A= =0A= All the best.=0A= =0A= Mark=0A= =0A= __=0A= =0A= -----Original Message-----=0A= From: Tim Cross =0A= Sent: 27 August 2018 23:05=0A= To: Mark Williams =0A= Cc: pgsql-admin@lists.postgresql.org; s.dunand@sirap.fr=0A= Subject: Re: FW: Setting up SSL for postgre=0A= =0A= =0A= Mark Williams writes:=0A= =0A= >=0A= >=0A= >=0A= >=0A= > __=0A= >=0A= >=0A= >=0A= > From: Mark Williams =0A= > Sent: 25 August 2018 18:14=0A= > To: 'Wim Bertels' =0A= > Subject: RE: Setting up SSL for postgre=0A= >=0A= >=0A= >=0A= > Hi Wim,=0A= >=0A= >=0A= >=0A= > I don't understand. If I don't include the password option, the=0A= > connection will be refused because I have not included it.=0A= >=0A= >=0A= >=0A= > I am connecting via PGAdmin with the same user ie postgres.=0A= >=0A= =0A= I suspect Wim was referring to private certificate authentication rather=0A= than connections over SSL - use the same basic technologies, but for=0A= different goals.=0A= =0A= While it may or may not be useful, I believe that recent versions of Debian= =0A= actually come with SSL connections enabled by default (using self signed=0A= cert). Might provide the example you need?=0A= =0A= Tim=0A= =0A= --=0A= Tim Cross=0A= =0A=