Where is the continue anyway?

408 views
Skip to first unread message

J Decker

unread,
Mar 27, 2019, 1:04:51 AM3/27/19
to Chromium-discuss
image.png

jlm

unread,
Mar 27, 2019, 3:38:52 AM3/27/19
to Chromium-discuss
There is no continue. The message states that Chrome cannot open the page because the encryption is scrambled.  Fix the website and click reload.
 
On Wednesday, March 27, 2019 at 1:04:51 AM UTC-4, J Decker wrote:
image.png

PhistucK

unread,
Mar 27, 2019, 3:47:39 AM3/27/19
to J Decker, Ryan Sleevi, John L Magee, Chromium-discuss
If you know how to debug web stuff, check whether the response has the Strict-Transport-Security header.
If it does, the website asked the browser not to allow the user to see it if there is any security problem.
(Though the message usually tells that to the user, so it might not be it)

Adding Ryan (it would be great if you added someone else if this is not your area) -
While I appreciate the lengthy description in the screenshot, it would have been better if at least technical users could understand the exact problem (or something close to it), because using the word "credentials" is about as vague as one can get. ;)

PhistucK


--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

---
You received this message because you are subscribed to the Google Groups "Chromium-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discu...@chromium.org.

J Decker

unread,
Apr 7, 2019, 7:33:39 AM4/7/19
to PhistucK, Ryan Sleevi, John L Magee, Chromium-discuss
Ran into this issue again...


On Wed, Mar 27, 2019 at 12:47 AM PhistucK <phis...@gmail.com> wrote:
If you know how to debug web stuff, check whether the response has the Strict-Transport-Security header.
If it does, the website asked the browser not to allow the user to see it if there is any security problem.
(Though the message usually tells that to the user, so it might not be it)

There is no header like that.
After installing the root certificate I was able to connect....however, windows firewall is not able to service my testing needs, so I had to move to my linux box.... so I have a new root certificate;  This new root had the proper name 'd3x0r.org' in addition to the original names, and the https:// connection has no option to continue anyway.

On the webpage, I have a link to a batch file which will download and install the proper certificate... 

Normally, the single point of content service would be using a let's encrypt certificate... but I really just don't want to be bothered with those hoops for just testing.

PhistucK

unread,
Apr 7, 2019, 7:41:10 AM4/7/19
to J Decker, Ryan Sleevi, John L Magee, Chromium-discuss
If this is just for testing, you might be able to use a command line flag or its chrome:flags equivalent -
--unsafely-treat-insecure-origin-as-secure="https://your-domain.com"
chrome://flags/#unsafely-treat-insecure-origin-as-secure and https://your-domain.com

PhistucK

Reply all
Reply to author
Forward
0 new messages