Does anyone know the rationale for doing so? It's made trying to figure out what the connection is using into a multi-step pain now.
Does anyone know the rationale for doing so? It's made trying to figure out what the connection is using into a multi-step pain now.
https://bugs.chromium.org/p/chromium/issues/detail?id=646465
https://bugs.chromium.org/p/chromium/issues/detail?id=663971
I have no idea about the rationale but here's where SSL details reside now... it's insane what they have done:
>First, get into Developer tools. You can do this via Chrome’s upper-right three vertical dots, then click “More tools” — then “Developer tools” — or on many systems you can just press the F12 button.
>But wait, there’s still more (yeah, Google took a simple click in an intuitive place and replaced it with a bunch of clicks scattered around).
>Once the panel opens, look up at its top. If you don’t see the word “Security” already, click on the “>>” to the right of “Console” — then look down the list that appears and click on “Security” — which will open the Security panel with all of the certificate-related goodies. When you’re done there, click the big “X” in the upper right of the panel to return to normal browser operations.
https://lauren.vortex.com/2017/01/28/heres-where-google-hid-...
>Click on the Secure/Not Secure/(i) page info button.
>Click "Details" to go straight to the Security panel of the Developer Tools