MIME-Version: 1.0
In-Reply-To: <a04ba257-712f-b47e-54bd-a2ee1087f014@2ndQuadrant.com>
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>
 <a04ba257-712f-b47e-54bd-a2ee1087f014@2ndQuadrant.com>
From: Dave Page <dpage@pgadmin.org>
Date: Sun, 8 Jan 2017 11:00:15 +0000
Message-ID: 
 <CA+OCxoyXniWV1rgyP9C1URFGb3z4rpsM29Dn5-i1DvbjykV84w@mail.gmail.com>
Subject: Re: Moving to HTTPS
To: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>,
	"buildfarm-members@postgresql.org" <buildfarm-members@postgresql.org>,
	"buildfarm-admins@postgresql.org" <buildfarm-admins@postgresql.org>
Content-Type: multipart/alternative; boundary=001a1144e1b4f6e1cd05459327c8
Precedence: bulk
Sender: buildfarm-members-owner@postgresql.org

--001a1144e1b4f6e1cd05459327c8
Content-Type: text/plain; charset=UTF-8

On Sunday, January 8, 2017, Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
wrote:

>
>
> On 01/07/2017 07:12 PM, Tom Lane wrote:
>
>> Andrew Dunstan <andrew.dunstan@2ndquadrant.com> 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?
>>
>
I get the same on the machine hosting casteroides and protociurus:

-bash-3.00$ /opt/csw/bin/perl -MLWP::Simple -e 'print qq{BAD\n} unless
head(q{https://www.postgresql.org});'
BAD

installing LWP::Protocol::https failed miserably with both Sun Studio and
GCC :-(


> Ugh. I was afraid of something like that. We might need to look at
> providing a proxy or something.
>

That would kinda defeat the point of us trying to secure everything :-(


-- 
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

--001a1144e1b4f6e1cd05459327c8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<br><br>On Sunday, January 8, 2017, Andrew Dunstan &lt;<a href=3D"mailto:an=
drew.dunstan@2ndquadrant.com">andrew.dunstan@2ndquadrant.com</a>&gt; wrote:=
<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex"><br>
<br>
On 01/07/2017 07:12 PM, Tom Lane wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Andrew Dunstan &lt;<a>andrew.dunstan@2ndquadrant.<wbr>com</a>&gt; writes:<b=
r>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Yeah, you&#39;re right. Or perhaps even more simply we could do:<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 perl -MLWP::Simple -e &#39;print qq{BAD\n} unle=
ss head(q{<a href=3D"https://www.postgresql.org" target=3D"_blank">https://=
www.postgresql.<wbr>org</a>});&#39;<br>
</blockquote>
Hmm, so that reports BAD on all four of my buildfarm critters :-(.<br>
<br>
On longfin, which is running a current macOS release, &quot;cpan install<br=
>
LWP::Protocol::https&quot; seems to be enough to fix it; but on the other<b=
r>
three, I get various flavors of failure.=C2=A0 It looks like the root cause=
 is<br>
that the versions of the relevant modules that are currently available<br>
from CPAN assume newer versions of OpenSSL and/or other Perl modules than<b=
r>
these machines have installed.<br>
<br>
I could embark on a massive update binge, but that would sort of defeat<br>
the purpose of testing against old Perl versions.=C2=A0 Thoughts?<br></bloc=
kquote></blockquote><div><br></div><div>I get the same on the machine hosti=
ng casteroides and protociurus:</div><div><br></div><div><div>-bash-3.00$ /=
opt/csw/bin/perl -MLWP::Simple -e &#39;print qq{BAD\n} unless head(q{<a hre=
f=3D"https://www.postgresql.org">https://www.postgresql.org</a>});&#39;</di=
v><div>BAD</div></div><div><br></div><div>installing LWP::Protocol::https f=
ailed miserably with both Sun Studio and GCC :-(</div><div>=C2=A0</div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">
Ugh. I was afraid of something like that. We might need to look at providin=
g a proxy or something.<br></blockquote><div><br></div><div>That would kind=
a defeat the point of us trying to secure everything :-(=C2=A0</div><br><br=
>-- <br>Dave Page<br>Blog: <a href=3D"http://pgsnake.blogspot.com" target=
=3D"_blank">http://pgsnake.blogspot.com</a><br>Twitter: @pgsnake<br><br>Ent=
erpriseDB UK: <a href=3D"http://www.enterprisedb.com" target=3D"_blank">htt=
p://www.enterprisedb.com</a><br>The Enterprise PostgreSQL Company<br><br>

--001a1144e1b4f6e1cd05459327c8--