Hi Tino, Thanks for the link. Unfortunately, it relates to a MS SQL server, which has the TrustServerCertificate connection parameter. That doesn't exist for Postgre. But thanks anyway. Look like I will have to give up on Postgre after all! Mark __ -----Original Message----- From: Dai, Tino <tdai@xxxxxxx> Sent: 28 August 2018 20:55 To: Mark Williams <markwillimas@xxxxxxxxx>; 'Tim Cross' <theophilusx@xxxxxxxxx> Cc: pgsql-admin@xxxxxxxxxxxxxxxxxxxx; s.dunand@xxxxxxxx; 'Wim Bertels' <wim.bertels@xxxxxxx> Subject: Re: FW: Setting up SSL for postgre Before you do give up on postgres, take a look at this. I'm not sure if you have tried this: https://stackoverflow.com/questions/16496199/firedac-sql-server-connection-u ntrusted-certificate -T ________________________________________ From: Mark Williams <markwillimas@xxxxxxxxx> Sent: Tuesday, August 28, 2018 2:52 PM To: 'Tim Cross' Cc: pgsql-admin@xxxxxxxxxxxxxxxxxxxx; s.dunand@xxxxxxxx; 'Wim Bertels' Subject: RE: FW: Setting up SSL for postgre Hi Tim, Thanks for the reply. Unfortunately, I don't know what private certificate authorisation is. I assume this is different to SSL and is not the same as a self signed cert. I have created my certificate with OpenSSL so I assume I am not in the arena of private certificate authorisation. Thanks for the tip re Debian, but sadly client and server are all Windows machines. I think I will put a plea out there to anyone who uses FireDAC and has managed to get SSL working with Postgre. Absent anything useful there, I will give up on Postgre. All the best. Mark =
