Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle SSL warnings #58

Closed
divico opened this issue Sep 5, 2016 · 3 comments
Closed

Handle SSL warnings #58

divico opened this issue Sep 5, 2016 · 3 comments
Assignees
Milestone

Comments

@divico
Copy link

divico commented Sep 5, 2016

Brief description of the issue.

rssguard version 3.3.4 will not connect to an owncloud news instance in case of SSL warnings.
My owncloud server supplies a SSL certificate issued for a different hostname. Therefore hostname verification is not possible. In this case, rssguard will not connect to the owncloud instance.

How to reproduce the bug?

Connect to an owncloud news instance that supplies a SSL certificate whose hostname cannot be verified.

What is the expected result?

Ask the user if he accepts the security exception and connect to the owncloud instance.

What actually happened?

On connection the following error is raised
WARNING: Ignoring SSL errors for 'https://xxxx/index.php/apps/news/api/v1-2/status': 'Unknown error' (code 0). WARNING: QIODevice::read (QNetworkReplyHttpImpl): device not open DEBUG: Destroying SilentNetworkAccessManager instance. WARNING: ownCloud: Obtaining status info failed with error 5.

I can provide access to the server if needed.

@martinrotter
Copy link
Owner

Hello. Yes, please provide demo account on your server, I will test it out and fix if possible.

Does this happen on Windows? Linux?

@martinrotter martinrotter added this to the 3.3.5 milestone Sep 6, 2016
@martinrotter martinrotter self-assigned this Sep 6, 2016
@martinrotter
Copy link
Owner

Follow-up: did it work with previous RSS Guard version?

@divico
Copy link
Author

divico commented Sep 6, 2016

Today it works perfectly so it must be an issue from the server. I'm sorry for having opened this issue!

@divico divico closed this as completed Sep 6, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants