Why do browsers show ugly errors for untrusted SSL certificates?

Question

When faced by an untrusted certificate, every single browser I know displays a blaring error like this:

Why is that?

This strongly discourages web developers to use an awesome technology like SSL out of fears that users will find the website extremely shady. Ilegitimate (ie: phishing) sites do fine on HTTP, so that can't be a concern.

Why do they make it look like such a big deal? Isn't having SSL even if untrusted better than not having it at all?

---

It looks like I am being misunderstood. I am taking issue with the fact that HTTP sites cannot be more secure than an HTTPS site, even if untrusted. HTTP doesn't do encryption or identification. Phishers can make their sites on HTTP and no warnings are shown. In good faith, I am at the very least encrypting traffic. How can that be a bad thing?

Solution 1

SSL provides for secure communication between client and server by allowing mutual authentication, the use of digital signatures for integrity, and encryption for privacy.

(apache ssl docs)

Yep, I don't see anything about third party certificate authorities that all browsers should recognize as "legit." Of course, that's just the way the world is, so if you don't want people to see a scary page, you've got to get a cert signed by someone the browsers will recognize.

or

If you're just using SSL for a small group of individuals or for in-house stuff, you can have people install your root cert in their browser as a trusted cert. This would work fairly well on a lan, where a network admin could install it across the entire network.

It may sound awkward to suggest sending your cert to people to install, but if you think about it, what do you trust more: a cert that came with your browser because that authority paid their dues, or a cert sent to you personally by your server admin / account manager / inside contact?

---

Just for shits and giggles I thought I'd include the text displayed by the "Help me understand" link in the screenshot in the OP...

When you connect to a secure website, the server hosting that site presents your browser with something called a "certificate" to verify its identity. This certificate contains identity information, such as the address of the website, which is verified by a third party that your computer trusts. By checking that the address in the certificate matches the address of the website, it is possible to verify that you are securely communicating with the website you intended, and not a third party (such as an attacker on your network).

For a domain mismatch (for example trying to go to a subdomain on a non-wildcard cert), this paragraph follows:

In this case, the address listed in the certificate does not match the address of the website your browser tried to go to. One possible reason for this is that your communications are being intercepted by an attacker who is presenting a certificate for a different website, which would cause a mismatch. Another possible reason is that the server is set up to return the same certificate for multiple websites, including the one you are attempting to visit, even though that certificate is not valid for all of those websites. Chromium can say for sure that you reached , but cannot verify that that is the same site as foo.admin.example.com which you intended to reach. If you proceed, Chromium will not check for any further name mismatches. In general, it is best not to proceed past this point.

If the cert isn't signed by a trusted authority, these paragraphs follow instead:

In this case, the certificate has not been verified by a third party that your computer trusts. Anyone can create a certificate claiming to be whatever website they choose, which is why it must be verified by a trusted third party. Without that verification, the identity information in the certificate is meaningless. It is therefore not possible to verify that you are communicating with admin.example.com instead of an attacker who generated his own certificate claiming to be admin.example.com. You should not proceed past this point.

If, however, you work in an organization that generates its own certificates, and you are trying to connect to an internal website of that organization using such a certificate, you may be able to solve this problem securely. You can import your organization's root certificate as a "root certificate", and then certificates issued or verified by your organization will be trusted and you will not see this error next time you try to connect to an internal website. Contact your organization's help staff for assistance in adding a new root certificate to your computer.

Those last paragraphs make a pretty good answer to this question I think. ;)

Solution 2

They do that because a SSL certificate isn't just meant to secure the communication over the wire. It is also a means to identify the source of the content that is being secured (secured content coming from a man in the middle attack via a fake cert isn't very helpful).

Unless you have a third party validate that you are who you say you are, there's no good reason to trust that your information (which is being sent over SSL) is any more secure than if you weren't using SSL in the first place.

Solution 3

The whole point of SSL is that you can verify that the site is who it says it is. If the certificate cannot be trusted, then it's highly likely that the site is not who it says it is.

An encrypted connection is really just a side-benefit in that respect (that is, you can encrypt the connection without the use of certificates).

Solution 4

