Top all-time · #6280
blog.digicert.com
Company blog · blog.digicert.comsecurityprogramming
blog.digicert.com is the company blog at blog.digicert.com, writing about security and programming. Since 2014, 13 different Hacker News readers have linked it 15 times, most often “How to Fix OS X Certificate Issues”. No feed was found, so read it on the site itself.
Too few sampled comments (11) to say how often HN recommends it.?
Why HN links it
DigiCert blog posts on SSL/TLS certificates, including the expired intermediate certificate, Heartbleed, .onion certificates and Certificate Transparency. Commenters mostly cite them as sources, and a few point readers to them as the explanation to read.
Summarised by Claude from a sample of 11 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- How to Fix OS X Certificate Issues3 people · 3 mentions · first linked 2014-07-27
- /certificate-transparency-required-ev-certificates-show-green-address-bar-chrome/2 people · 2 mentions · first linked 2016-02-12
- /understanding-the-google-chrome-connection-tab/2 people · 2 mentions · first linked 2015-05-14
What Hacker News says?
I now see that we're not really talking about alerts in the 'alert()' sense, but rather about the popups - which are not native widgets (which are better off non-modifiable, in my opinion). My bad. Do you know of any good reading material concerning these form validation popups? From reading on MDN [0], they seem to be browser specific - like the Chrome connection tab [1] - but somewhat customisable via JS. [0]: htt…
Comment linking /understanding-the-google-chrome-connection-tab/
on “You might not need JavaScript”Submitted Supporting the Anonymous Use of Facebook via Tor as a story · 64 points
HN discussionThe solution to this is Certificate Transparency[0], a distributed public log of certificate timestamps that are submitted by CA's and checked by browsers. CT has been required for EV certificates in Chrome for a year now[1], and eventually will be required for all certificates otherwise they will error out on connection. A certificate signed by a root cert that is not the original CA will not validate. [0] https://…
Comment linking /certificate-transparency-required-ev-certificates-show-green-address-bar-chrome/
on “Download.com and Others Bundle Superfish-Style HTTPS Breaking Adware”- mo · 2015-12-15
Submitted Ordering a .Onion Certificate from DigiCert – DigiCert Blog as a story · 3 points
HN discussion We've posted an update on the DigiCert blog: https://blog.digicert.com/openssl-patches-security-vulnerabi... No affect on any issued SSL Certificates, that's always a positive.
Comment linking /openssl-patches-security-vulnerabilities-2/
on “OpenSSL Security Advisory”Submitted How to Fix OS X Certificate Issues as a story · 1 points
HN discussionDigicert has already issued at least one certificate to a .onion address[0]. See [1] for additional info [0]: https://blog.digicert.com/anonymous-facebook-via-tor/ [1]: https://blog.digicert.com/the-current-state-of-onion-certifi...
Comment linking /the-current-state-of-onion-certificates-and-what-happens-next/
on “Onion names reserved by the IETF”I think this is the experience of a lot of people and good security folks are taking notice to try and help: https://blog.digicert.com/understanding-the-google-chrome-co...
Comment linking /understanding-the-google-chrome-connection-tab/
on “Why your 'A' grade SSL is 'outdated cryptography' on Chrome”Yep, I was just hassling our billing SaaS provider about this, but then I looked into their SSL vendor heartbleed post, and their customers mention this in the comments: 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."
Comment linking /2014/04/heartbleed-openssl-fix/
on “OpenSSL Heartbleed Security Update”It’s intentional. The general idea is to make it easier to detect fraudulently issued certificates. LetsEncrypt submit all certificates[0] to Certificate Transparency[1] logs. Chrome won’t actually show the green address bar for EV certs unless a CT proof is provided along with the certificate[2]. [0] https://letsencrypt.org/certificates/ [1] https://www.certificate-transparency.org/faq [2] https://blog.digicert.com…
Comment linking /certificate-transparency-required-ev-certificates-show-green-address-bar-chrome/
on “Watch LetsEncrypt issue its millionth certificate live”Thanks, very helpful, though I think affected users are going to want to use this link instead: http://blog.digicert.com/expired-intermediate-certificate/
Comment linking /expired-intermediate-certificate/
on “GitHub and BitBucket's SSL Provider's Cert has expired”For a full explanation on the legacy intermediate explanation and affected users see DigiCert's post: https://blog.digicert.com/expired-intermediate-certificate/
Comment linking /expired-intermediate-certificate/
on “GitHub and BitBucket's SSL Provider's Cert has expired”https://blog.digicert.com/onion-officially-recognized-specia... http://www.thewhir.com/web-hosting-news/iana-designates-onio... http://blog.explodingads.com/?p=155261 https://en.wikipedia.org/wiki/.onion
Comment linking /onion-officially-recognized-special-use-domain/
on “IETF and IANA Officially Designate .onion as a “Special Use Domain””That's actually the cert on your computer allowing you to trust it that has expired. https://blog.digicert.com/expired-intermediate-certificate/
Comment linking /expired-intermediate-certificate/
on “GitHub's issuing CA has expired (DigiCert High Assurance EV Root CA)”