Story #4710: Refresh certificates following HeartBleed vulnerability
Replace CN client certificate
As part of the fallout from the Heartbleed vulnerability, the CN client certificates need to be regenerated, the old ones revoked, and new ones used in their place.
This should not be done until the production server SSL certificates have been replaced.
- Category set to Environment.Production
- Status changed from New to In Progress
- Assignee set to Chris Jones
I've updated the three server-side SSL certificates for the production CNs, and will move on to the client certs.
Updated by Robert Waltz over 7 years ago
- Target version changed from 2014.16-Block.2.4 to Maintenance Backlog
Also available in: Atom