Notices are not for user attention, or things the user needs to change or adjust. They're for news and other non-intrusive messages. No action needed things.

But we could have taken action, by adjusting our certificates file to do their job for them.

---

No connections to projects because of this issue.
Well, seems BOINC doesn't need my computing power anymore, ok.

EDIT: BTW, why nothing in BOINC notices about this issue?
They so verbose with different junk, but when REALLY user attention required they are silent! WTF!

Are you still having problems with this on any projects ?

LHC has updated the server https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=5441&postid=42767#42767
Rosetta has also fixed the issue https://boinc.bakerlab.org/rosetta/forum_thread.php?id=14006
I'm only aware of one other affected project. https://numberfields.asu.edu/NumberFields/forum_thread.php?id=460

Are there still any projects that are having problems ?

The Windows Boinc version update (and the temporary fix) sorted LHC and Rosetta here. LHC's own fix sorted my Androids (the Android update didn't help).

---

And yet didn't sort it before that date. Utter incompetance. Somebody should have written the expiry date on a calendar for goodness sake. If Boinc was a private company, somebody would now be fired.

Did I hear you volunteering to contribute? Thought not.

When a program is written and maintained by volunteers, accusations of incompetence etc are unlikely to produce any change.

And yet didn't sort it before that date. Utter incompetance. Somebody should have written the expiry date on a calendar for goodness sake. If Boinc was a private company, somebody would now be fired.

Did I hear you volunteering to contribute? Thought not.

When a program is written and maintained by volunteers, accusations of incompetence etc are unlikely to produce any change.

I'm not a programmer. I do my job and expect everyone else to do theirs. So, what was the reason for forgetting this important date? It's not rocket science to mark a date on a calendar.

And I don't expect change, I expect it to be held together on a shoe string forever more. But if they want the system to work, they need to pull their fingers out.

---

I'm still having problems with Einstein@home. Both with Linux and Windows machines...
I've read most of the thread, but where are the ca-certificate files hidden ? Before I can update them I need to find them....

T.A..

I'm still having problems with Einstein@home. Both with Linux and Windows machines...
I've read most of the thread, but where are the ca-certificate files hidden ? Before I can update them I need to find them....

T.A..

On Windows, it's C:\Program Files\BOINC\ca-bundle.crt

I don't know about Linux as I've not used it (yet)

---

