Our CA will eventually revoke the previous incarnations of our certificates, signed with the old private keys, making them invalid.
This [1] Seems to suggest that Firefox, for instance, only checks for EV certs?
[1] http://news.netcraft.com/archives/2013/05/13/how-certificate...
We generated new CSRs, with new private keys, but with the same dates and details as the originals. This let us get fresh certs without going through a full renewal.
Thanks for the prod.
http://blog.digicert.com/2014/04/heartbleed-openssl-fix/
Excerpt: "Also, Busy IT Guy is right; it's a little disheartening to be listed as Unsafe after having done all the right things, just because the issue date didn’t get updated."
However, this blogpost says, "As of Tuesday, April 8 at 15:55 UTC, all Heroku certificates and infrastructure have been updated and are no longer vulnerable"... while the certificate still superficially looks like it's almost 3 months old. Something isn't as it seems, I hope it's just the certificate age.
Am I interpreting the certificate info wrong? [edit per official answer below: YES] (Are fresh certificates sometimes given much older start times? [edit: YES])
This blogpost doesn't clearly address *.herokuapp.com HTTPS service, as opposed to the custom-domains "ssl:endpoint" service.