public inbox for [email protected]
help / color / mirror / Atom feedFrom: Dave Page <[email protected]>
To: Andrew Dunstan <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: [email protected] <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: Moving to HTTPS
Date: Sun, 8 Jan 2017 11:00:15 +0000
Message-ID: <CA+OCxoyXniWV1rgyP9C1URFGb3z4rpsM29Dn5-i1DvbjykV84w@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20buildfarm-members>
On Sunday, January 8, 2017, Andrew Dunstan <[email protected]>
wrote:
>
>
> On 01/07/2017 07:12 PM, Tom Lane wrote:
>
>> Andrew Dunstan <[email protected]> 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
view thread (15+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: Moving to HTTPS
In-Reply-To: <CA+OCxoyXniWV1rgyP9C1URFGb3z4rpsM29Dn5-i1DvbjykV84w@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox