You are viewing a plain text version of this content. The canonical link for it is here.

Posted to infrastructure-issues@apache.org by "Geoffrey Corey (JIRA)" <ji...@apache.org> on 2015/04/27 19:48:38 UTC

[jira] [Commented] (INFRA-9531) Create/Deploy new wildcard cert without SHA-1

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

Geoffrey Corey commented on INFRA-9531:
---------------------------------------

CSR generated for *.apache.org and added a SAN for apache.org.

Waiting for the cert siging service to approve and sing the cert.

> Create/Deploy new wildcard cert without SHA-1
> ---------------------------------------------
>
>                 Key: INFRA-9531
>                 URL: https://issues.apache.org/jira/browse/INFRA-9531
>             Project: Infrastructure
>          Issue Type: Task
>            Reporter: Geoffrey Corey
>            Assignee: Geoffrey Corey
>
> A ticket (INFRA-9484) has come in where windows is complaining the current wildcard cert is invalid, as well as an email to infrastrucutre-dev about a similar issue.
> Chrome has also begun warning that the current cert is using outdated cryptography.
> This ticket will serve as tracking for replacing the old wildcard with the new on for hosts in puppet.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)