When you open up Chrome’s DevTools and switch to the Security Tab you’ll see the message
This request does not comply with Chrome's Certificate Transparency policy. on some origins. (Example:
https://de.ioam.de when you visit
I know the concept of Certificate Transparency in general but I neither know what
Chrome's Certificate Transparency policy is nor do I know what the impact of this statement is.
Obviously Chrome establishes the https connection to this host, but what’s wrong here?
Will https connections to affected origins be blocked in the future?
Chrome’s password manager allows for users to view their saved passwords on passwords.google.com. The saved passwords can be viewed on different devices as long as the user logs into their Google account. So, these passwords must be stored in a Google database. Is it known as to whether the passwords are encrypted in this database, so that Google wouldn’t be able to know what your account passwords are?
What does clicking the word “
(change)” do, in the window the “Save to Google Drive” Extension (https://chrome.google.com/webstore/detail/save-to-google-drive/gmbmikajjgmnabiglmofipeabaddhgne) pops after every save for Google Chrome to Google Drive?
(https://drive.google.com/file/d/1Vn6mtk7JjThMmdRK-Gaj6nwX6Amna91y/view?usp=sharing is the version saved with said tool showing the unknown/unspecified word in question “
This has been a topic that's been ticking the back of my mind now for quite some time.
Amazon uses symantec cert for the product images that we show on our site.
And google is scheduled (April 17 Chrome update 66) to deem unsecure any site using Symantec certs issued before 2016.
So what will really happen when Chrome update 66 kicks in?
Has Amazon updated their certs? If so, why do we see the images-na.ssl-images-amazon warnings in our browser inspects?
And what exactly dose…
Thoughts on Chrome’s Plan to Distrust Symantec Certificates