search

blueclosure / BCDetect

5 stars 0 forks source link

v1.03 error - This page is insecure (broken HTTPS). #5

Closed wisec closed 8 years ago

wisec commented 8 years ago

On behalf of a BCDetect user:

Suddenly after upgrading from 1.01 to 1.03 I get cert errors. It seems Chrome does not trust the Node MITM. OS: Windows 8.1 Pro Chrome V: 53.0.2785.143

wisec commented 8 years ago

There are two chances:

1) If user can still to navigate then is an expected behavior. The reason is that to avoid proxy certificate issues we add --ignore-certificate-errors to Chrome.

The other option would be to add the proxy CA to Chrome, but then it would be present to every other Chrome profile (that is how Chrome certification management works that is globally on your User system environment).

So if you see something like: image it is expected.

2) If, on the other hand, the user sees a full page error about insecure certificate then it's a bug that must be fixed.

wisec commented 8 years ago

Closing this as it resulted as case 1).