BOINC communications failure

10 views
Skip to first unread message

Richard Haselgrove

unread,
Oct 1, 2021, 12:24:59 PM10/1/21
to boinc...@googlegroups.com

It's now over 24 hours since the first public report that multiple BOINC projects were losing contact with their scientific volunteer collaborators.


The problem turned out to be an expired certificate in the client security bundle - a bundle which was last updated on 31 May 2020, following a similar unexpected expiry.


Not one single member of the project management team has posted one single word about the outage.


The problem affects the Windows client, so the remedy will require action by somebody with authorisation to use the UCB software licence (InstallShield), and the UCB code-signing machine.


Does anybody know whether David Anderson is available at the moment? Failing that, does anybody know who would be assigned to deputise for him in his absence?

Vitalii Koshura

unread,
Oct 1, 2021, 12:39:17 PM10/1/21
to Richard Haselgrove, boinc...@googlegroups.com
It is not only installshield license.
New version of software should be built too to update the version.
Also certificate is required to sign executables and installer.

Пт, 1 окт. 2021 г. в 18:24, 'Richard Haselgrove' via boinc_admin <boinc...@googlegroups.com>:
--
You received this message because you are subscribed to the Google Groups "boinc_admin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to boinc_admin...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/boinc_admin/5a79821d.6859e.17c3cac5008.Webtop.93%40btinternet.com.
--
Best regards,
Vitalii Koshura

Sent via iPhone

Matthew Blumberg

unread,
Oct 1, 2021, 12:55:10 PM10/1/21
to Vitalii Koshura, Richard Haselgrove, boinc_admin
My understanding is that a client update will be useful to preempt similar/related issues in the future. 
But that a server-side fix was proposed in the Github thread yesterday, by Nicholas Alvarez.
I know Rytis and Tristan are working on testing/validating that fix; possibly Nicholas and others are too.
-- I assume further discussion of specifics will carry on in the GitHub thread (Issue #4530)


Reply all
Reply to author
Forward
0 new messages