From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL WWW <pgsql-www(at)lists(dot)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
Subject: | Re: buildfarm server suddenly not talking to old SSL stacks? |
Date: | 2018-07-17 13:23:25 |
Message-ID: | CABUevEyu1sWhdsOeGSZ9gmFSUa+WMJpPtpxM4zp9OjvAY1Z8Ug@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
On Tue, Jul 17, 2018 at 3:20 PM, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:
> On 07/16/2018 08:31 PM, Tom Lane wrote:
>
>> My buildfarm animals dromedary and prairiedog have been failing since
>> around 9AM EDT on Sunday. The buildfarm script output isn't very
>> detailed:
>>
>> getting branches of interest (https://buildfarm.postgresql.
>> org/branches_of_inte\
>> rest.txt) at ./run_branches.pl line 129.
>>
>> but trying it manually yields
>>
>> $ curl https://buildfarm.postgresql.org/branches_of_interest.txt
>> curl: (35) error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1
>> alert protocol version
>>
>> The same thing works fine on newer machines though, as does fetching with
>> http: instead of https:. Have we done something recently to create an
>> incompatibility with old SSL stacks?
>>
>
> Maybe something to do with this?:
>
> https://blog.pcisecuritystandards.org/are-you-ready-for-30-
> june-2018-sayin-goodbye-to-ssl-early-tls
Our buildfarm does not require PCI classification :P
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-07-17 17:04:50 | Re: buildfarm server suddenly not talking to old SSL stacks? |
Previous Message | Adrian Klaver | 2018-07-17 13:20:31 | Re: buildfarm server suddenly not talking to old SSL stacks? |