People assume that https connections are secure, good enough for their credit card details and important passwords. A man-in-the-middle can intercept the SSL connection to your bank or paypal and provide you with their own self-signed or different certificate instead of the bank's real certificate. It's important to warn people loudly if such an attack might be taking place.

If an attacker uses a false certificate for the bank's domain, and gets it signed by some dodgy CA that does not check things properly, he may be able to intercept SSL traffic to your bank and you will be none the wiser, just a little poorer. Without the popup warning, there's no need for a dodgy CA, and internet banking and e-commerce would be totally unsafe.

Solution 5

Why is that?

Because most people don't read. They don't what what https means. A big error is MANDATORY to make people read it.

This strongly discourages web developers to use an awesome technology like SSL out of fears that users will find the website extremely shady.

No it doesn't. Do you have any evidence for that? That claim is ridiculous.

This strongly encourages developers and users to know whom they are dealing with.

"fears that users will find the website extremely shady"

What does this even mean? Do you mean "fears that lack of a certificate means that users will find the website extremely shady"?

That's not a "fear": that's the goal.

The goal is that "lack of a certificate means that users will find the website extremely shady" That's the purpose.

View more solutions

Comments

[Chris Thompson]

It's not hard to get a legitimate SSL certificate. These errors happen when something is wrong with the cert -- something users should definitely be aware of!!

[Confluence]

I am not talking about certs that don't match the domain (yes, that is pretty bad). I am talking about certs signed by authorities not in the browser's trusted CA's (eg: self-signed)

[Dean Harding]

@Confluence: what's the difference? If I can self-sign a certificate that says I'm "yourbank.com" then why would you not expect it to throw up an error?

[Matt Greer]

Since literally anyone can make a self signed certificate, they are very correctly not trusted.

[Confluence]

But why do they have to show the error? Sure, an "untrusted" cert can't be guaranteed to be more secure than no SSL, but it can't be less secure. Conversely, why not show the errors for pages on HTTP?

[Confluence]

@Dean You would have to hijack yourbank.com too in that case.

[Confluence]

@Matt See my comment on Justin's answer.

[Justin Niessner]

