As you are probably aware, Firefox 37 will be made publicly available tonight, with updates starting tomorrow morning. This release contains some features that are quite exciting. Let's jump in!
Desktop
Heartbeat. This new feature is going to be the most groundbreaking thing in a long time when it comes to better understanding our users. You can read more about it here, but basically this will allow us to be in constant contact with our real users, learning of their perception of Firefox, and at the same time helping those who need help find it, and those who love Firefox learn more about how they can share it with their friends and get more out of Firefox.
We are changing a bunch of things with TLS and SSL Support, which means that sites that use outdated or insecure versions of these protocols will break. Sites should be updating anyway, and users who are upset should contact the site admins.
Youtube now fully supports HTML5 playback, the first major step towards killing the Flash plugin.
Various performance improvements should improve the reliability and performance of this release.
Various changes for devs
Yandex is now the default search provider in Turkey, replacing Google. Google does not have a dominate position in Turkey and studies show that most Turkish users prefer Yandex to Google.
Mobile
We are duplicating the crypto changes on desktop, so expect similar breakages on Android.
Yandex is also the default on all Turkish installs of Firefox for Android
We are adding several new locales: Albanian [sq], Burmese [my], Lower Sorbian [dsb], Songhai [son], Upper Sorbian [hsb], Uzbek [uz]
Downloads should be much faster due to download backend rewrite.
Hello all!
As you are probably aware, Firefox 37 will be made publicly available tonight, with updates starting tomorrow morning. This release contains some features that are quite exciting. Let's jump in!
'''Desktop'''
* Heartbeat. This new feature is going to be the most groundbreaking thing in a long time when it comes to better understanding our users. You can read more about it [https://wiki.mozilla.org/Advocacy/heartbeat here], but basically this will allow us to be in constant contact with our real users, learning of their perception of Firefox, and at the same time helping those who need help find it, and those who love Firefox learn more about how they can share it with their friends and get more out of Firefox.
* We are changing a bunch of things with TLS and SSL Support, which means that sites that use outdated or insecure versions of these protocols will break. Sites should be updating anyway, and users who are upset should contact the site admins.
* Youtube now fully supports HTML5 playback, the first major step towards killing the Flash plugin.
* Various performance improvements should improve the reliability and performance of this release.
* Various changes for devs
* Yandex is now the default search provider in Turkey, replacing Google. Google does not have a dominate position in Turkey and studies show that most Turkish users prefer Yandex to Google.
'''Mobile'''
* We are duplicating the crypto changes on desktop, so expect similar breakages on Android.
* Yandex is also the default on all Turkish installs of Firefox for Android
* We are adding several new locales: Albanian [sq], Burmese [my], Lower Sorbian [dsb], Songhai [son], Upper Sorbian [hsb], Uzbek [uz]
* Downloads should be much faster due to download backend rewrite.
We are changing a bunch of things with TLS and SSL Support, which means that sites that use outdated or insecure versions of these protocols will break. Sites should be updating anyway, and users who are upset should contact the site admins.
Hello, in the Italian support forum we have plenty of messages from upset users complaining that they are no more able to log in, or simply view, websites that are usable with other browsers.
I think we should give them
an explanation of what is happening now, and why this didn't happen before
a workaround to revert back the browser behaviour, even if this would mean weakening the security - they do it at their own risk
''Tyler Downer [[#post-64737|said]]''
<blockquote>
* We are changing a bunch of things with TLS and SSL Support, which means that sites that use outdated or insecure versions of these protocols will break. Sites should be updating anyway, and users who are upset should contact the site admins.</blockquote>
Hello, in the Italian support forum we have plenty of messages from upset users complaining that they are no more able to log in, or simply view, websites that are usable with other browsers.
I think we should give them
* an explanation of what is happening now, and why this didn't happen before
* a workaround to revert back the browser behaviour, even if this would mean weakening the security - they do it at their own risk
* maybe an update of the SSL errors page: [["This Connection is Untrusted" error message appears - What to do]]
With the new TLS/SSL updates people are most likely to see the error on this newly updated page.
This is because TLS 1.0 is no longer considered secure and as such support for this protocol has been removed as of v37.0. Other browsers such as Chrome and and Internet Explorer will also be dropping support for this protocol in the near future.
Other potential issues due to the TLS/SSL updates in v37.0 are much less likely than this issue and should not result in the "This Connection is Untrusted" error. (If you are seeing an increase in this specific error though, then we should definitely take a closer look at the cause.)
''Underpass [[#post-64888|said]]''
<blockquote>
* maybe an update of the SSL errors page: [["This Connection is Untrusted" error message appears - What to do]]
</blockquote>
With the new TLS/SSL updates people are most likely to see the error on [[TLS Error Reports|this newly updated page]].
This is because TLS 1.0 is no longer considered secure and as such support for this protocol has been removed as of v37.0. Other browsers such as Chrome and and Internet Explorer will also be dropping support for this protocol in the near future.
Other potential issues due to the TLS/SSL updates in v37.0 are much less likely than this issue and should not result in the "This Connection is Untrusted" error. (If you are seeing an increase in this specific error though, then we should definitely take a closer look at the cause.)
If you clic on "Per accedere con smartcard" (i.e. "Log in with smartcard"), you get the "ssl_error_handshake_failure_alert" error. This is not the only website that gives this (and other similar) errors.
We know that this is not a Firefox error, but we would like to know what can we do to mitigate this (for example: is it possible to have a whitlist?).
For example: this is an institutional website (Ministry of Justice)
https://pst.giustizia.it/PST/authentication/it/pst_ar.wp
If you clic on "Per accedere con smartcard" (i.e. "Log in with smartcard"), you get the "ssl_error_handshake_failure_alert" error. This is not the only website that gives this (and other similar) errors.
We know that this is not a Firefox error, but we would like to know what can we do to mitigate this (for example: is it possible to have a whitlist?).
This is because TLS 1.0 is no longer considered secure and as such support for this protocol has been removed as of v37.0. Other browsers such as Chrome and and Internet Explorer will also be dropping support for this protocol in the near future.
Maybe it could be a good idea to also write that even competitors will be dropping support to the old TLS protocol.
P.S.
''Mark Schmidt [[#post-64889|said]]''
<blockquote>
This is because TLS 1.0 is no longer considered secure and as such support for this protocol has been removed as of v37.0. '''Other browsers such as Chrome and and Internet Explorer will also be dropping support for this protocol in the near future.'''
</blockquote>
Maybe it could be a good idea to also write that even competitors will be dropping support to the old TLS protocol.
Fixed | Google Maps may render incorrectly in some cases
Fixed | Stability fixes for select graphics hardware and feature sets
Fixed | Various security fixes
The release notes didn't reference the first two fixes but I found these related bugs:
Bug 1153381 - WebGL Google Maps rendering bugs with D3D11 ANGLE on GMA4500 comment 21:
Lawrence Mandel [:lmandel] (use needinfo) 2015-04-20 11:24:10 PDTRelnoted as "Google Maps may render incorrectly in some cases"
Bug 1151361 - 37.0.1 crashes on startup during gfxWindowsPlatform::InitD3D11Devices() when creating WARP device comment 42:
Lawrence Mandel [:lmandel] (use needinfo) 2015-04-20 11:30:30 PDTrelnoted as "Stability fixes for select graphics hardware and feature sets". Takes into account this bug, bug 1151721 and bug 1137716.
https://www.mozilla.org/en-US/firefox/37.0.2/releasenotes/
Fixed | Google Maps may render incorrectly in some cases
Fixed | Stability fixes for select graphics hardware and feature sets
Fixed | Various [https://www.mozilla.org/security/known-vulnerabilities/firefox/#firefox37.0.2 security fixes]
-----
The release notes didn't reference the first two fixes but I found these related bugs:
[https://bugzilla.mozilla.org/show_bug.cgi?id=1153381 Bug 1153381] - WebGL Google Maps rendering bugs with D3D11 ANGLE on GMA4500 [https://bugzilla.mozilla.org/show_bug.cgi?id=1153381#c21 comment 21]:
''Lawrence Mandel [:lmandel] (use needinfo) 2015-04-20 11:24:10 PDT''
''Relnoted as "Google Maps may render incorrectly in some cases"''
[https://bugzilla.mozilla.org/show_bug.cgi?id=1151361 Bug 1151361] - 37.0.1 crashes on startup during gfxWindowsPlatform::InitD3D11Devices() when creating WARP device [https://bugzilla.mozilla.org/show_bug.cgi?id=1151361#c42 comment 42]:
''Lawrence Mandel [:lmandel] (use needinfo) 2015-04-20 11:30:30 PDT''
''relnoted as "Stability fixes for select graphics hardware and feature sets". Takes into account this bug, [https://bugzilla.mozilla.org/show_bug.cgi?id=1151721 bug 1151721] and [https://bugzilla.mozilla.org/show_bug.cgi?id=1137716 bug 1137716].''
Just an FYI, we are seeing a spike in crashes caused by Trusteerraport. Any crash signature with "Messagepump" in the title is likely caused by trusteer. We've reached out to them, but in the meantime please have users disable or remove Trusteer if possible.
Just an FYI, we are seeing a spike in crashes caused by Trusteerraport. Any crash signature with "Messagepump" in the title is likely caused by trusteer. We've reached out to them, but in the meantime please have users disable or remove Trusteer if possible.
Just an FYI, we are seeing a spike in crashes caused by Trusteerraport. Any crash signature with "Messagepump" in the title is likely caused by trusteer. We've reached out to them, but in the meantime please have users disable or remove Trusteer if possible.
Windows users: Click Start > All Programs > Trusteer Endpoint Protection > Stop Trusteer Endpoint Protection.
Mac users: On the Apple menu, click System Preferences. In the Other category, click Trusteer Endpoint Protection, and then click Stop Trusteer Endpoint Protection
P.S. Bug 1159484 - Firefox 37.0.2 crashes with Trusteer Rapport
''Tyler Downer [[#post-64990|said]]''
<blockquote>
Just an FYI, we are seeing a spike in crashes caused by Trusteerraport. Any crash signature with "Messagepump" in the title is likely caused by trusteer. We've reached out to them, but in the meantime please have users disable or remove Trusteer if possible.
</blockquote>
Instructions to disable [http://www-03.ibm.com/software/products/en/trusteer-rapport Trusteer Rapport]:
'''Windows users: '''Click Start > All Programs > Trusteer Endpoint Protection > Stop Trusteer Endpoint Protection.
'''Mac users:''' On the Apple menu, click System Preferences. In the Other category, click Trusteer Endpoint Protection, and then click Stop Trusteer Endpoint Protection
Ref:
*http://trusteer.force.com/PKB/articles/en_US/FAQ/Browser-wont-start
*http://trusteer.force.com/PKB/articles/FAQ/browser-crashes
P.S. ''[https://bugzilla.mozilla.org/show_bug.cgi?id=1159484 Bug 1159484] - Firefox 37.0.2 crashes with Trusteer Rapport''
