google https problem due to firefox lag?

[tuxcoder]

On two different ALARM systems (both armv7h), my upgrade today to ca-certificates-mozilla-3.28.1-1 seems to have led to problems with Firefox accepting the certificate from google.com. The aforementioned package became available yesterday (Jan 28 UTC), and the currently available Firefox package is 50.1.0-1 (Dec 14 UTC).

Mainline Arch has Firefox 51.0.1-1 from just a couple days ago. Could the new ca-certificates-mozilla package be causing the problem with the older Firefox? To test that, I've downgraded the certificates to 3.27.2-1, then further down to 3.27.1-1. Oddly, the problem persisted. I tested what's effectively this scenario on one of the ALARM systems prior to its upgrade to 3.28.1-1, and there was no problem.

Finally, a mainline Arch x86_64 system that is currently fully upgraded has no issues with google.com.

Is anyone else seeing this?

[tuxcoder]

By the way, the exact error reported is "the website tried to negotiate an inadequate level of security" aka NS_ERROR_NET_INADEQUATE_SECURITY.

[tuxcoder]

Nobody else has seen this issue?

I'm not good at diagnosing HTTPS issues, so alternatively, does anyone have any suggestions of things I could try to further narrow down the problem?

[BetaPictoris]

Put "network.http.spdy.enforce-tls-profile" to "false" in your about:config
And look at this: https://bugzilla.mozilla.org/show_bug.cgi?id=1323209

[tuxcoder]

Thank you very much, BetaPictoris, after reading that bug report, that sounds exactly like what I'm seeing. I'll have to try it out later today.

Now, where have they put that Firefox 51 ALARM package? (Thank you for all your hard work, ALARM maintainers!)

[BetaPictoris]

Perhaps the maintainers have forgotten to upload it on repo , or they encounter problems to compile it.
I have, also, tried to compile it from its pkgbuilds, but without success for the moment.