| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-www(at)lists(dot)postgresql(dot)org |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Subject: | Re: buildfarm server suddenly not talking to old SSL stacks? |
| Date: | 2018-07-17 13:20:31 |
| Message-ID: | 4949d2ba-5869-103b-5496-3a9a8a37cb83@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
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
>
> regards, tom lane
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2018-07-17 13:23:25 | Re: buildfarm server suddenly not talking to old SSL stacks? |
| Previous Message | Magnus Hagander | 2018-07-17 08:44:11 | Re: buildfarm server suddenly not talking to old SSL stacks? |