[Cialug] Fwd: Chrome 63.x

[Jimmy Lela]

Try typing "badidea" (without the quotes) at the cert error page.  Maybe
they just took away the clicky method of proceeding but left this option.

---------- Forwarded message ----------
From: Adam Hill <adam at diginc.us>
Date: Tue, Dec 19, 2017 at 9:14 AM
Subject: Re: [Cialug] Chrome 63.x
To: Central Iowa Linux Users Group <cialug at cialug.org>


What is the top level domain?

https://ma.ttias.be/chrome-force-dev-domains-https-via-preloaded-hsts/

On Tue, Dec 19, 2017 at 8:43 AM Dave Hala <dave at 58ghz.net> wrote:

> This morning Google Chrome (on windows) updated to version 63.x.
>
> My php development workstation is a linux vm and apache uses a self-signed
> certificate.  Chrome 63.x is having no part of it, generating invalid
> certificate errors. This new version has eliminated the option to proceed.
>
> Other than getting a valid certificate, anyone know a way around this? For
> the interim, I down graded to chrome 62.x and then renamed the .exe
> GoogleUpdate.exe to GoogeUpdate.disabled.exe so that Chrome won't auto
> update.
>
> :) Dave
>
> --
> NIFCAP  -The Premier Client Intake System for Non-Profit Organizations.
> _______________________________________________
> Cialug mailing list
> Cialug at cialug.org
> http://cialug.org/mailman/listinfo/cialug
>
_______________________________________________
Cialug mailing list
Cialug at cialug.org
http://cialug.org/mailman/listinfo/cialug



-- 
"Can you jam with the console cowboys in cyberspace?"