public inbox for [email protected]
help / color / mirror / Atom feedFrom: Andrew Dunstan <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: Moving to HTTPS
Date: Sat, 7 Jan 2017 16:37:47 -0500
Message-ID: <[email protected]> (raw)
List-Unsubscribe: <mailto:[email protected]?body=unsub%20buildfarm-members>
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 ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/buildfarm-members
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]
Subject: Re: Moving to HTTPS
In-Reply-To: <[email protected]>
* 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