Web site access and Firefox 60.0b4
17 Mar 2018 6:42:24 UTC
Topic 214029
(moderation:
FYI
Firefox has started complaining since last update. Used Chrome to post this as cannot find a way to ignore the warning.
--------------------------------------------------------------------------------------------------------------------------------------
einsteinathome.org uses an invalid security certificate. The certificate is not trusted because the issuer certificate is unknown. The server might not be sending the appropriate intermediate certificates. An additional root certificate may need to be imported. Error code: SEC_ERROR_UNKNOWN_ISSUER
https://einsteinathome.org/account/dashboard
Peer’s Certificate issuer is not recognized.
HTTP Strict Transport Security: true HTTP Public Key Pinning: false
---------------------------------------------------------------------------------------------------------------------------------------
Cheers!
I reported this to
)
I reported this to Firefox.
Cheers!!
poppageek wrote:FYI Firefox
)
I believe the problem is due to Google distrusting Symantec. https://security.googleblog.com/2017/09/chromes-plan-to-distrust-symantec.html. Mozilla is following Google in distrusting the same Web certificates.
We are aware of this problem and actively trying to solve it. Unfortunately it is complicated by the fact that a number of users have installed an older BOINC client, where the new certificates, which don't give this error, will not work.
PS- contacting Mozilla (Firefox) may not help. The problem is project/server-side.
Einstein@Home Project
When chrome 66 will be
)
When chrome 66 will be released (17. Apr) people won't be able to access einsteinathome.org anymore.
https://knowledge.rapidssl.com/support/ssl-certificate-support/index?page=content&id=ALERT2566&actp=LIST&viewlocale=en_US
Stef_5 wrote:When chrome 66
)
Thanks, we are aware of this and have posted a News item about it. We plan to update our certificate April 16.
Einstein@Home Project
Shawn Kwang wrote:...
)
How old is "older BOINC client"? I'm deploying the new bundle to a bunch of hosts with 7.2.42 clients (Linux). Is that going to be a version that "will not work"?
Thanks for any response about this.
Cheers,
Gary.
Gary Roberts wrote:How old
)
Gary,
I think you asked this in the News thread, but I'll answer it here too. It's my understanding that Linux clients running v 7.2 and older should still work. This is because Linux BOINC clients should use the system's CA bundle installed by the Linux distribution. I say should because there are always exceptions.
It's mainly Windows and MacOS older BOINC clients that use the CA bundle. Again this is a blanket statement and the one thing I've learned in this work is that exceptions abound.
It's like spelling in English: 'i' before 'e' except after 'c', or when the 'i' just feels like going first because it wants to: (science, laciest), or they switch positions because they can (foreign, weird).
Einstein@Home Project