Tracking task to replace git's sha1 cert with sha256, in multiple steps:
- - reissue certificate in sha256
- - update configuration of ganglia to use new certificate
- - push changes live
- - revoke old sha1 certificate
Tracking task to replace git's sha1 cert with sha256, in multiple steps:
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
git.wikimedia.org.crt sha1 to sha256 | operations/puppet | production | +26 -29 |
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | RobH | T73156 Replace SHA1 certificates with SHA256 | |||
Resolved | RobH | T100827 replace git's sha1 cert with sha256 |
Change 214673 had a related patch set uploaded (by RobH):
git.wikimedia.org.crt sha1 to sha256
Indeed, it is behind misc-web. I think we can indeed revoke this cert/keypair entirely. I'll keep it assigned to me and do so later today. Once done, I'll remove from our repo(s).
Change 214673 abandoned by RobH:
git.wikimedia.org.crt sha1 to sha256
Reason:
git.w.o lives behind misc-web, this cert doesn't need to exist.
I revoked and deleted the git.wikimedia.org key and certificate, and Daniel's patchset stops the system from installing the now delete (and also unused) cert/key from systems.