Mozilla Firefox Version 36 Released with Security Updates

[siljaline]

Checking your plugins will also tell you you're running an older version of Firefox.
For those that do not wish to run the somewhat compromised new version as discussed here, may not want to obey this prompt.

[DonnaB]

How weird is this.....

I went surfing around the many forums I frequent and found that I experienced this scroll bar issue only on forums that used IP.Board software. Reverting back to FF 35.0.1 fixed the problem. No more scroll bar at the bottom of the reply boxes at any of the forums.   :laughing:

[satrow]

Clearest info I've seen so far: Bug 1136772 - Suddenly Windows 7 firewall is blocking Firefox 36.0 on our network, Anyone else having this issue?

Looks like the firewall exception is purely for the detection of Roku devices (which apparently should only be, or are only designed/intended for, Private networks).

The FF installer is set to open firewall exceptions on both Public and Private networks, causing blocking in W7 when it fails when it's on a Domain connected PC.

Those on Private networks should not see the firewall popup, those on Public (higher security) do.

There's also a request for someone from security to evaluate (I hope it's not the same person who gave it the go-ahead first time around!).

It's not clear whether the definition Private as used includes both Home and Work networks as defined by MS.

The bottom line looks like "Let's add lots of stuff and release it, if we get problems, we'll call in an expert while we read the manuals".

[Corrine]

That does make sense why I didn't get the firewall exception prompt. 

The bottom line looks like "Let's add lots of stuff and release it, if we get problems, we'll call in an expert while we read the manuals".

That, unfortunately, sounds like a perfect definition of the path Firefox has been going since the move to the rapid release schedule. 

[ky331]

Firefox 36.0.1  ( 5 March 2015 )

What's New  ( https://www.mozilla.org/en-US/firefox/36.0.1/releasenotes/ )

◦Fixed
36.0.1 - Disable the usage of the ANY DNS query type (1093983)

◦Fixed
36.0.1 - Fixed a startup crash with EMET (1137050)

◦Fixed
36.0.1 - Hello may become inactive until restart (1137469)

◦Fixed
36.0.1 - Print preferences may not be preserved (1136855)

◦Fixed
36.0.1 - Hello contact tabs may not be visible (1137141)

◦Fixed
36.0.1 - Accept hostnames that include an underscore character ("_") (1136616)

◦Fixed
36.0.1 - WebGL may use significant memory with Canvas2d (1137251)

◦Fixed
36.0.1 - Option -remote has been restored (1080319)

◦Fixed
36.0.1 - Fix a top crash

[Corrine]

The update to version 36.0.1 includes nine (9) security updates, of which four (4) are identified as high, four (4) moderate and one (1) low.  The security updates included in this release are items 2015-19 through 2015-27 at Security Advisories for Firefox.

[siljaline]

Firefox 36.0.1 still breaches your Firewall. Angry Tweets to https://twitter.com/mozilla &  https://twitter.com/firefox sent. 

[Corrine]

Can't figure out why some people get the Firewall exception and others don't. 

[siljaline]

Until the Firewall bug has been fixed, I've reverted to FF 35.0.1 

[siljaline]

Can't figure out why some people get the Firewall exception and others don't.

I've asked over at MozillaZine, we'll see what shakes out although they been likely told by Corporate to keep their mouths shut on the firewall pinhole as Hello seems to be a big seller. 

[plodr]

I also can not figure out why 31 ESR does not get updated as often as v 36. Isn't it vulnerable to the 9 security flaws that have been patched? Maybe it doesn't have all the bells and whistles that add security holes to the browser.
Every time FF gets an update, I check the ESR running on three of the computers.

[Corrine]

Can't figure out why some people get the Firewall exception and others don't.

I've asked over at MozillaZine, we'll see what shakes out although they been likely told by Corporate to keep their mouths shut on the firewall pinhole as Hello seems to be a big seller. 

:thumbsup: on this:

If Market share is something Mozilla wants to keep, John and his big crew need to be more transparent.

I followed the link you posted to the instructions to toggle loop.enabled to false to disable "Hello" and have not received the firewall exception prompt.

[siljaline]

@ Corinne - I think you had mentioned further up this thread or on Facebook that some were getting the Firewall exception closed once having done the about:config (toggle loop) trick to close out Hello.

It works for some but from what I've seen with many users, this has not worked.

Thus, many are staying at Firefox version 35.0.1  My post at MozillaZine has gone unanswered as have Tweets to Mozilla and Firefox.

Mozilla have clearly shot themselves in the proverbial foot on this one in introducing a Browser based chat client that needs to speak through your Firewall. Until they've told us how to fix this - many we not go forward with the rapid releases of Mozilla Firefox.

This and other ongoing issues has put Firefox on the endangered species list



 

[plodr]

I now use PaleMoon exclusively. When I go to a website, am I identified as using FF or PM?
If FF then perhaps the 10% or fewer of us identified as using FF are not really using it.

[Corrine]

I also use PaleMoon exclusively.  Two out of three sites recognize that I am using PaleMoon by the UserAgent:

https://www.whatismybrowser.com/
http://www.whatbrowser.org/

This site thinks I'm using FF 31.9:  http://www.whatbrowseramiusing.co/

Many websites do not recognize the PaleMoon UserAgent.  As a result, with version 25.0.2, Moonchild added a default setting under Options > Advanced > General to set Firefox Compatibility mode.  (More info here:  http://forum.palemoon.org/viewtopic.php?f=24&t=6004)