“This connection is not secure” solution. If you get an “This connection is not secure” error page, read the tutorial below. Do large companies that operate on the web create changes for users or, on the contrary, suffer? However, they must adapt by offering new features in their services, updating them constantly. Google Chrome, Firefox and others are no exception to this rule.
What does “This connection is not secure” mean?
If Google Chrome, Firefox and others are showing “your connection is not secure”, it’s because it has a good reason. It is not your Internet connection but the connection between your computer, that is ISP, and the site you are trying to visit. We will try to schematize all this.
When accessing a site, the computer sends and receives information about the servers of the site in question. With the http protocol, used until recently, the data transferred was not confidential, could be seen by anyone (at least to those who knew how to do it) because it was not encrypted. At a time when you are constantly accessing sites thanks to identifiers/passwords (e-mails, banks, etc.), an improvement in security is obviously essential.
“This connection is not secure” for displaying this message
It is for this reason that another protocol has been added to HTTP: SSL. Together they form https. The end S obviously refers to “secure” and indicates that now the connection is encrypted between the user, each end with the decryption key to understand the value of the information provided. Without this key, no one else can access the information. Obviously, in practice, the user does not see any of this, simply inserting his credentials as before, but in the shadows everything is much safer.
That’s fine, but what is the relationship with Google Chrome, Firefox and others?
Google Chrome Google Chrome, Firefox and others connect you to the server (s) of the sites you visit. The problem is that not everyone has chosen the https protocol: many have remained in HTTP and therefore are not up to current security standards. It’s been a while since the sites have the opportunity to use https but not all of them do (this can have various reasons: lack of resources, lack of seriousness, etc.). And they continue to stay in HTTP.
Google has decided that its Chrome 68 browser will consider unsafe HTTP sites. When you use the browser, you will get a message explaining that the site is not safe and therefore potentially dangerous. On the one hand, this protects the user from security issues and can put pressure on recalcitrant webmasters, as this error message can affect their traffic. Note that users will still be able to visit the site, agreeing to take the risk despite Chrome’s warning.
Things must be as simple as possible for the user: connections must be as secure as possible with the greatest possible transparency. Therefore, we think that if we are not told anything, everything is perfectly safe and now that we are talking about https, we will think we are at a risk level 0.
One thing to keep in mind: https does not mean you will not have problems. If the site/company server is hacked, you will have problems. If your account is hacked (the hacker can get your credentials) in one way or another, you will have problems. The https is not the miraculous solution that protects you from all the problems!