Page MenuHomePhabricator

replace sha1 cert with sha256 cert
Closed, ResolvedPublic


This tracks the replacement of sha1 cert with sha256 cert.

I'll link in the patchset, but I am not sure if we should simply push without announcement? Dumps are their own particular service, and interrupting any current downloads seems mean.

Event Timeline

RobH claimed this task.
RobH raised the priority of this task from to High.
RobH updated the task description. (Show Details)
RobH added projects: acl*sre-team, HTTPS.
RobH added subscribers: Dzahn, RobH, Krenair and 8 others.

So while I see no https traffic on the system, I do see regular http traffic, and reloading apache for the https change will affect those downloads.

When there is no traffic, the following patchset can be merged:

Then, once it is live on palladium, someone can rm the file /etc/ssl/certs/ and then run puppet. Once puppet runs, reloading apache should show the new certificate.

Also, Once this is completed, we need to revoke the SHA1 cert. So someone can do this via rapidssl, or I'll do so once the other ticket is live.

(Anyone can push this change live when they notice there is no http/https traffic on ms1001. You can check with the following commands:

netstat | grep http
netstat | grep https

followed my own advice, and the one http connection that wasnt a crawler or neon just died, so pushing now.

so the cert is in the filesystem on ms1001, but isnt serving it. ive restarted and reloaded nginx, so not sure whats up. I'll keep hacking at it, but usability isnt gone, just still shows SHA1 cert.

This changeset ( will, after the old /etc/ssl/localcerts/ is moved out of the way, force the generation of a new one. Verified on ms1001. However nginx does not start up with the new crt file because the old private key is still being used (where is the new one? I don't see it in the private repo.) I have put the old crt file back in place for now.

It is the same private key, no change.

Hrmm, that change is correct, and this should work. Let me loop back to this shortly.

Fixed, we had the old 'leading blank before ---BEGIN line in the cert' bug. Deployed and serving. Closing ticket.