Skip to content

Conversation

@Nanoatic
Copy link

@Nanoatic Nanoatic commented Sep 7, 2018

Fix for self signed certificates.

Fix for **self signed certificates**.
@Nanoatic Nanoatic changed the title Update webview.cpp Web view Fix for Self Signed Certificates Sep 7, 2018

bool WebEnginePage::certificateError(const QWebEngineCertificateError &certificateError) {
//handle webview certificate errors here
return true;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please, fix the indentation.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This means we just accept all self signed certificates right?

Copy link
Author

@Nanoatic Nanoatic Sep 7, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

certificates are already accepted or rejected at the setup page.

indentation fixed.
@wdehoog
Copy link

wdehoog commented Sep 7, 2018

If the WebView does not have certificates (in the setup wizard). This will probably not help.


bool WebEnginePage::certificateError(const QWebEngineCertificateError &certificateError) {
//handle webview certificate errors here
return true;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok so after looking it up. really fixing it is not so straight forward as the webengineview uses it own network stack. So no QNAM etc.

What we could do. Is pass in the original URL we try to connect to. As we have to accept that cert before continuing.

If the url matches the cert here. Then we continue. Else we should still fail.

How does that sound?

@rullzer
Copy link
Member

rullzer commented Oct 30, 2018

See #758

@rullzer rullzer closed this Oct 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants