Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cSgM2-0001LW-AG for buildfarm-members@arkaria.postgresql.org; Sun, 15 Jan 2017 08:39:58 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cSgM0-0003Dw-Ic for buildfarm-members@arkaria.postgresql.org; Sun, 15 Jan 2017 08:39:56 +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.84_2) (envelope-from ) id 1cSgLw-0003Aj-0i; Sun, 15 Jan 2017 08:39:52 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cSgLo-0008Qm-5i; Sun, 15 Jan 2017 08:39:50 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id v0F8dg3o007218; Sun, 15 Jan 2017 03:39:42 -0500 From: Tom Lane To: Andrew Dunstan cc: buildfarm-members@postgresql.org, buildfarm-admins@postgresql.org Subject: Re: Moving to HTTPS In-reply-to: References: <89d566b4-58fb-c1e9-97ef-46d4d915b86c@dunslane.net> <20170107215523.GA294152@tornado.leadboat.com> <96080bc2-086f-c47f-6cee-b7f00a9bcd38@2ndQuadrant.com> <3104.1483834327@sss.pgh.pa.us> Comments: In-reply-to Andrew Dunstan message dated "Sat, 07 Jan 2017 21:37:12 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <7216.1484469582.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Sun, 15 Jan 2017 03:39:42 -0500 Message-ID: <7217.1484469582@sss.pgh.pa.us> X-Pg-Spam-Score: -5.1 (-----) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: buildfarm-members Precedence: bulk Sender: buildfarm-members-owner@postgresql.org Andrew Dunstan writes: > On 01/07/2017 07:12 PM, Tom Lane wrote: >> Andrew Dunstan writes: >>> Yeah, you're right. Or perhaps even more simply we could do: >>> perl -MLWP::Simple -e 'print qq{BAD\n} unless head(q{https://www.postgr= esql.org});' >> Hmm, so that reports BAD on all four of my buildfarm critters :-(. > Ugh. I was afraid of something like that. We might need to look at=20 > providing a proxy or something. After further fooling with this, it seems the root cause is that you need Perl (specifically Net::SSLeay) to be linked to OpenSSL 0.9.8 or later. Since we require at least 0.9.8 for PG itself, this does not seem like an unreasonably heavy lift. I found that some of the involved modules, particularly IO::Socket::SSL and LWP::Protocol::https, fail a few of their regression tests even with 0.9.8. But if you tell cpan to ignore that and install them anyway, it seems like things work; at least, the simple test proposed above now works on all four of my buildfarm critters. It will be interesting to see whether that equates to "buildfarm script can talk to https server". Do we have any more-thorough test case available? BTW, if anyone else is like me and has a more modern openssl installed in a non-default location on an old machine, the secret sauce for getting Net::SSLeay to use that is to set environment variable OPENSSL_PREFIX to the openssl install prefix path before building Net::SSLeay. regards, tom lane --=20 Sent via buildfarm-members mailing list (buildfarm-members@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/buildfarm-members