I use the CURL library (libcurl on Mac) in my DAW plugins to connect with my server database for plugin registration. It works fine everywhere except for some Win 7 users who report "SSL Connection" error. There seems to be something missing, an old SSL protocol or something that prevents this CURL code from connecting in Win 7.
Win 7 is an old, unsupported OS and I don't want to spend a lot of time on this but if there is something I can do - a "switch" or something simple - that will get this working I will do it. Otherwise, I will specify "does not support Win 7".
Any input appreciated. Thank you!
What is Win 7 missing that causes connection errors with CURL?
-
- KVRAF
- 16795 posts since 8 Mar, 2005 from Utrecht, Holland
Win7 does not know about modern encryption algorithms and Certification Authorities, so it does not trust them. Back then, there were about 100 CAs (of which dozens aren't in business anymore), now 150 or so.
Either you disable certificate checks (options of libcurl, but not a good idea - you might as well use plain http instead of https) or you tell that customer to keep his outdated machine off the internet, with the consequence your stuff cannot be authorised.
We discussed this ten months ago already, I tested stuff for you and gave you this explanation already via email back then.
Either you disable certificate checks (options of libcurl, but not a good idea - you might as well use plain http instead of https) or you tell that customer to keep his outdated machine off the internet, with the consequence your stuff cannot be authorised.
We discussed this ten months ago already, I tested stuff for you and gave you this explanation already via email back then.
We are the KVR collective. Resistance is futile. You will be assimilated. 
My MusicCalc is served over https!!
My MusicCalc is served over https!!
-
- KVRist
- 218 posts since 6 Sep, 2015
Hi this is another alternative while still keeping everything secure. Might help for future projects as well.
When the user clicks register on your plugin open their default web browser directing them to your plugin registration page.
You then create a mini server in your plugin something like localhost:4005 on the background thread . Make sure it’s a unique port or not used to often for other purposes.
Once the user registers on your website and gets a response from your server you can send back the info to your plugin at: localhost:4005 with JavaScript in the browser
When the user clicks register on your plugin open their default web browser directing them to your plugin registration page.
You then create a mini server in your plugin something like localhost:4005 on the background thread . Make sure it’s a unique port or not used to often for other purposes.
Once the user registers on your website and gets a response from your server you can send back the info to your plugin at: localhost:4005 with JavaScript in the browser
-
- KVRian
- Topic Starter
- 641 posts since 30 Aug, 2012
Yes, thank you for reminding me and re-posting the explanation. The issue had not come up again until this week (it's rare) and I forgot about our previous discussion. Sorry, won't ask again!