Problem solved !!!
Thanks to Toby Broom and his replacement file, and a facepalm for not realising where the the thing was hidden in the first place..... :(
Regards
T.A.

In Linux it was in my /home/*user*/BOINC directory.....

T.A.

It was just BOINC that was caught out.

https://nakedsecurity.sophos.com/2020/06/02/the-mystery-of-the-expiring-sectigo-web-certificate/

Are you still having problems with this on any projects ?

Are there still any projects that are having problems ?

Yes, still can't upload/download from/to Rosetta

https://clip2net.com/s/47RTSv7

---

And yet didn't sort it before that date. Utter incompetance. Somebody should have written the expiry date on a calendar for goodness sake. If Boinc was a private company, somebody would now be fired.

Did I hear you volunteering to contribute? Thought not.

When a program is written and maintained by volunteers, accusations of incompetence etc are unlikely to produce any change.

LoL, volunteer just mean "no pay", it doesn't change competence/incompetence status. At all.
Shit happens, but better not in SUCH degree.
(In defense of Berkeley though I could say that it's not the single big university that forgot about expiration dates. Once we lost whole domain name because of expiration of DNS registration :))))) )

EDIT: And I would appreciate concise instructions what to do on my end to solve incompetence (yes, lets call things by their names) on server-end.
And preferably no-BOINC-version-update fix, cause I'm fully aware how many issues I potentially would have changing from checked-to-be-stable to "recommended" one...

---

Are you still having problems with this on any projects ?

Are there still any projects that are having problems ?

Yes, still can't upload/download from/to Rosetta

https://clip2net.com/s/47RTSv7

Is this on Android, or other OS ?
If Android, which version of the BOINC app ?

And yet didn't sort it before that date. Utter incompetance. Somebody should have written the expiry date on a calendar for goodness sake. If Boinc was a private company, somebody would now be fired.

Did I hear you volunteering to contribute? Thought not.

When a program is written and maintained by volunteers, accusations of incompetence etc are unlikely to produce any change.

LoL, volunteer just mean "no pay", it doesn't change competence/incompetence status. At all.
Shit happens, but better not in SUCH degree.

EDIT: And I would appreciate concise instructions what to do on my end to solve incompetence (yes, lets call things by their names) on server-end.
And preferably no-BOINC-version-update fix, cause I'm fully aware how many issues I potentially would have changing from checked-to-be-stable to "recommended" one...

Might I suggest that with your attitude your best fix is to turn your computers off.

Why should the volunteers give up their time to give you concise instructions to do a job that no longer needs doing for those who’ve accepted the updated software that you so insultingly refuse to run.

Might I suggest that with your attitude your best fix is to turn your computers off.

Why should the volunteers give up their time to give you concise instructions to do a job that no longer needs doing for those who’ve accepted the updated software that you so insultingly refuse to run.

Nope, you may not :)

(Learn what cause issue, learn how it connected with executable if connected at all then rant about my attitude)

---

Are you still having problems with this on any projects ?

Are there still any projects that are having problems ?

Yes, still can't upload/download from/to Rosetta

https://clip2net.com/s/47RTSv7

Is this on Android, or other OS ?
If Android, which version of the BOINC app ?

Vista, BOINC 7.4.42

---

Are you still having problems with this on any projects ?

Are there still any projects that are having problems ?

Yes, still can't upload/download from/to Rosetta

https://clip2net.com/s/47RTSv7

Is this on Android, or other OS ?
If Android, which version of the BOINC app ?

Vista, BOINC 7.4.42

I found your Rosetta hosts https://boinc.bakerlab.org/rosetta/hosts_user.php?userid=2135309

Have you tried editing the ca-bundle.crt file ? https://boinc.bakerlab.org/rosetta/forum_thread.php?id=14006&postid=96882#96882

Have you tried editing the ca-bundle.crt file ? https://boinc.bakerlab.org/rosetta/forum_thread.php?id=14006&postid=96882#96882

Thanks for link.

Unfortunately, seems it's not enough in my case:

05/06/2020 13:46:45 | Rosetta@home | [http] [ID#18] Info: Connected to boinc.bakerlab.org (128.95.160.157) port 443 (#25)
05/06/2020 13:46:45 | Rosetta@home | [http] [ID#18] Info: successfully set certificate verify locations:
05/06/2020 13:46:45 | Rosetta@home | [http] [ID#18] Info: CAfile: P:\bin\BOINC\ca-bundle.crt
05/06/2020 13:46:45 | Rosetta@home | [http] [ID#18] Info: CApath: none
05/06/2020 13:46:45 | Rosetta@home | [http] [ID#18] Info: SSLv3, TLS handshake, Client hello (1):
05/06/2020 13:46:45 | Rosetta@home | [http] [ID#19] Info: Connected to boinc.bakerlab.org (128.95.160.157) port 443 (#26)
05/06/2020 13:46:45 | Rosetta@home | [http] [ID#19] Info: successfully set certificate verify locations:
05/06/2020 13:46:45 | Rosetta@home | [http] [ID#19] Info: CAfile: P:\bin\BOINC\ca-bundle.crt
05/06/2020 13:46:45 | Rosetta@home | [http] [ID#19] Info: CApath: none
05/06/2020 13:46:45 | Rosetta@home | [http] [ID#19] Info: SSLv3, TLS handshake, Client hello (1):
05/06/2020 13:46:45 | Rosetta@home | [http] [ID#18] Info: SSLv3, TLS handshake, Server hello (2):
05/06/2020 13:46:45 | Rosetta@home | [http] [ID#18] Info: SSLv3, TLS handshake, CERT (11):
05/06/2020 13:46:45 | Rosetta@home | [http] [ID#18] Info: SSLv3, TLS alert, Server hello (2):
05/06/2020 13:46:45 | Rosetta@home | [http] [ID#18] Info: SSL certificate problem: unable to get local issuer certificate
05/06/2020 13:46:45 | Rosetta@home | [http] [ID#18] Info: Closing connection 25
05/06/2020 13:46:45 | Rosetta@home | [http] HTTP error: Peer certificate cannot be authenticated with given CA certificates
05/06/2020 13:46:45 | Rosetta@home | [http] [ID#19] Info: SSLv3, TLS handshake, Server hello (2):
05/06/2020 13:46:45 | Rosetta@home | [http] [ID#19] Info: SSLv3, TLS handshake, CERT (11):
05/06/2020 13:46:45 | Rosetta@home | [http] [ID#19] Info: SSLv3, TLS alert, Server hello (2):
05/06/2020 13:46:45 | Rosetta@home | [http] [ID#19] Info: SSL certificate problem: unable to get local issuer certificate
05/06/2020 13:46:45 | Rosetta@home | [http] [ID#19] Info: Closing connection 26
05/06/2020 13:46:45 | Rosetta@home | [http] HTTP error: Peer certificate cannot be authenticated with given CA certificates

I see few other entries from AddTrust there, maybe they should be deleted too?
Or maybe properly updated ca-bundle.crt is available somewhere?

---

Might I suggest that with your attitude your best fix is to turn your computers off.

Why should the volunteers give up their time to give you concise instructions to do a job that no longer needs doing for those who’ve accepted the updated software that you so insultingly refuse to run.

Nope, you may not :)

(Learn what cause issue, learn how it connected with executable if connected at all then rant about my attitude)

I know exactly what caused the problem and I know, even if you don’t, where the line is between legitimate complaint and out and out ignorance. You sir, have crossed that line.

There is more information in https://boinc.bakerlab.org/rosetta/forum_thread.php?id=14006

I only had this problem on LHC, both Windows and Android

The expired certificate problem has affected at least 3 projects, Rosetta, LHC and Number Fields, a few people have reported problems on Einstein as well.

There is an updated version of ca-bundle.crt available, but I'm not sure where to download the latest version.

---

You sir, have crossed that line.

Very helpful statement from Эксперт-помощник (expert helper, right :) ) I'm here little longer it seems and know what new executable could do, so call it as you wish, but if issue can be fixed w/o executable change I still prefer to fix it w/o changing executable. And I'm not "sir", I'm товарищ :D (joke ;) )

---