infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Gruno (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-16018) Expired certificates for backend lists.a.o servers
Date Mon, 12 Feb 2018 18:33:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-16018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16361233#comment-16361233
] 

Daniel Gruno commented on INFRA-16018:
--------------------------------------

Colour me blind, but...what problem?
We are pointing lists.a.o to a machine with a perfectly valid cert. There is an older back-end
we're switching away from, it'll go away at some point - but so what if it's there for a few
more days? I honestly can't see any problem with this.

> Expired certificates for backend lists.a.o servers
> --------------------------------------------------
>
>                 Key: INFRA-16018
>                 URL: https://issues.apache.org/jira/browse/INFRA-16018
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Mail Archives
>            Reporter: Sebb
>            Assignee: Daniel Gruno
>            Priority: Major
>
> According to https://reference.apache.org/infra/ponymail
> lists.a.o is run on following servers:
> [1] https://cust-asf.ponee.io/
> [2] https://cust-asf2.ponee.io/ (primary failover)
> with backup cluster:
> [3] https://cust-asf-backup.ponee.io/
> However the certificate for [1] expired Sunday, 10 December 2017 at 23:59:59 Greenwich
Mean Time
> The cert for [2] expired Saturday, 3 December 2016 at 23:59:59 Greenwich Mean Time
> The URL [3] does not respond.
> The expired certificates are not visible to the user of the lists.apache.org host, however
assuming that the documentation is correct and l.a.o still proxies to [1] and/or [2] it seems
to me that the certificates ought to be updated.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message