Mozilla Plans Fix For Critical Firefox Vulnerability In Next Release
Trailrunner7 writes "A month after an advisory was published detailing a new vulnerability in Firefox, Mozilla said it has received exploit code for the flaw and is planning to patch the weakness on March 30 in the next release of Firefox. Mozilla officials said Thursday that the vulnerability, which was disclosed February 18 by Secunia, is a critical flaw that could result in remote code execution on a vulnerable machine. The vulnerability is in version 3.6 of Firefox."
Congratulations on your purchase of a brand new nigger! If handled properly, your apeman will give years of valuable, if reluctant, service.
INSTALLING YOUR NIGGER.
You should install your nigger differently according to whether you have purchased the field or house model. Field niggers work best in a serial configuration, i.e. chained together. Chain your nigger to another nigger immediately after unpacking it, and don't even think about taking that chain off, ever. Many niggers start singing as soon as you put a chain on them. This habit can usually be thrashed out of them if nipped in the bud. House niggers work best as standalone units, but should be hobbled or hamstrung to prevent attempts at escape. At this stage, your nigger can also be given a name. Most owners use the same names over and over, since niggers become confused by too much data. Rufus, Rastus, Remus, Toby, Carslisle, Carlton, Hey-You!-Yes-you!, Yeller, Blackstar, and Sambo are all effective names for your new buck nigger. If your nigger is a ho, it should be called Latrelle, L'Tanya, or Jemima. Some owners call their nigger hoes Latrine for a joke. Pearl, Blossom, and Ivory are also righteous names for nigger hoes. These names go straight over your nigger's head, by the way.
CONFIGURING YOUR NIGGER
Owing to a design error, your nigger comes equipped with a tongue and vocal chords. Most niggers can master only a few basic human phrases with this apparatus - "muh dick" being the most popular. However, others make barking, yelping, yapping noises and appear to be in some pain, so you should probably call a vet and have him remove your nigger's tongue. Once de-tongued your nigger will be a lot happier - at least, you won't hear it complaining anywhere near as much. Niggers have nothing interesting to say, anyway. Many owners also castrate their niggers for health reasons (yours, mine, and that of women, not the nigger's). This is strongly recommended, and frankly, it's a mystery why this is not done on the boat
HOUSING YOUR NIGGER.
Your nigger can be accommodated in cages with stout iron bars. Make sure, however, that the bars are wide enough to push pieces of nigger food through. The rule of thumb is, four niggers per square yard of cage. So a fifteen foot by thirty foot nigger cage can accommodate two hundred niggers. You can site a nigger cage anywhere, even on soft ground. Don't worry about your nigger fashioning makeshift shovels out of odd pieces of wood and digging an escape tunnel under the bars of the cage. Niggers never invented the shovel before and they're not about to now. In any case, your nigger is certainly too lazy to attempt escape. As long as the free food holds out, your nigger is living better than it did in Africa, so it will stay put. Buck niggers and hoe niggers can be safely accommodated in the same cage, as bucks never attempt sex with black hoes.
FEEDING YOUR NIGGER.
Your Nigger likes fried chicken, corn bread, and watermelon. You should therefore give it none of these things because its lazy ass almost certainly doesn't deserve it. Instead, feed it on porridge with salt, and creek water. Your nigger will supplement its diet with whatever it finds in the fields, other niggers, etc. Experienced nigger owners sometimes push watermelon slices through the bars of the nigger cage at the end of the day as a treat, but only if all niggers have worked well and nothing has been stolen that day. Mike of the Old Ranch Plantation reports that this last one is a killer, since all niggers steal something almost every single day of their lives. He reports he doesn't have to spend much on free watermelon for his niggers as a result. You should never allow your nigger meal breaks while at work, since if it stops work for more than ten minutes it will need to be retrained. You would be surprised how long it takes to teach a nigger to pick cotton. You really would. Coffee beans? Don't ask. You have no idea.
MAKING YOUR NIGGER WORK.
Niggers are very, very averse to work of any kind. The nigger's most
There's a disturbing amount of "Microsoft" in this.
Ok, so, since the summary didn't make this clear and I didn't find any explanation in the article, maybe someone on Slashdot can shed some light on this. What took Mozilla so long? It's a critical vulnerability that allows remote code execution. Why did is it taking over a month to fix?
Please correct me if I got my facts wrong.
It's a critical vulnerability that allows remote code execution. Why did is it taking over a month to fix?
Answer: Further details available in Customer Area
Just because you run Firefox, you can't relax about malware attacks. Not on Windows anyway. Imagine how quickly an exploit of this type could be integrated into a malware kit, already running on countless compromised sites? No one can relax about buffer/stack smashing, dangling pointers, etc..., until there's a bulletproof safeguard against them built into the OS/processor architecture.
Emotions! In your brain!
I am afraid, just planning for a fix isn't enough. Saying definitively that a fix will be available is more useful.
You might ask why:
Because plans are notorious for remaining just that. That is, plans.
Why are companies so unwilling to micro-patch their software? If Mozilla has a fix NOW, why are they waiting another ~2 weeks to push it out with the next minor upgrade? Just to avoid making users upgrade too often?
OMFG, it's a critical vulnerability and it takes ONE month for them to fix. Those dogs of redmond... That's the advantage of OS. An open source project would have issued a fix in one day....oh wait...
Because if this was IE, the bug would already be patched in what is a beta release... oh no. IE takes months if not years to patch holes in production releases.
MS fanboy's, always miss those tiny details for some reason.
Which distro would make it easier to update FFox and other apps?
I've used the rpm ones and rpm Uvh is somewhat easy; repositories are not that immediate though and dependence is not always simple to solve.
Ubuntu has well-maintained repositories and apt-search/apt-get makes ones life so easy -- except when you find you can't get the last FF. I installed the last one once, only to see it returned to the version present in the official repositories.
And there's always the problem of binary availability... not that compiling is that frightening -- but regarding binaries, it's either Fedora or Debian/Ubuntu.
To further complicate matters, I don't want Gnome...
And what happened to distro-agnostic packaging?
So you can get the untested version now which may or may not fix the vulnerability and potentially botch-up your system. This is better than waiting until March 30th in what way?
This is why Mozilla should be implemented in Java, Smalltalk, Lisp, OCaml or a similar system. I don't know enough about this particular vulnerability to say if it would make a difference, but in general any garbage-collected language without obvious pointer indexing and with built-in array index checking is going to have a lot fewer low level security problems like buffer overruns or duplicate deallocations and so on that can lead to malicious code execution... Is the slight speed boost from a language like C++ worth all the extra security issues at this point, now that we have such fast computers? And with manual memory allocation and deallocation, sometimes code written in C++ can be slower than a language that takes care of it for the programmer in an optimal way... As a reminder:
http://en.wikipedia.org/wiki/Greenspun's_Tenth_Rule
"Any sufficiently complicated C or Fortran program contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of Common Lisp." (or Smalltalk or some other languages...)
A 21st century issue: the irony of technologies of abundance in the hands of those still thinking in terms of scarcity.
Alternatively, users can download Release Candidate builds of Firefox 3.6.2 which contains the fix from here:
https://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/3.6.2-candidates/build3/
s/©//g
Seeing as how something's already botched up, QA seems like a moot point...
I thought rats got in my computer and ate my sdram module, then I discovered it was just FF 3.6. Seriously, anyone one else having a huge memory gobbling problem with this?
"But, does it run on Linux?"
Hey, if the damned exploit won't run on Linux, then it's not a real exploit, is it? This kind of thing kinda pisses me off. There are all KINDS of neat software out there, that just won't run on Linux. It's definitley not fair. I think it might even be illegal. In today's modern world, no one is supposed to be excluded from anything. Not even nerds!!
"Windows is like the faint smell of piss in a subway: it's there, and there's nothing you can do about it." - Charlie Br
In other news, several security bigwigs have recommended using IE or Opera until 3.6.2 is released... wait, no... as the faulty product is not from MS, we don't care... keep using FireFox.
Luckily I'm still using IE6.
Though it wasn't presented to me in EU's browser choice, I was able to prevent any other browser to infect my system with their buggy code.
Good thing I'm using IE6.
Fuck I just upgraded too, like a week or so ago. =\
Why is common sense called that if it's not common?
This post is one serious candidate for removal.
And the least offending part is the word nigger; people should not be enraged by the use of such a word.
The real problem is using common words for racial slur.
Funny thing, one can read the entire post replace the word nigger with "car" or "cellphone". It works the same, because all the text is made-up anyway...