> On Apr 10, 2017, at 11:18 AM, Rich Shepard <rshep...@appl-ecosys.com> wrote:
> 
>   Installed here is chromium-54.0.2840.100, my backup browser when a server
> has issues with firefox. Recently I ran into a puzzling response by firefox
> when I tried to access my bank's web site. Because I received a solution to
> the firefox 'crash' page issue here I'm hopeful I'll get equally good advice
> on resolving the chromium issue.
> 
>   Using firefox (and opera in the past) I have no problems accessing my
> bank's web site using https. When I entered that URL in chromium it refused
> to load the site, turned 'https' red and put a slash through it, and told me
> it was so badly insecure (something about a SSL certificate) that it would
> not let me proceed. Really?
> 
>   I know little about chromium as it's used so infrequently. I've not found
> anything in the preferences/options that seem to address this issue. If you
> have ideas on how to fix this browser-specific problem please share them
> with me.
> 
> Rich

Chrome and chromium test for things like self-signed certificates, untrusted 
CAs, and other things. Here's one report:

https://www.scmagazineuk.com/google-creates-list-of-untrusted-certificate-authorities/article/530574/

Did you make a note of the specific error message?

David

--

David - Offbeat         http://pgp.mit.edu/
dafydd - Online         0xda3f18449337d6b5

----5----1----5----2----5----3----5----4----5----5----5----6----5----7--

The most dangerous phrase is, 'We've always done it this way.' –RADM Grace 
Hopper

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

_______________________________________________
PLUG mailing list
PLUG@lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Reply via email to