{"id":1126467,"date":"2024-06-29T11:28:01","date_gmt":"2024-06-29T15:28:01","guid":{"rendered":"https:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/uncategorized\/google-chrome-will-soon-flag-several-websites-for-invalid-certificates-android-police\/"},"modified":"2024-06-29T11:28:01","modified_gmt":"2024-06-29T15:28:01","slug":"google-chrome-will-soon-flag-several-websites-for-invalid-certificates-android-police","status":"publish","type":"post","link":"https:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/google\/google-chrome-will-soon-flag-several-websites-for-invalid-certificates-android-police\/","title":{"rendered":"Google Chrome will soon flag several websites for invalid certificates &#8211; Android Police"},"content":{"rendered":"<p><p>Summary                    <\/p>\n<p>    From the earliest days of computing, computer scientists have    recognized the need for the secure transport of information.    Early computer protocols like Telnet would broadcast    information (like usernames and passwords) across the internet    without encryption, making it visible to anyone who wanted to    look. Those early protocols were replaced with more secure    protocols that rely on public-key encryption to transport data,    and a similar public-key encryption is what most websites today    rely on to move your information securely between their servers    and your browser.  <\/p>\n<p>    Websites use digital certificates to validate their identity    and provide public cryptography keys that your browser can use    to establish a secure connection. But, your browser won't trust    just any certificate. Instead, your browser has an internal    list of trusted certificate issuers (they're usually called    root stores, here's    Chrome's root store) with which it will automatically    establish a secure connection. Today, Google announced that    it's kicking at least one certificate issuer off of that list.  <\/p>\n<p>        Fit, durability, sound quality, and price matter      <\/p>\n<p>    In a post    released today on Google's Security Blog (spotted by    9to5Google), the company singles out the certification    authority (CA) Entrust. It doesn't appear that Entrust has done    just one thing to get on Google's naughty list, rather it's a    pattern of behavior. To get on Google's nice list, CAs have to    jump through more than a    few hoops, and Google makes clear in its blog post that    Entrust has \"fallen short\" of its expectations. Indeed, Google    doesn't mince words when it says Entrust's actions have \"eroded    confidence in their competence, reliability, and integrity as a    publicly-trusted CA Owner.\" Ouch.  <\/p>\n<p>    The exile of Entrust from the annals of the elite CAs won't    take place immediately. Rather, any Entrust certificate issued    after October 31, 2024 will no longer be trusted by Chrome as a    matter of course. That isn't to say that Chrome users will lose    access to any sites that use certificates issued by Entrust,    users will simply need to manually enable trust in Entrust, or    wade through a warning screen when visiting a site that uses    Entrust's certificates. These changes will affect all Chrome    users except for iOS users.  <\/p>\n<p>    You've probably come across a few certificate warnings on your    browser if you've spent any time wandering the web. For the    most part it's not a big deal if you go to one of these    browser-designated \"dangerous\" sites, but you should be aware    that these sites most likely aren't using encryption to move    data between the server and the browser. That means if you use    a username or password on one of these unsecured sites, someone    could be listening in and taking that information from you. In    other words, don't use any personal information on an unsecured    site. Having an up-to-date certificate is also a sign of a    website that takes itself and its security seriously.  <\/p>\n<p>        How can an app send messages that only you can decode?      <\/p>\n<p>    Given that any site using Entrust will now appear as    untrustworthy, many big names on the internet are probably    scrambling to change their certificate providers. Entrust is    currently used by sites such as MoneyGram and the US Department    of Energy, but unless Entrust can strike a deal with Google,    it's almost a sure thing that they'll be switching providers.    It's worth noting that Entrust is currently on Firefox's    list of trusted CAs, but given that Chrome controls over    65% of the browser market, Firefox's opinion on Entrust isn't    likely to move the needle.  <\/p>\n<p>    We have reached out to Google, Entrust, and Mozilla for comment    on this story and will update if they respond.  <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>Read more: <\/p>\n<p><a target=\"_blank\" rel=\"nofollow noopener\" href=\"https:\/\/www.androidpolice.com\/google-chrome-will-soon-flag-several-websites-for-invalid-certificates\/\" title=\"Google Chrome will soon flag several websites for invalid certificates - Android Police\">Google Chrome will soon flag several websites for invalid certificates - Android Police<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> Summary From the earliest days of computing, computer scientists have recognized the need for the secure transport of information. Early computer protocols like Telnet would broadcast information (like usernames and passwords) across the internet without encryption, making it visible to anyone who wanted to look.  <a href=\"https:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/google\/google-chrome-will-soon-flag-several-websites-for-invalid-certificates-android-police\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[345634],"tags":[],"class_list":["post-1126467","post","type-post","status-publish","format-standard","hentry","category-google"],"_links":{"self":[{"href":"https:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/wp-json\/wp\/v2\/posts\/1126467"}],"collection":[{"href":"https:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/wp-json\/wp\/v2\/comments?post=1126467"}],"version-history":[{"count":0,"href":"https:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/wp-json\/wp\/v2\/posts\/1126467\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/wp-json\/wp\/v2\/media?parent=1126467"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/wp-json\/wp\/v2\/categories?post=1126467"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.euvolution.com\/prometheism-transhumanism-posthumanism\/wp-json\/wp\/v2\/tags?post=1126467"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}