News for hackers. Stuff that matters.
Re:Firefox 27 Released by nfoz on Tuesday February 04, 2014 @10:54AM (#7178186)
I would much rather a long-term-stable product with fewer security vulnerabilities that didn't need frequent updates.
Re:Firefox 27 Released by nly on Tuesday February 04, 2014 @11:21AM (#7178359)
I think that's a false dichotomy. High profile targets like FF aren't going to survive without frequent updates, regardless of feature bumping releases. Personally I wouldn't want to have to go back to convincing people to upgrade between major releases again, and thus far Mozilla has kept FF pretty stable so I see no reason to worry.
Re:Firefox 27 Released by yeukhon on Tuesday February 04, 2014 @12:41PM (#7178968)
False logic. Slow update does not mean you have secure version. You can get ESR if you want the so-called LTS version. Freqeunt update addresses multiple things quickly:

(1) security vulnerability,

(2) performance regression

(3) new features

For a software widely used like FF, it is important that they keep the software up-to-date, make the software as slim as possible, and make the software easy to use. If you want to do some "AB" testing, frequent testing is necessary.

When was the last time you boot up Ubuntu LTS and think "oh I need to update?"

Browser tends to move fast and break fast because browser is a complex software and because the tool people use to make web application are so flexible there are so many corner cases (which can be abused to use to make things work) it is hard to have a dead version.

I look at the CentOS machine yesterday and I thought "god, where is the shiny webconsole that FF comes with?" CentOS apparently comes with old FF and I had to force to upgrade to 26.

Re:Firefox 27 Released by nfoz on Tuesday February 04, 2014 @12:55PM (#7179077)
> Slow update does not mean you have secure version.

This was not my claim. When there are security vulnerabilities I'm happy for the updates to be as quick as possible and as frequent as necessary. The problem is:

> (3) new features

Adding new features has a high chance of new security flaws, when you're operating at the speed of firefox on such an error-prone technology stack.

Different users want to meet this trade-off differently. I want fewer features, in fact I'm ok not to be bleeding-edge compatible with the latest poorly-designed HTML draft spec if it means a more secure browser. It's a question of how and where Mozilla (or other browser teams) organize their effort.

Re:Firefox 27 Released by yeukhon on Tuesday February 04, 2014 @01:12PM (#7179188)
You have to take a couple things into account.

1. FF is a product, meaning if Chrome or Opera or Safari have some shiny features that a lot of developers enjoy to have, FF will very likely implement that feature.

2. Some new features are to replace the old one. For example, the original Firefox sync was pain in the ass and so there will be a new thing called Firefox Account. That's a new feature to user but it's easier to use and makes more sense to users.

3. Some new shiny features are there because of requests. People requested them and developers thought they were useful for users to have. That's inevitable. Unlike Windows, unless you cry to TechCrunch, MS won't care about your email because it's one of the 1000000 emails they receive every day.

In reality, software can't stay in the way the old OS works. Granted, we take Android fun as they roll out new features. But we can't upgrade easily because the phone manufacture and/or the service provider does not provide the stock upgrade (at least this is how my shitty phone works).

I know there are compatibility breakage and some UI decisions are really really bad. For instance, the latest nightly rolls out a different color scheme for web console which I find a huge problem for people with poor eye sight (me) or work long hours. The UI is changing to australis soon (maybe 29, maybe 30, don't remember, they haven't have a final decision yet).

It is actually quite frustrating to work in the browser side. A line of change can impact millions of websites. Often time you have to make a complex patch to make simple adjustment.

Regarding security vulnerability, I personally think they are minor compare to other more common, cheap threats. They are exploitable (and yes some are critical and severe) but when was the last time you find yourself exploited because of browser? It was probably you downloading an infected file. I know this is kind of unethical to say, but I think it is fair to say browser is quite secure these days and attackers are more likely to do things like clickjacking.

I don't remember if Firefox rolls out update (not upgrade) that includes vulnerability fixes or not. Someone correct me on this.

Re:Firefox 27 Released by girvo on Tuesday February 04, 2014 @10:45PM (#7181758)
Then get the ESR version? That's what you're looking for if those are your requirements.
Re:Firefox 27 Released by gtaylor on Tuesday February 04, 2014 @11:13AM (#7178309)
On the flipside, a frequently updated browser that is constantly improving is a bit of a moving target. Because of the ease for them to push out updates, vulnerabilities can be fixed and pushed out to the vast majority of users in short order. Malicious people may only get a few days/weeks to wreak havoc at a large scale, as the vast majority will have updated shortly after the problem is fixed.

In Forefox's case, the frequent releases more have to do with rapid improvement and iteration than anything. Read the changelog and notice how it was largely a bunch of mid-moderate improvements. Some CSS goodies, some JS goodies, some security goodies.

Re:Firefox 27 Released by fabrice_d on Tuesday February 04, 2014 @11:27AM (#7178410)
Note that we don't wait 6 weeks to push security updates when there is any serious issue. We do "chemspill" releases in these cases to fix the problem as soon as possible (usually less than 2 days after it's reported).
Re:Firefox 27 Released by gtaylor on Tuesday February 04, 2014 @11:31AM (#7178441)
And I am thankful for this! You guys do great work.
Re:Firefox 27 Released by nirvdrum on Tuesday February 04, 2014 @11:08AM (#7178273)
Check out the Firefox ESR builds. They're supported for 1 year. Not super long-term, but better than 6 weeks:

http://www.mozilla.org/en-US/firefox/organizations/all/

Re:Firefox 27 Released by nfoz on Tuesday February 04, 2014 @12:23PM (#7178817)
That's great, I didn't know this existed. Thanks.
Re:Firefox 27 Released by hollerith on Tuesday February 04, 2014 @11:23AM (#7178380)
My browser is on the ESR (Extended Support Release) update channel instead of the usual, "release" update channel.

I can recommended it.

Re:Firefox 27 Released by iambateman on Tuesday February 04, 2014 @11:15AM (#7178319)
If you want a browser that is released once per year...be my guest: http://www.apple.com/safari/
Re:Firefox 27 Released by orbitur on Tuesday February 04, 2014 @11:03AM (#7178244)
To have that, we would need to be disconnected from the internet.
Re:Firefox 27 Released by cpeterso on Tuesday February 04, 2014 @12:18PM (#7178781)
What browser do you use now? I recommend Firefox's Extended Support Release, which receives only security updates for twelve months
Re:Firefox 27 Released by dangayle on Tuesday February 04, 2014 @12:45PM (#7178998)
How did that work for the TOR browser? It didn't.
Re:Firefox 27 Released by jlgaddis on Wednesday February 05, 2014 @05:11PM (#7187210)
I assume you're referring to the Firefox vulnerability that was exploited to attempt to identify users of the Tor Browser Bundle?

FWIW, that had also been fixed by the Tor Project and a newer version of TBB was available. The users who had upgraded were not vulnerable.

Re:Firefox 27 Released by dangayle on Tuesday February 11, 2014 @04:19PM (#7220537)
Yes, that's what I was referring to. I was unaware that a newer version had been available that had addressed that issue. It's hard sometimes to plow through the FUD to know exactly what happened. Thanks.