Mozilla sent Firefox Version 32.0 to the release channel. The update includes three (3) Critical, one (1) High and one (1) Moderate security updates.
Finally fixed is the text rendering issue that was introduced with version 29.1. Information about the addition of Public Key Pining is available in this Mozilla post, Firefox 32 supports Public Key Pinning (http://monica-at-mozilla.blogspot.de/2014/08/firefox-32-supports-public-key-pinning.html).
Mozilla Firefox Release Notes (https://www.mozilla.org/en-US/firefox/32.0/releasenotes/)
Security Updates (https://www.mozilla.org/security/known-vulnerabilities/firefox.html)
Running now without issue. As a side-note Australis Theme Restorer (Customize Australis) is at version 1.2.4 but not approved by AMO.
AMO being Add-ons Mozilla.
https://addons.mozilla.org/en-US/firefox/addon/classicthemerestorer/versions/?page=1#version-1.2.4
More on Public Key Pinning (https://wiki.mozilla.org/SecurityEngineering/Public_Key_Pinning)
good and nice to know all this..
thank you all :hammy:
Firefox 32.0.1 (12 September 2014)
What's New
Fixed
32.0.1 - Start-up crash when using switchable Intel+ATI graphics cards
Fixed
32.0.1 - Mixed content icon may be incorrectly displayed instead of lock icon for SSL sites
Fixed
32.0.1 - WebRTC: setRemoteDescription() silently fails if no success callback is specified
Release Notes (https://www.mozilla.org/en-US/firefox/32.0.1/releasenotes/) Not yet noted in Mozilla MFSA (https://www.mozilla.org/security/announce/)
There seems to be some significant changes - updated over-top.
My add-ons manager or [about:addons] seems to be rendering slower. Just my .02 :cool:
Font rendering (https://support.mozilla.org/en-US/kb/change-fonts-and-colors-websites-use) has always been buggy under Firefox. I'd take Mozilla to task on that one.
(https://www.landzdown.com/proxy.php?request=http%3A%2F%2Fimg.photobucket.com%2Falbums%2Fv330%2Fsiljaline%2FPics%2FBSODUser_zpsbad6515e.gif&hash=09c28f6ff02963cd72c16593dd5ae42c780968d8)
Sophos writeup about the update: Firefox sneaks out an "inbetweener" update, with security improvements rather than fixes | Naked Security (http://nakedsecurity.sophos.com/2014/09/14/firefox-sneaks-out-an-inbetweener-update-with-security-improvements-rather-than-fixes/)
Version 32.0.2 of Firefox was released to fix a critical bug where corrupt installations cause Firefox to crash on update.
Bug 1063052 (https://bugzilla.mozilla.org/show_bug.cgi?id=1063052) - Firefox 32+ startup crash in nsFrame::BoxReflow
Download Firefox 32.0.2 in your language (https://www.mozilla.org/en-US/firefox/all/) • Release Notes (https://www.mozilla.org/en-US/firefox/32.0.2/releasenotes/)
Build version [32.0.3] is available. Release notes (https://www.mozilla.org/en-US/firefox/32.0.3/releasenotes/) Download in your language (https://www.mozilla.org/en-US/firefox/all/)
Quote from: siljaline on September 24, 2014, 09:29:42 PM
Build version [32.0.3] is available. Release notes (https://www.mozilla.org/en-US/firefox/32.0.3/releasenotes/) Download in your language (https://www.mozilla.org/en-US/firefox/all/)
I read this post and then opened FF and searched "about" this version, and it applied some updates and requested a restart. It's still version 32.0.2.
What differentiates "... Release channel users ..." (stated in the link you provided) from the rest of us? And, what is "Build version [32.0.3]"? A beta of some sort? If it's not a beta and is actually the newest version of FF, why doesn't FF just upgrade to the latest version when FF users check the "about" feature?
Yup! :wink: You can count on me for continual stupid questions.
Hi, John.
No, Build version 32.0.3 is not a beta, it is the most recent version. With the change to their "Rapid Release Program", Firefox is updated to a new version every 42 days. Those updates are a version increment. Any updates released within the 42 days are either bug fixes, security updates or a combination that cannot wait until the scheduled version update. Thus, during this cycle, we've had version 32.0, 32.0.1, 32.0.2 and now 32.0.3.
As to the language page that siljaline linked to, there are translators who provide localized versions for the languages shown on that page. However, it is not unusual that the translations haven't kept up to the update.
To get the latest version of Firefox, see Update Firefox to the latest version | Firefox Help (https://support.mozilla.org/en-US/kb/update-firefox-latest-version?redirectlocale=en-US&redirectslug=Updating+Firefox)
Thank you, Corrine! :rose:
Fixed in Firefox 32.0.3 per Firefox security advisories (https://www.mozilla.org/security/known-vulnerabilities/firefox.html) • MFSA2014-73 (https://www.mozilla.org/security/announce/2014/mfsa2014-73.html) RSA Signature Forgery in NSS
Quote from: Corrine on September 24, 2014, 11:08:37 PM
Hi, John.
No, Build version 32.0.3 is not a beta, it is the most recent version. With the change to their "Rapid Release Program", Firefox is updated to a new version every 42 days. Those updates are a version increment. Any updates released within the 42 days are either bug fixes, security updates or a combination that cannot wait until the scheduled version update. Thus, during this cycle, we've had version 32.0, 32.0.1, 32.0.2 and now 32.0.3.
As to the language page that siljaline linked to, there are translators who provide localized versions for the languages shown on that page. However, it is not unusual that the translations haven't kept up to the update.
To get the latest version of Firefox, see Update Firefox to the latest version | Firefox Help (https://support.mozilla.org/en-US/kb/update-firefox-latest-version?redirectlocale=en-US&redirectslug=Updating+Firefox)
Corrine, I just had an "aha!" moment. When I arrived here at work, I followed your link where it states that FF should automatically update to the latest version. That's what I thought should happen. The mistake I made was not restarting the browser (computer?) after I clicked "about" this morning and the updates subsequently being loaded. Stupidly, I first checked "programs" which showed 32.0.2. Now it shows 32.0.3. My bad.
Anyway, thanks again for your prompt reply. :smiley: :rose:
That's right, John, you need to restart the browser and provide UAC account approval to approve the changes.