| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Scheduler request failed: SSL connect error |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 110
|
|
| Author |
|
|
petehardy
Senior Cruncher USA Joined: May 4, 2007 Post Count: 318 Status: Offline Project Badges: 
|
My windows vista machine hasn't up or downloaded anything since at least july 20. Have work to upload but can't. Same machine is up/downloading seti and rosetta just fine. boinc ver 6.6.20  Why can't you update your Boinc?  "Patience is a virtue", I can't wait to learn it! |
||
|
|
metalius
Cruncher Lithuania Joined: Aug 19, 2014 Post Count: 31 Status: Offline Project Badges: 
|
Why can't you update your Boinc? You asked not me, but my answer is: "because the host is remote, far, very far away..." Also, I hate new versions of BOINC, because they are using so named "long term debt" and, of course, event log in a stupid separate window. To hell...  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I had the same problem connecting to localhost when started with BOINCPortable.exe. That is why I use boincmgr.exe. I had it from the start so it has nothing to do with "new" dlls (at least on my side). 0.9.8 is SSL that was "banned". Only SSL 1.0.1 and higher works now. Nothing was banned and only using the number for the OpenSSL is incorrect as well. There are four active OpenSSL versions: 0.9.8zg was released June 11, 2015 1.0.0s was released June 11, 2015 1.0.1p was released July 9th, 2015 1.0.2d was released July 9th, 2015 Major changes between OpenSSL 0.9.8n and OpenSSL 0.9.8o [1 Jun 2010]: Recognise SHA2 certificates if only SSL algorithms added. Major changes between OpenSSL 1.0.0d and OpenSSL 1.0.0e [6 Sep 2011]: Support ECDH ciphersuites for certificates using SHA2 algorithms. Nothing was banned. CA's are enforcing the use of more secure certificates and it just so happens that the OpenSSL version was distributed with earlier BOINC releases does not support them. OpenSSL doesn't know how to handle the newer certificates. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
My windows vista machine hasn't up or downloaded anything since at least july 20. Have work to upload but can't. Same machine is up/downloading seti and rosetta just fine. boinc ver 6.6.20 Well, WCG admins put the old certificate in place until July 20th. The old certificate expires today, so there is no putting it back. You have two options: 1) Upgrade the client 2) Don't upgrade the client There is a caveat to not upgrading though. While SETI and Rosetta work "just fine", that won't be that way. Their certificates will expire and they will put new certs in. When they do, your client will fail to connect there as well. CA's are not issuing the older certificates anymore; so all new and renewals will be with the better encryption. If you want to launch the event log, ctrl-shift-e and I find that it is easier as you can open it up and view the messages while you are elsewhere in BOINC. No need to switch windows. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Also, here are some articles in the sunsetting of SHA-1:
[url]https://www.symantec.com/page.jsp?id=sha2-transition[/url] [url]https://www.digicert.com/sha1-sunset/[/url] [url]https://en.wikipedia.org/wiki/SHA-1[/url] So, it is not that WCG decided to implment it, they were forced too. No major CA is issuing SHA-1 certs; doing so will just cause implementations problems as Chrome and Opera will show the site as a risk and any server running Windows won't take the cert. IIS accounts for 1/3 of the web servers out there. Mozilla will remove support for SHA-1 by 2017. The cert that SETI is currently using expires on April 13th, 2017. It is using SHA1 and they could rekey it at anytime to SHA2. |
||
|
|
Bensboy
Cruncher Joined: May 6, 2007 Post Count: 1 Status: Offline Project Badges: 
|
I have the same problem w/ windows and MacBook Pro.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
There's several ways of certificate use. Under some Linux [also a Unix derivative], the BOINC CA-bundle is not even used, rather the certs that come with the OS are.
----------------------------------------'I have the same problem' begs the question, what BOINC version are you using, and can you update to the recommended level of 7.2 per the WCG download [again] page. [Edit 1 times, last edit by Former Member at Jul 28, 2015 5:17:58 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
There's several ways of certificate use. Under some Linux [also a Unix derivative], the BOINC CA-bundle is not even used, rather the certs that come with the OS are. In Windows it appears that they are not using SSL support from the OS but it is all built-in to the BOINC client. I have a few old 2003 machines that I haven't patched in quite sometime since they are remote, behind an enterprise firewall and have very limited access out. The OS is not patched to support SHA2, and the 7.6 BOINC client can communicate just fine. When I finally replace them I'm going to VM them and I'll just have BOINC running on a dedicated VM. |
||
|
|
zuxy
Cruncher Joined: Jan 26, 2008 Post Count: 1 Status: Offline Project Badges: 
|
Why can't you update your Boinc? You asked not me, but my answer is: "because the host is remote, far, very far away..." Also, I hate new versions of BOINC, because they are using so named "long term debt" and, of course, event log in a stupid separate window. To hell... Yeah I hate the separate event log too. But in you situation, choices are not so many: 1) If your old BOINC binary is dynamically linked to OpenSSL, probably you can upgrade the OpenSSL library only; 2) Otherwise you have to rebuild from source, which I just did. |
||
|
|
metalius
Cruncher Lithuania Joined: Aug 19, 2014 Post Count: 31 Status: Offline Project Badges:
|
Yeah I hate the separate event log too. But in you situation, choices are not so many:... Zuxy, thank You for reply. I solved the problem in a lame but simple way: a phone call to my friend (very bad situation, but what to do?), TeamViewer, download BOINC, install... To hell, again. So, farewell BOINC 6.2.19! |
||
|
|
|