Google launches Chrome 68 with doomsaying for unsecured websites



[ad_1]

  Google launches Chrome 68 with doomsaying for unsecured websites "title =" Google launches Chrome 68 with doomsaying for unsecured websites "src =" http://www.theinquirer.net/w-images/1c2b14db -8775-438a-ab3f -505f1799e711 / 1 / htmlshutterstock952787141-580x358.jpg "/>

 
<figcaption>
<p>
  If people do not like it, wait HaTeMaiL
</p>
</figcaption></div>
<div>
<p><strong>  GOOGLE PUBLISHED </strong> Chrome 68, the latest version of its number one web browser that brings with it serious security bonuses. </p>
<p>  After <em> INQ </em> some time ago, Chrome 68 must be the first iteration of the browser that warns users that any site without HTTPS encryption is not secure. </p>
<p>  The move is part of Google's long-term goal to run the entire Internet with encryption, and (apparently) Yahoo's ongoing determination to pretend that this is not happening. </p>
<p>  With 81 of the 100 most popular sites on the web, this is not something that most people will notice, but for those who are moving away from the path, there will be some evidence, Glowing warning of dragons inside. </p>
<p>  This is not a huge surprise – Google has been planning and getting ready for months. However, some webmasters still are not convinced why HTTPS is so important. </p>
<p>  Google is already penalizing unsecured sites in its search results, this has been true for some time, but if you have a closed audience, the need for high search rankings is less of a priority, and in this case, the search is not a priority. pulse disappears. Until there is an attack on the site, of course. </p>
<p>  For Android and iOS users, the Site Isolation feature is designed to add belt and braces in the fight against Specter vulnerability. On browser performance, initial reports suggest up to 13%. </p>
<p>  There is a fairly typical level of those who fear that the web will suddenly become imploded, leaving people to cope with new confusing messages from the sites. who have not yet adopted the call to arms, or those who are struggling to implement it causing a potential downtime, but in reality this has not been a huge problem until now. </p>
<p>  The evidence will come, as always, in a few days, when everyone is up to date and (hopefully) at the speed of change. </p>
<p>  Next month, Chrome 69 will remove the message "secure" compliant sites in favor of going ape-shitaki on unsecured instead. μ </p>
</div>
</pre>
</pre>
[ad_2]
<br /><a href=Source link