Domain validated SSL certs for google.com.mg and google.com.im (not Google)

https://certsimple.com/blog/domain-validated-ssl-google-com-mg

by nailer • 11 years ago

19 24 11 years ago

nailer8• 11 years ago

Author here. As the article mentions, this is how DV SSL works. The issue is that most people outside tech are conditioned to trust DV identifiers.

As a side note, newer versions of Chrome have stopped using 'identity' for domain validated certificates.

A domain validated cert in Chrome in 47.0.2526.106 http://i.imgur.com/RiISSrU.png

A domain validated cert in Chrome 49.0.2618.0 no longer refers to 'identity' http://i.imgur.com/XkaPDwx.png

The term 'identity' remains in use with extended validation certs - http://imgur.com/j7fKGt1

dchest2• 11 years ago

66 days later google.com.mg is still owned by not-Google, not revoked, and not on any 'safe browsing' warning lists.

So? Why would a website be in safe browsing warning lists if it doesn't do anything malicious? Does Google own a trademark in Madagascar? If so, they probably can take down this domain by asking NIC-MG. If not, then, unless this website is used for phishing, I don't see any problems with issuing a certificate.

(It's interesting how companies selling certificates switched to scare tactics after Let's Encrypt made DV certs free.)

nailer8• 11 years ago

Why would a website be in safe browsing warning lists if it doesn't do anything malicious?

Some of the previous arguments in favour of DV have said that safe browsing lists will catch misissuance.

Whether DV certs are $10 or $0 doesn't make a huge difference: they don't check identity.

dchest2• 11 years ago

Some of the previous arguments in favour of DV have said that safe browsing lists will catch misissuance.

Yes, so what is this website doing that warrants this measure? There was no misissuance.

jpgvm• 11 years ago

I don't get the tone of the article. Why is this a bad thing?

It's not the job of SSL to ensure a domain name is not owned by someone it shouldn't be. That falls to the domain registrar, if you have a problem with someone owning google.com.mg go take it up with the registrar or better yet leave it up to Google as it's THEIR trademark.

I actually find this to be a good thing that someone was able to get a domain, create an SSL certificate for it painlessly and start securing traffic between clients and their web property without having to spend a) tons of money and b) tons of time dealing with antiquated CAs that should be entirely automated.

colinbartlett2• 11 years ago

The tone of the article is such because the company writing it only sells EV certs and therefore is on a relentless quest to discredit DV certs as inferior.

nailer8• 11 years ago

Author here: DV certificates are inferior. Knowing whose key you're encrypting with is a good thing. DNS providers do not do identity checks.

Edit: 100% agreed with laumars' point below regarding blogs and low trust sites. DV certificates have their place, it's just that high trust websites aren't it. I've added an author tag as requested.

HappyTypist• 11 years ago

And furthermore, you shouldn't need to get your identity verified and send in pictures of your ID just to make a website, blog, or custom email domain.

nailer8• 11 years ago

it's not the job of SSL to ensure a domain name is not owned by someone it shouldn't be.

That's correct. CAs checked identity back in the 90s, but stopped and moved to domain validation for most certificates. The article mentions explicitly: the certificates aren't fake, they're just DV, and that's what DV is. Obviously most consumers have no idea about that, and have been conditioned to trust any kind of SSL.

The main issue asides from most consumers having no idea what DV is, is that Section 4.2 of the baseline requirements - which applies to all CAs - asks CAs to check for 'high risk' domains. That's clearly broken here.

Certificate transparency records for the domains in question:

https://crt.sh/?q=google.com.%25

detaro2• 11 years ago

Obviously most consumers have no idea about that, and have been conditioned to trust any kind of SSL.

Is that actually the case? If I see a "check for HTTPS!" reminder, most of them clearly show and talk about the name from a DV cert.

walrus• 11 years ago

So everything is working as intended? Great!

nailer8• 11 years ago

That's the third paragraph of the article. Keep reading.

beeps• 11 years ago

This feels a little like link bait. You don't realize till the end that it's a pitch.

notacoward• 11 years ago

So, in a nutshell, these guys are saying that (a) it's too easy to get a misleading cert and (b) they make it easier to get a certain kind of cert. That's going to be a hard sell. They need to make a case that non-EV certs are worthless not only in terms of security but to consumers - i.e. that you, the certificate buyer, will lose business. Then they need to explain why EV certs are better, and lastly how that superiority can be preserved even on a shorter acquisition timeline. They do none of that. The article is not only too pitch-y for HN, but it's also a poor pitch.

joshmoz• 11 years ago

Head of Let's Encrypt here.

We were aware of the "google.com.mg" cert soon after it was issued. We didn't revoke the cert for the same reason we don't revoke most certs: as far as we can tell, the cert was issued to the entity properly controlling "google.com.mg". Whether or not that is Google (the company) is not really within our purview.

That said, in this case, as a courtesy, we did notify Google employees and made the decision to report the site to Google Safe Browsing. GSB and SmartScreen are the right places to deal with things like this.

IIRC GSB did block the site for a while, but that block seems to be gone now.

nailer8• 11 years ago

Whether or not that is Google (the company) is not really within our purview.

Hi Josh. This is mentioned in the third paragraph of the article, but it looks like HN didn't read that far, so probably worth mentioning it again.

I didn't mention LE specifically out of respect for the work you guys are doing, but since you've posted here: why wasn't this flagged as a High Risk Certificate Request before issuing per Baseline Requirements 4.2.1?

Also where is the High Risk Certificate Request check available in the LE source?

Thanks!

foota• 11 years ago

In other words: DV CA does exactly what it's supposed to do.

Domain validated SSL certs for google.com.mg and google.com.im (not Google)

Related Stories