Closed Bug 992753 Opened 11 years ago Closed 11 years ago

Update SSL certificate for ssl-md5.mozqa.com

Categories

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

Product:
Infrastructure & Operations Graveyard
Component:
WebOps: Other
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: whimboo, Assigned: bburton)

References

Details

(Whiteboard: [qa-automation-blocked][change - SSL])

For bug 990557 we need an updated SSL certificate, so that the MD5 certificate tests will continue to work with Mozmill. As David pointed out attachment 8402106 [details] can be used to create a new certificate. See bug 990557 comment 20. Maybe it would be good to check if the other certificates for mozqa.com are also affected, and contain the netscape cert type extension.
Whiteboard: [qa-automation-blocked] → [qa-automation-blocked][change - SSL]
Assignee: server-ops-webops → bburton
Severity: major → normal
* Ran the script, it seems to have worked * Updated /ca/ssl-md5-mozqa-ca.pem with the new CA certificate and am deploying the new md5 certificate now
Status: NEW → ASSIGNED
The new certificate has been installed and pushed live in the Load Balancer, can you test https://ssl-md5.mozqa.com/ and confirm it's working as expected? * Note, the new CA is at https://mozqa.com/ca/ If it looks good, I'll clean up the old certificate and we can RF this bug
Flags: needinfo?(hskupin)
Thanks Brandon! Andreea is the assignee of the appropriate Mozmill test, which was failing. She can test the fix tomorrow. Brandon, have you checked if other SSL certificates of mozqa.com are also affected? Or is it only the MD5 one?
Flags: needinfo?(bburton)
Flags: needinfo?(andreea.matei)
Flags: needinfo?(hskupin)
(In reply to Henrik Skupin (:whimboo) from comment #3) > Thanks Brandon! Andreea is the assignee of the appropriate Mozmill test, > which was failing. She can test the fix tomorrow. > > Brandon, have you checked if other SSL certificates of mozqa.com are also > affected? Or is it only the MD5 one? From what I can tell, the md5 one was the only one generated with this CA that we generated and that we've now updated
Flags: needinfo?(bburton)
Great. Thanks Brandon for checking that! Now lets wait for the verification so that we can close this bug.
This fixed our test so we're good here and since there aren't more certificates to change, I'll close this bug. Thanks Brandon!
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Flags: needinfo?(andreea.matei)
Resolution: --- → FIXED
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.