SSL warning returns after browser restart #94

Closed
zeke opened this Issue Jan 18, 2013 · 11 comments

8 participants

@zeke

All is well when I "Proceed Anyway" -- until I restart Chrome. Then the warning comes back.

http://cl.ly/image/0G3J121I452a

@fklingler

👍

@fuadsaud

This is not a dotjs problem.

http://superuser.com/questions/27268/how-do-i-disable-the-warning-chrome-gives-if-a-security-certificate-is-not-trust

However, I think it should be mentioned on the README.

@fklingler

Thanks for the link.

Did you manage to make this work?
I added the certificate, but now it says that the certificate does not match the URL :-/

@fuadsaud

@fklingler Sadly no. Not with Google Chrome. Safari works fine after restarting it.

@fklingler

@fuadsaud Maybe we could recreate the server certificate to set the URL as localhost, I don't know if it's really the problem?

@zeke

@defunkt thoughts?

@dismory

Same problem.

@brunoarueira

👍 I had this error too!

@tekkub

I tried manually installing the cert, but this is the error I get:

You attempted to reach localhost, but instead you actually reached a server
identifying itself  as . This may be caused by a misconfiguration on the server
or by something more serious. An attacker on your network could be trying to get
you to visit a fake (and potentially harmful) version of localhost.

Sounds like the dotjs server isn't identifying itself correctly as localhost, so Chrome still thinks the cert doesn't match.

@burkemw3

I took a stab in the dark and figured out a workaround for this.

I told the server to identify itself has localhost, instead of whatever WEBrick thinks it should be called: burkemw3@3e74065. Then, I used Rob Peck's directions to trust the cert.

I am not submitting a pull request at this time because I have not done any due diligence investigating SSLCertName or WEBrick::Utils::getservername.

I was experiencing this issue today with djsd v2.0.0 from b8b545d and extension v2.0.1 from the Chrome Web Store.

@defunkt
Owner

works now

@defunkt defunkt closed this Jun 15, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment