Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cQ6Y6-0005By-7j for buildfarm-members@arkaria.postgresql.org; Sun, 08 Jan 2017 06:01:46 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cQ6Y5-0000oe-4y for buildfarm-members@arkaria.postgresql.org; Sun, 08 Jan 2017 06:01:45 +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 1cQ6Y4-0000oY-SN for buildfarm-members@postgresql.org; Sun, 08 Jan 2017 06:01:45 +0000 Received: from 173-164-140-181-sfba.hfc.comcastbusiness.net ([173.164.140.181] helo=fetter.org) by makus.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cQ6Y2-0005vm-1U for buildfarm-members@postgresql.org; Sun, 08 Jan 2017 06:01:43 +0000 Received: by fetter.org (Postfix, from userid 1000) id 2638FE06D4; Sat, 7 Jan 2017 22:01:40 -0800 (PST) Date: Sat, 7 Jan 2017 22:01:40 -0800 From: David Fetter To: buildfarm-members@postgresql.org Subject: Re: Moving to HTTPS Message-ID: <20170108060140.GA27033@fetter.org> 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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3104.1483834327@sss.pgh.pa.us> User-Agent: Mutt/1.7.1 (2016-10-04) X-Pg-Spam-Score: -0.9 (/) 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 On Sat, Jan 07, 2017 at 07:12:07PM -0500, 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.postgresql.org});' > > Hmm, so that reports BAD on all four of my buildfarm critters :-(. > > On longfin, which is running a current macOS release, "cpan install > LWP::Protocol::https" seems to be enough to fix it; but on the other > three, I get various flavors of failure. It looks like the root cause is > that the versions of the relevant modules that are currently available > from CPAN assume newer versions of OpenSSL and/or other Perl modules than > these machines have installed. > > I could embark on a massive update binge, but that would sort of defeat > the purpose of testing against old Perl versions. Thoughts? You could use install a more modern Perl version just for the buildfarm client while keeping the system perl marooned however far in the past we promise to support. Don't know just how painful that is on those machines... Best, David. -- David Fetter http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate -- Sent via buildfarm-members mailing list (buildfarm-members@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/buildfarm-members