| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 2
|
|
| Author |
|
|
Jord
Advanced Cruncher Joined: Dec 30, 2005 Post Count: 148 Status: Offline Project Badges:
|
Is this of any consequence to the CA certificate in the client and/or server software/forums?
----------------------------------------https://googleonlinesecurity.blogspot.nl/2015...-measures-in-digital.html Over the course of the coming weeks, Google will be moving to distrust the “Class 3 Public Primary CA” root certificate operated by Symantec Corporation, across Chrome, Android, and Google products. We are taking this action in response to a notification by Symantec Corporation that, as of December 1, 2015, Symantec has decided that this root will no longer comply with the CA/Browser Forum’s Baseline Requirements. As these requirements reflect industry best practice and are the foundation for publicly trusted certificates, the failure to comply with these represents an unacceptable risk to users of Google products. This certificate is also known under the old Verisign name.
Tears in my eyes
How they fall like rain to the floor |
||
|
|
Jord
Advanced Cruncher Joined: Dec 30, 2005 Post Count: 148 Status: Offline Project Badges:
|
Rom Walton says:
----------------------------------------We are using a Comodo cert for code-signing on Windows these days. As far as BOINC as a whole, we probably just need to send out an advisory to boinc_projects. I’ll remove the cert from the ca-bundle.crt file, but it’ll only effect new client releases. ----- Rom
Tears in my eyes
How they fall like rain to the floor |
||
|
|
|