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 1fuj6r-0007QN-Iq for pgsql-admin@arkaria.postgresql.org; Tue, 28 Aug 2018 18:53:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fuj6p-0008J4-FN for pgsql-admin@arkaria.postgresql.org; Tue, 28 Aug 2018 18:52:59 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fuj6p-0008IS-1Y for pgsql-admin@lists.postgresql.org; Tue, 28 Aug 2018 18:52:59 +0000 Received: from mail-wr1-x431.google.com ([2a00:1450:4864:20::431]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fuj6l-0005b1-I2 for pgsql-admin@lists.postgresql.org; Tue, 28 Aug 2018 18:52:57 +0000 Received: by mail-wr1-x431.google.com with SMTP id j26-v6so2526824wre.2 for ; Tue, 28 Aug 2018 11:52:55 -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=YNied6hbVho3MGKYl3esLYwM1PMwoAzNZWULFD5yGT0=; b=dZ0DKlVvMi09j3mU0ddCVgh08UFQGzevUHUcuvy5ihxf3JP9hOqOP2YhiUDjjVxiae V+8uh1KDpFljYIZ9KOH2OvfKjsOLVzl8yv3NNY2IjMcLLR0JYJhdkxzmnCY+SYDas3d4 l9InF2vF/tqOxu516X72K5RTmyYMboDnWtmCoq5H7geJdrBRCyhZdES1+113Ru44CAgp sepLFpJcTtLBtIs68Tuaqv9WvTaTJSV4/lqUrPQGWAZJHeBV3DIMJSMg3cVMbd3/JBjr OKHpd62wT/YU2Q6144hWr0tznOYnIuCwG0Jl9fi3qkB7TxX6ZmDWZxO0H0jH+OruZ/9b yyJg== 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=YNied6hbVho3MGKYl3esLYwM1PMwoAzNZWULFD5yGT0=; b=FLfrRuB4q+DXlhFukTxc2x6F++tY5o4cdWYfUwoRdk5lQhIeSz3hpPTU0YrFvOsJkd dYpQRRBK+9FLb2ub+fb3i2uXgSSuAguk62SiaGr8XQw0bhB+3W9jjgDHhNkz1GfxZy51 TOl5nbgVZTtTLbmeAfFA4qwVjgaPTWunNGVROvBm6EYN/RfYEBEEAA5B+t32horN+nFB p2QMWX+hARdCKso3NML/vlNCyZSzaCJzddkmhN1JAlTuvz1Lg+lrLoYZL0ETZ9QXuunV vFxrtHDv/4ZlZb0RMw4uSEI2aiQhZDRHXZ0+yCG1Y74Yns4vsDI6fTZHpBPER4S1bK5C uEMQ== X-Gm-Message-State: APzg51BfTmiEUi9cxbgawMufbbM2wt+ZYe3ZpijjGtp0kmidgAgenMAU u0b6GYlG2SdRPix3I5IY/54EdrJUHD0= X-Google-Smtp-Source: ANB0VdZ2UJgPZEwBAsAMS7YIaIJef3OxbeboF+Ui8elds2qkaAHlA/TXgcrHDQVsCpOVpVkEcJRQeQ== X-Received: by 2002:adf:dfca:: with SMTP id q10-v6mr1914921wrn.113.1535482373705; Tue, 28 Aug 2018 11:52:53 -0700 (PDT) Received: from LAPTOPE7EH7MDP (167.221-30-62.static.virginmediabusiness.co.uk. [62.30.221.167]) by smtp.gmail.com with ESMTPSA id r140-v6sm3573770wmd.7.2018.08.28.11.52.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 Aug 2018 11:52:52 -0700 (PDT) From: "Mark Williams" To: "'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> In-Reply-To: <87efejihy9.fsf@gmail.com> Subject: RE: FW: Setting up SSL for postgre Date: Tue, 28 Aug 2018 19:52:50 +0100 Message-ID: <013b01d43f00$527caf80$f7760e80$@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/1AcD6KUcCiXXq5QDWmBXZAcT4CjwCSq7bNqMuUO/A Content-Language: en-gb List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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 __ -----Original Message----- From: Tim Cross Sent: 27 August 2018 23:05 To: Mark Williams Cc: pgsql-admin@lists.postgresql.org; s.dunand@sirap.fr Subject: Re: FW: Setting up SSL for postgre Mark Williams writes: > > > > > __ > > > > From: Mark Williams > Sent: 25 August 2018 18:14 > To: 'Wim Bertels' > Subject: RE: Setting up SSL for postgre > > > > Hi Wim, > > > > I don't understand. If I don't include the password option, the > connection will be refused because I have not included it. > > > > I am connecting via PGAdmin with the same user ie postgres. > I suspect Wim was referring to private certificate authentication rather than connections over SSL - use the same basic technologies, but for different goals. While it may or may not be useful, I believe that recent versions of Debian actually come with SSL connections enabled by default (using self signed cert). Might provide the example you need? Tim -- Tim Cross