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 1fv3Sr-0005XX-65 for pgsql-admin@arkaria.postgresql.org; Wed, 29 Aug 2018 16:37:05 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fv3Sp-0005wb-0T for pgsql-admin@arkaria.postgresql.org; Wed, 29 Aug 2018 16:37:03 +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 1fv3So-0005wU-Pm for pgsql-admin@lists.postgresql.org; Wed, 29 Aug 2018 16:37:02 +0000 Received: from mail-wr1-x42d.google.com ([2a00:1450:4864:20::42d]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fv3Sl-0003rj-JN for pgsql-admin@lists.postgresql.org; Wed, 29 Aug 2018 16:37:02 +0000 Received: by mail-wr1-x42d.google.com with SMTP id v90-v6so5454350wrc.0 for ; Wed, 29 Aug 2018 09:36:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:thread-index :content-language; bh=CREmpME8FhvgGkqEngizsernRanqrv6w/XJ3TtxK8Cc=; b=qE4faQYfoh/KvSXcrlFYeH0eQEAUpM2ojgE1wpy6UAv59ySlIOT1mh7AOl1vd02QKF 2zEx7/h+/VK/xySmTvy2q9e212Js9um2WQQZFqqgo2Dzz4rj2IeHSPxhezcv5Wm1Yp9U UIV9SaLVJUsOjzHOCZTtk9n+oJk3R/pXZVwzo1nNVTxs4bsButG+oOePMK36lXbpKQqq P18vY+CUrgkHAJc0iDipg4hcHB5b/gBjdl8Cw7IufboffS9GF9pOOfjNtKCF82MrY6GU Oq2bp78Cj29rqt9GdrCvR+yciyJg02r0Zuh95XCoWtXXXDS5/XP2AtFnsnCC5qe7rEG9 BzxQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=CREmpME8FhvgGkqEngizsernRanqrv6w/XJ3TtxK8Cc=; b=djuHFP7zgRyCfpozggyRi/3t8A6k5rWoYzjBic+rSUpAU75+QJx4JJv8PH3EseKVjz vHJLOQFtACEMjrO3P3TRfdZRjkDHjxEAFpL2osVmz+IPklB+E7xBBvIpy+zgfyN7W1ID wnM+Mme+45k/fPMHQD0Y5F7xGAgIpdYHTj8h5vCMOaMSZN5Bdg+Z9DbIQYlOoknvEQpf gTp10yGBtUWFdEbHvsyTjo++5m3QBkIIOTihuPSE2YXo/c3DdwR7lyOxsCkoBxBA+lzr +dtUcFEzzsCm+8inBxP1d/Ubn1yrRIpKyFkCKvlXNpq3xOBDGfH0cugc7NDFM7LXWlCl YTiQ== X-Gm-Message-State: APzg51CJ5j+/Sx4RHDriFa9uUgUH1wdlVoPla/T42Dk93Zfm6a/rYaIt e7mnKo+xTvyC9ChXgQUjx+bzRV5JsYw= X-Google-Smtp-Source: ANB0VdZ0oc7GrOD+OqwoUMF15sNKwXz6Vrhji6kGaIdQIq0LbA3hUYdn1JKTvN1hvczKomSEo8zyVw== X-Received: by 2002:adf:a30a:: with SMTP id c10-v6mr5187239wrb.31.1535560618484; Wed, 29 Aug 2018 09:36:58 -0700 (PDT) Received: from LAPTOPE7EH7MDP (167.221-30-62.static.virginmediabusiness.co.uk. [62.30.221.167]) by smtp.gmail.com with ESMTPSA id 34-v6sm7418414wra.20.2018.08.29.09.36.57 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Aug 2018 09:36:57 -0700 (PDT) From: "Mark Williams" To: "'Dai, Tino'" , "'Tim Cross'" Cc: , , "'Wim Bertels'" 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> <1535486102822.43883@loc.gov> In-Reply-To: <1535486102822.43883@loc.gov> Subject: RE: FW: Setting up SSL for postgre Date: Wed, 29 Aug 2018 17:36:55 +0100 Message-ID: <01de01d43fb6$7feec820$7fcc5860$@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQJ64nPKQfAewiPZ9t7gQ7SiT+1fnwIMhi/1AcD6KUcCiXXq5QDWmBXZAcT4CjwCSq7bNgG5QIOHAnC1B7+jDm5SEA== Content-Language: en-gb List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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 Sent: 28 August 2018 20:55 To: Mark Williams ; 'Tim Cross' Cc: pgsql-admin@lists.postgresql.org; s.dunand@sirap.fr; 'Wim Bertels' 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 Sent: Tuesday, August 28, 2018 2:52 PM To: 'Tim Cross' Cc: pgsql-admin@lists.postgresql.org; s.dunand@sirap.fr; '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 =