a few people have reported problems on Einstein as well.

yep, seems Einstein is affected on this host too :(
Well, I't try to extract new file from latest package then report.

---

Or maybe properly updated ca-bundle.crt is available somewhere?

The file already released in the hotfix v7.16.7 of BOINC is at

https://raw.githubusercontent.com/computezrmle/boinc/patch-1/curl/ca-bundle.crt

It's plaintext, so the easiest way of making it is to 'select all' on that RAW page, and paste it into an empty ca_bundle.crt (text) file.

But watch out for outdated OpenSSL library files, too. Ask separately if you fall foul of those.

a few people have reported problems on Einstein as well.

yep, seems Einstein is affected on this host too :(
Well, I't try to extract new file from latest package then report.

Try here https://github.com/BOINC/boinc/blob/master/curl/

---

NO

Try here [url]https://github.com/BOINC/boinc/blob/master/curl/ca-bundle.crt[/url]

That's the two-year-old one that caused all the trouble in the first place.

a few people have reported problems on Einstein as well.

yep, seems Einstein is affected on this host too :(
Well, I't try to extract new file from latest package then report.

Well, I'm not "expert helper", but dare to provide this link ;) :

https://github.com/BOINC/boinc/blob/master/curl/ca-bundle.crt

to updated certificate's bundle.

Replace old with new, and connection will be restored.

Thanks Keith for initial hint.

---

a few people have reported problems on Einstein as well.

yep, seems Einstein is affected on this host too :(
Well, I't try to extract new file from latest package then report.

Try here https://github.com/BOINC/boinc/blob/master/curl/ca-bundle.crt

Thanks! I was busy with extraction from exe but realised that taking from sources will be much easier (so came to same link :) )

---

NO

Try here [url]https://github.com/BOINC/boinc/blob/master/curl/ca-bundle.crt[/url]

That's the two-year-old one that caused all the trouble in the first place.

Richard, maybe it's updated already?
At least I experimentally confirmed - connection restored....

EDIT: though, actually I did it in little different way:
1) downloaded zipped source tree
2) extracted
3) found required file
4) came back to web-sources and found link to the same place as in ZIP.

---

Well, I't try to extract new file from latest package then report.

I'll save you the trouble: it'll fail.

Master has not yet been updated. There are two contenders for the honour:

https://github.com/BOINC/boinc/pull/3791 (good)
https://github.com/BOINC/boinc/pull/3802 (bad)

Well, I't try to extract new file from latest package then report.

I'll save you the trouble: it'll fail.

Master has not yet been updated. There are two contenders for the honour:

https://github.com/BOINC/boinc/pull/3791 (good)
https://github.com/BOINC/boinc/pull/3802 (bad)

Hm... at least Rosetta uploaded, downloaded and running again on this host.
I'm happy and can go back to my ignorance will feelings of completed job, LoL :)

(EDIT E@h project is happy too)

---

Richard, maybe it's updated already?

Check the dates, and read the comments I've put on #3802 this morning.

NO

Try here [url]https://github.com/BOINC/boinc/blob/master/curl/ca-bundle.crt[/url]

That's the two-year-old one that caused all the trouble in the first place.

Sorry, if that one is a problem, can it be removed as a download ? Or replaced with the latest correct version ?

---

Hm... at least Rosetta uploaded, downloaded and running again on this host.

Rosetta and LHC have done server-side updates. NumberFields, I suspect, is still broken and has lost a lot of computing power because of this foul-up. I seem to be doing mostly other people's cast-offs at the moment.

But watch out for outdated OpenSSL library files, too. Ask separately if you fall foul of those.

This issue stopped few my old Android hosts with NativeBOINC and w/o root rights :/
Still no progress there (and BOINC from Google Play doesn't support those devices either).

---

Hm... at least Rosetta uploaded, downloaded and running again on this host.

Rosetta and LHC have done server-side updates. NumberFields, I suspect, is still broken and has lost a lot of computing power because of this foul-up. I seem to be doing mostly other people's cast-offs at the moment.

I don't understand then... Before local file change host didn't able to connect to (updated?) Rosetta server. After I put 2years-old file in place - it can....

The single explanation I have - 2-years-old-files missed some junk that was added later...

---

Sorry, if that one is a problem, can it be removed as a download ? Or replaced with the latest correct version ?

To explain how GitHub works:

Normally, 'master' has the latest and greatest version. Access to master is controlled, peer-reviewed, and automatically tested - so usually, it's good.

But in this case, because of the urgency of the situation, the priority was to get out a quick'n'dirty fix. So, the best copy (currently) is actually in

https://github.com/BOINC/boinc/tree/client_release/7/7.16/curl (note the date and comment)

But it's slightly difficult to download a single file, so it's easier to make your own file from

https://raw.githubusercontent.com/BOINC/boinc/client_release/7/7.16/curl/ca-bundle.crt

The single explanation I have - 2-years-old-files missed some junk that was added later...

Yes, you were probably using a 6-years-old file... ;-)

The single explanation I have - 2-years-old-files missed some junk that was added later...

Yes, you were probably using a 6-years-old file... ;-)

:D :D :D
very probably :)

---

Sorry, if that one is a problem, can it be removed as a download ? Or replaced with the latest correct version ?

To explain how GitHub works:

Normally, 'master' has the latest and greatest version. Access to master is controlled, peer-reviewed, and automatically tested - so usually, it's good.

But in this case, because of the urgency of the situation, the priority was to get out a quick'n'dirty fix. So, the best copy (currently) is actually in

https://github.com/BOINC/boinc/tree/client_release/7/7.16/curl (note the date and comment)

But it's slightly difficult to download a single file, so it's easier to make your own file from

https://raw.githubusercontent.com/BOINC/boinc/client_release/7/7.16/curl/ca-bundle.crt

Thanks again Richard !

You are correct that I am a complete newbie at GitHub. I think my mistake was in assuming that something called Master would be the authoritative version !

---

I see it solved itself in the end, but can we please post with a certain level of respect to each other? The attacks, if you feel you need to do them, do so in private message, not in these threads.
Thank you.

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.

You forget that each and every one of us is also a volunteer, spending a lot of time and money on computers and electricity. This problem, which could have been avoided by someone remembering to update the certificate before it expired, would have saved 100s of 1000s of people a wasted afternoon, and saved the stopping of many important science projects. Perhaps the programmers could pay more attention in future.

---

Only people with OCD will care that this is a signature. Look up what the D means, it means you're broken.