@Confluence - If you're expecting an untrusted cert, then there is no issue. Ignore the message, move forward, and enjoy the encryption. But if you're going to an e-commerce site, you enter your credit card info, and see an untrusted cert message I would stop (I wouldn't submit that info over regular HTTP either).

[Matt Greer]

Yes but creating your-bank.com or y0urbank.com is not that hard and still easily fools less technical people. Remember the famous paypa1.com scam? (that's a one not the letter 'l')

[Confluence]

That is not the issue. I am talking about having a self-signed cert matching a domain I own, that a user willingly visits.

[Confluence]

@Matt There is nothing stopping scammers from creating y0urbank.com and not using any encryption. Regular users (about 90% of the Internet population) would still be blissfully unaware.

[Greg Hewgill]

@Confluence: How is that situation different from a malicious operator running a site he owns, with a self-signed certificate impersonating an online banking site that the user willingly visits?

[Confluence]

I understand that. Techies understand that. But to a regular user (90% of the Internet population) it just looks extremely shady.

[Sam Watkins]

If they didn't warn about your cert, they wouldn't be able to warn about the MITM attack cert either.

[Justin Niessner]

@Confluence - And it is. If you want to be a mainstream site using SSL, use a third party certificate authority and get a real certificate so people know you are who you say you are trying to be.

[Confluence]

@Greg None. But the browser doesn't warn the user when a malicious site is on HTTP either (unless the browser knows it is malicious)

[Confluence]

My main beef is with the error message. Unencrypted HTTP doesn't do any identification either, but no browser will warn the user about that.

[Dagg Nabbit]

That's not the whole point of SSL, though. Part of the point (a big part) is that the data is encrypted so anyone watching stuff go across the wire can't see your passwords, credit card numbers, sensitive emails, etc. This is a huge benefit of SSL, signed or not.

[Dean Harding]

@no: it's a benefit, yes, but not the whole point. As I said, you can encrypt a socket connection without a certificate, but SSL also validates the identity of the server as one of it's primary features.

[Dagg Nabbit]

All the browser needs to do to prevent that kind of attack is sound an alarm when the RSA key fingerprint changes (whether or not the cert is signed). An unexpected change from a signed cert to another signed cert is just as sketchy as a change from an unsigned cert to another unsigned, or unsigned to signed, or whatever. The point of getting certified is your name gets put on file somewhere so you can be held accountable for evil stuff you might do with people's data.

[Dagg Nabbit]

Are you saying you can open an http-over-ssh socket without using ssl? If so I'd be very curious to see how that works.

[Dean Harding]

@no: no, I'm just saying that encryption is possible without certificates. If the goal had just been about encrypting the connection, then we would have something other than HTTPS/SSL. Since the goal was encryption and identification, then we have SSL and certificates.

[Confluence]

'The goal is that "lack of a certificate means that users will find the website extremely shady" That's the purpose.' Then why aren't these warnings shown to users visiting regular HTTP sites?

[Dagg Nabbit]

encryption and identification ... that was my point, "the whole point of SSL" is not identifying the server, it's also about encrypting your connection to them. You might realize that the server is run by a bunch of underhanded goons but it's still worth it to you to open a connection, as long as nobody else can spy on the transaction... "SSL provides for secure communication between client and server by allowing mutual authentication, the use of digital signatures for integrity, and encryption for privacy." (httpd.apache.org/docs/2.0/ssl/ssl_intro.html)

[André Caron]

Because HTTP is not encrypted, anybody can intercept the content, so man in the middle attacks make no sense. When establishing a one-to-one encrypted connection, you want to make sure you established the connection with the right person!

[Confluence]

That is exactly my point. HTTP => totally insecure, no warning. HTTPS with untrusted cert => possibly insecure, huge warning.

[Dagg Nabbit]

@Confluence - You probably should get warnings about unencrypted pages, but only for pages with sensitive data. The trick is, how does the browser know if there's any sensitive data? It could look for password inputs, but that wouldn't cover everything. I think with HTTPS the assumption is there's some private data being exchanged, so this puts the browser on high alert for things that look fishy.

[B.Z.B]

@Confluence - the idea is to warn the end user as loudly and clearly as possible that something might be wrong. That's considered to be really important.

[laurent]

But you use https when you need secure conection (at least the user thinks it is one) so it needs a warning and http when you don't need one and the user doesn't expects one so there is no need of warning. The warning is to alert the user because an https conection is supposed to be secure and identified while on http nobody expects a secure connection. Anyways, even after the message, I think 99% of the users don't know why the connection is not secure (wrong host or not trusted certificate) so the warning has to be big to stop them in all cases.

[laurent]

Agreed, I think the same and I use self signed certs in both cases - LAN and customers - installing the root cert in their browsers and until now everybody is happy with that because they know the cert will identify my server and will give an alert for another one unless the pirate server owner hacks my DNS and manage to get a trusted cert on my domain and I expect no trusted certificate provider will give one to him!

[Confluence]

"There is no need for a warning because you are not transferring sensitive information." I beg to differ. Many sites that should be using SSL don't use it. They make people login and transmit their passwords over plain HTTP. Often times these people use the same password for their online banking, and that's "sensitive" enough to me. I would protect my users from eavesdroppers if I could use a self-signed cert, but I can't. See my dilemma now?

[Bruno]

@Confluence there is no expectation that the communication with an HTTP site will be secure, hence you don't get any specific warning or reinsurance. There is a user expectation for most users that communication with an HTTPS site will be secure: when the safe-guards (i.e. valid cert) are missing, there is a message to indicate something may be wrong.

[user1066101]

@Confluence: "Then why aren't these warnings shown to users visiting regular HTTP sites?" Because the certificate's not wrong, it's missing. There's a logic problem with presenting an error when (a) there's no certification and (b) no certificate was expected. If you try to use IE in "safe" mode on a non-professional version Windows, you'll see that IE provides all kinds of alerts and warnings at random times and places. The issue is simple logic. http has no certification expectation, so there can't be an error.

[André Caron]

This is how the system works, so you play by the rules. The warning is pressure for you to purchase a certificate from a trusted authority. By not paying for the process of identifying yourself with a trusted certificate, you demonstrate your shadiness and the browser reminds the user you are not willing to go through that process.