To: buildfarm-members@postgresql.org
Cc: buildfarm-admins@postgresql.org
From: Andrew Dunstan <andrew@dunslane.net>
Subject: Moving to HTTPS
Message-ID: <89d566b4-58fb-c1e9-97ef-46d4d915b86c@dunslane.net>
Date: Sat, 7 Jan 2017 16:37:47 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: buildfarm-members-owner@postgresql.org


In common with the rest of the PostgreSQL infrastructure, we will 
shortly be moving the buildfarm server to supporting HTTPS, and 
eventually will stop support for plain HTTP. Many installations on 
buildfarm animals will not need any great adjustment, others will need 
some extra modules installed. Here's a simple test that should help tell 
if your animal needs some extra stuff installed. Run something like this 
on your animal, making sure that the perl in your path is the one used 
to run the buildfarm client:


    perl -MLWP::Simple -e 'head(q{https://www.postgresql.org});


If this doesn't complain you should be good. If it does, you probably 
need to install the LWP::Protocol::https module, and anything it depends 
on (e.g. crypto libraries).

This isn't enabled yet, I'm just being proactive so you don't get caught 
having to adjust in a hurry.

Windows users probably don't need to worry - this works on every 
installation of AS perl I have.


cheers


andrew


-- 
Sent via buildfarm-members mailing list (buildfarm-members@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/buildfarm-members