[Cialug] Chrome 63.x

[Dave Hala]

What's really interesting about this, is that I downgraded and then renamed
the ChromeUpdate.exe so that it wouldn't update.   It would appear that
Chrome  fixed the updater that I intentionally broke, updated itself and
now it I'm not having the issue... which is really strange, if not a bit
scary.   I poked around in the Chrome change logs and didn't see anything
related to this.    Its a mystery.

:) Dave


On Thu, Dec 21, 2017 at 3:01 PM, Scott Yates <Scott at yatesframe.com> wrote:

> Are you sure there is no option to proceed past the ssl issue?  I am on the
> latest version as well, and i can still continue on as before.  Could there
> be a config option that got set on yours that is preventing that?
>
> On Thu, Dec 21, 2017 at 2:58 PM, Tim Champion <timchampion at gmail.com>
> wrote:
>
> > How about using a free SSL cert that chrome will be happy with?
> >
> > https://letsencrypt.org/
> >
> > Tim Champion
> > timchampion at gmail.com
> >
> > On Tue, Dec 19, 2017 at 9:20 AM, Josh More <jmore at starmind.org> wrote:
> >
> > > Try mysite-dev.foo
> > >
> > > Wildcards are only intended to match one level of subdomains (though
> > > enforcement of this has been lax).
> > >
> > > -Josh More
> > >
> > > On Dec 19, 2017 08:18, "Dave Hala" <dave at 58ghz.net> wrote:
> > >
> > > > mysite.dev.foo    So... *.foo should be ok.   Just to be sure Chrome
> > > wasn't
> > > > doing something funky, I changed it to mysite.home.foo and it didn't
> > make
> > > > any difference.
> > > >
> > > >
> > > >
> > > > On Tue, Dec 19, 2017 at 9:14 AM, Adam Hill <adam at diginc.us> wrote:
> > > >
> > > > > 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
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > 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
> > >
> > _______________________________________________
> > 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
>



-- 
NIFCAP  -The Premier Client Intake System for Non-Profit Organizations.