Skip to content
This repository has been archived by the owner on Mar 29, 2019. It is now read-only.

Problem with certificates on windows only? #1

Open
norbe opened this issue Jul 3, 2015 · 8 comments
Open

Problem with certificates on windows only? #1

norbe opened this issue Jul 3, 2015 · 8 comments

Comments

@norbe
Copy link

norbe commented Jul 3, 2015

Hi,

I just discover problem that on windows machines I'm not able to crawl some sites (for example http://ssl.heureka.cz/login-process/). Even when I use CurlCaBundle I still getting error SSL Certificate problem: Unable to get local issuer certificate.

The same domain is used for Heureka Kosik Api and it works ok (on production server).

When I use quite old crt file from http://filehostuk.com/downloads/cacert.rar it works ok (i found it thanx to this post). Do you have any idea why?

@fprochazka
Copy link
Member

Interesting, I'll try to upgrade the script, haven't done that in a while, maybe it will fix the problem.
Otherwise I think I'll have to setup testing, if the certificates work on buch of domains.

@fprochazka
Copy link
Member

I've already have to revert one cert for our usage https://github.com/Kdyby/CurlCaBundle/tree/with-old-cybertrust-root.
Maybe it's related to mozilla droping the "weak" certs? http://curl.haxx.se/docs/caextract.html

@fprochazka
Copy link
Member

https://www.ssllabs.com/ssltest/analyze.html?d=heureka.cz&latest "Certificate uses a weak signature. When renewing, ensure you upgrade to SHA2."

@norbe
Copy link
Author

norbe commented Jul 3, 2015

It's hard to say as I don't know how it is processed internally in curl. Is it possible that on linux it's enought that top level authority is trusted and on windows it requires all levels to be trusted?

When I compare ca-bundle.crt on my dev machine with that from production server, there is no change in "thawte" brand (and even if I replace my ca-bundle.crt with that from production it do not help)...

@fprochazka
Copy link
Member

I'm guessing the problem started with this commit, right? 50b9eef

@norbe
Copy link
Author

norbe commented Jul 3, 2015

Yes, when I try ca-bundle.crt before that commit, it works. After that it ends with SSL error...

@fprochazka
Copy link
Member

You can just lock on the previous tag v1.0.5 and it should work till we figure something out...
I'm guessing I could create another branch that would contain the weaker certs.

@norbe
Copy link
Author

norbe commented Jul 5, 2015

Ok, thanks

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants