Slashdot Mirror


Bugzilla Breached, Private Vulnerability Data Stolen

darthcamaro writes: Mozilla today publicly announced that secured areas of bugzilla, where non-public zero days are stored, were accessed by an attacker. The attacker got access to as many as 185 security bugs before they were made public. They say, "We believe they used that information to attack Firefox users." The whole hack raises the issue of Mozilla's own security, since it was a user password that was stolen and the bugzilla accounts weren't using two-factor authentication. According to Mozilla's FAQ about the breach (PDF), "The earliest confirmed instance of unauthorized access dates to September 2014. There are some indications that the attacker may have had access since September 2013."

97 comments

  1. Haha. by Anonymous Coward · · Score: 3, Insightful

    You just can't make this stuff up.

    I've come to the conclusion that human nature just does not allow good security. If you make something completely secure, you've spent way too much time on it and your competitors have beat you to market. People don't care.

    1. Re:Haha. by Anonymous Coward · · Score: 0

      Yes, many are too lazy to spend the little extra time to do it correctly. I haven't been bitten yet, so why care?

    2. Re:Haha. by Anonymous Coward · · Score: 0

      Uh-huh.
      And if you make it idiot-proof, then you can be pretty sure that only idiots will be going to use it. (*sigh!*)

    3. Re: Haha. by Anonymous Coward · · Score: 0

      I came here to type "Hahahahahahahaha who cares anymore?" This shit is unbelievable. Bugzilla is a terrible piece of software, as anyone who's ever used it knows. This is no surprise to me. WHY ARE PEOPLE USING BUGZILLA?

    4. Re: Haha. by Anonymous Coward · · Score: 0

      Rhymes with hogfood

    5. Re: Haha. by Anonymous Coward · · Score: 0

      because it is free.

      Always remember: Open source is only free if your time is worthless.

    6. Re: Haha. by Anonymous Coward · · Score: 0

      Closed source is only free if... hm, I guess it's not. And of course, nobody has ever spent any time at all trying to delete that last fucking page of a Microsoft Word document.

    7. Re: Haha. by Anonymous Coward · · Score: 0

      Doesn't this assume that you spend every minute of your day earning money? If you spend time you wouldn't spend working using open source, how is that an actual loss? On paper, yes your time is 'wasted' but I can't imagine people who are productive 24 hours a day.
       
      I hear people make this argument at work "It takes too much time to do do it cheaply and time is money!" Yes, if you're spending all 8 hours being productive. If you're standing there pounding the pooch anyway, it doesn't actually cost more for you to do your job properly.

    8. Re: Haha. by Anonymous Coward · · Score: 0

      Slow day for Microsoft shills?

      http://itsfoss.com/97-percent-worlds-top-500-supercomputers-run-linux/

      97 Percent Of The World’s Top 500 Supercomputers Run Linux

      distrowatch.com

      http://www.technobuffalo.com/2013/08/22/nsa-windows-8-exploit/
      http://www.technobuffalo.com/2013/07/11/microsoft-gave-the-nsa-direct-backdoor-access-to-outlook-skype/
      http://winsupersite.com/windows-10/how-stop-windows-10-upgrade-downloading-your-system
      http://www.extremetech.com/computing/195592-with-windows-10-microsoft-could-move-to-a-subscription-based-model
      http://www.extremetech.com/computing/205320-microsoft-windows-10-will-be-the-last-version-of-windows
      https://www.youtube.com/watch?v=5GU5uv28a3I
      http://techrights.org/2015/07/31/vista-10-anticompetitive/
      https://www.youtube.com/watch?v=wwRYyWn7BEo
      https://www.youtube.com/watch?v=Gghj03J_ri0
      http://localghost.org/posts/a-traffic-analysis-of-windows-10
      http://www.ghacks.net/2015/08/28/microsoft-intensifies-data-collection-on-windows-7-and-8-systems/

      https://gitlab.com/windowslies/blockwindows
      I suggest just copy the hosts file to your /etc folder. Disable Automatic updates and read every KB before you let it update/install in the future (forever). When Patch Tuesday or "some special scary news occasion" comes... just rename the hosts file to hosts_disable or similar while you do any updates you care to. Reboot and rename the hosts file back to hosts so it is detected.

      Who would care to steal Bugzilla's bugs for Firefox? Maybe oh I don't know, look at any company with a complete CLOSED SOURCE GLOBAL SPYWARE OPERATING SYSTEM LIKE WINDOWS 10... or you know a company pushing a new browser.

      Could be anybody sure because there is a buyer for that information.

    9. Re: Haha. by Anonymous Coward · · Score: 0

      Pirated.

    10. Re: Haha. by Anonymous Coward · · Score: 0

      Everything has a cost, whether financial or otherwise. Before I had children I wasted a lot of time doing meaningless things on the Internet, like filing almost 2,000 Bugzilla bugs. Now I don't have time for that shit as I'd much rather spend time with my son than waste it pointing out what a failure Firefox has become.

    11. Re: Haha. by Anonymous Coward · · Score: 2, Interesting

      Bugzilla is an especially bad piece of software. I had to use it for years.

      Here's the proof:
      https://bugzilla.mozilla.org/show_bug.cgi?id=540

      This bug was open since 1999 and survived a complete rewrite of bugzilla in a another language. Nice read if you have the time.

      How someone could still use this piece of crap is beyond me. Especially Mozilla.

    12. Re:Haha. by Anonymous Coward · · Score: 1

      Indeed. I worked for software 'security' startup with security certifications and security is the least important priority. They have documented procedures that are demanded by the customers and they exist purely for show.
      Some examples are:
      - Most developers have full read/write access to customer data and many modify it without telling anyone (procedures require tickets).
      - Vulnerabilities such as XSS are ignored by developers and we have to notify customers within 30 days by contract. Upper management orders to not tell customers.
      - Support and sales share customer passwords over email ... threads get forwarded around with said passwords.
      - Some of the third party libraries versions are up to decade old ... yet still maintained but the dev are afraid to upgrade.
      - Some devs bring code from former employers and are praised for it.
      - Lead devs have no understanding of unittesting and refuse to write them: it is QA job to find bugs.

      And this is happening at a successful 'unicorn' startup, the customers are very large financial companies, health insurances, even foreign government agencies.

      I can only conclude that security certifications are meaningless since the external auditors make no efforts whatsoever to confirm that the procedures are nothing more than TSA theater.

    13. Re: Haha. by shonangreg · · Score: 1

      I know you geeks can be "eccentric", but I don't think you can pick up girls by claiming the way to fix this is to jog nude.

    14. Re: Haha. by Gerv · · Score: 1

      There was no issue with the Bugzilla software here; the problem was that a user reused their password on another site, which suffered a breach.

      Gerv

    15. Re: Haha. by Gerv · · Score: 1

      The bug is unfixed for philosophical reasons, not because it's hard to fix. The Bugzilla developers feel history should be immutable.

      And there has been no rewrite into another language since that bug was filed; Bugzilla as released by Mozilla has always been in Perl.

      Gerv

  2. Interesting Data Point by Bill+Hayden · · Score: 5, Interesting

    The most interesting aspect of this, in my opinion, is that once the vulnerabilities were known to not be private anymore, the vendor (Mozilla in this case) immediately fixed all of them. Some bugs had been open for over 300 days. What this says to me is that by keeping vulnerabilities private, it makes vendors lazy about fixing them, and is another data point in favor of the "full disclosure" model of computer security.

    --
    Protect your browser with the Force Safe Search add-on
    1. Re:Interesting Data Point by Anonymous Coward · · Score: 0

      Every time a vendor cries about a vulnerability being made public an angel gets its wings. Make the world a better place. Release immediately.

    2. Re:Interesting Data Point by Anonymous Coward · · Score: 3, Interesting

      What this says to me

      I'm glad it's talking to you, and not that you're actually concluding anything, nor even making correct observations.

      It demonstrates that disclosure should occur after a certain limited time period, but not "full disclosure". No bug is fixed instantly, and Mozilla didn't "immediately" do anything - it just did so in short time.

      It never ceases to amuse me how binary nerds are in their answers to problems. Every real-world problem involves a nuanced solution which acknowledges extremes only as an initial, crude approximation reality.

      (Communists, libertarians, atheist-zealots and God-thumpers can fuck off for the same reasons.)

    3. Re:Interesting Data Point by Anonymous Coward · · Score: 0

      What does that have to do with Republican control of Bugzilla? They control it. They rule over the main contributors lives, just as they rule over nearly every minute of all of our lives. They control everything. They are why this world is so screwed-up. It is screwed-up, because they decided to screw it up. They're the ones that did this. They did this.

    4. Re:Interesting Data Point by Anonymous Coward · · Score: 4, Insightful

      Absolutely true.

      There was one password stealing bug (javascript can steal focus between tabs) that I was tracking in Firefox for _over 2 years_ that kept getting deferred.

      Then one day, it got reported on one of the big security mailing lists. Suddenly, a new bug report got created and fixed within 2 days, and the 2 year old bug report got marked as a duplicate. The devs went on to pat themselves on the backs and crow publicly about how they fixed it so quickly.

    5. Re:Interesting Data Point by Anonymous Coward · · Score: 1

      After reading the article it seems like they held up on those last 10 severe vulnerabilities due to potential regressions.

    6. Re:Interesting Data Point by radarskiy · · Score: 3, Insightful

      "it makes vendors lazy about fixing them"

      You cannot say this without knowing what they were doing instead of fixing these particular bugs. They may have correctly triaged the undisclosed bugs in terms of importance until disclosure forced less important bugs to a higher urgency.

    7. Re: Interesting Data Point by Anonymous Coward · · Score: 0

      Dude!

    8. Re:Interesting Data Point by Anonymous Coward · · Score: 0

      Do you have link for this bug? (surely you do since you were tracking it for _over 2 years_)

    9. Re:Interesting Data Point by DNS-and-BIND · · Score: 3, Insightful

      Oh, come on, that's bullshit, Mozilla hates fixing bugs and would much rather work on adding new features. Anytime someone tries to pull that "we are working on more important bugs" baloney, it means they're not working on anything. Those bugs will sit there unfixed for years, if they were actually prioritizing bugs they'd get fixed eventually. But, no. It's just a phrase they use to brush off criticism.

      --
      Shutting down free speech with violence isn't fighting fascism. It IS fascism!
    10. Re:Interesting Data Point by citizenr · · Score: 1

      "it makes vendors lazy about fixing them"

      You cannot say this without knowing what they were doing instead of fixing these particular bugs.

      we do know, they SAT ON THEM

      --
      Who logs in to gdm? Not I, said the duck.
    11. Re:Interesting Data Point by amorsen · · Score: 1

      They may have correctly triaged the undisclosed bugs in terms of importance until disclosure forced less important bugs to a higher urgency.

      They made the assumption that undisclosed bugs are unknown to blackhats. As the breach shows, that is a pretty bad assumption.

      Basing importance on the disclosure status is a horrible policy, and the only effective antidote is immediate full disclosure without grace period.

      --
      Finally! A year of moderation! Ready for 2019?
    12. Re:Interesting Data Point by ioErr · · Score: 1

      Most likely referring to this bug or one of its duplicates: https://bugzilla.mozilla.org/s...

  3. Re:Chrome by Anonymous Coward · · Score: 5, Informative

    Just one more reason to use Chrome. Firefox hasn't offered anything in years that Chrome doesn't do and does better, and since it's free and open source there's really no reason at all to stick with a legacy browsers.

    Chromium is open source. Chrome is not.

  4. *Mozilla* Bugzilla breached. Not all bugzillas by Da+w00t · · Score: 5, Informative

    Please update the article title, JFC.

    --

    da w00t. mtfnpy?
    1. Re:*Mozilla* Bugzilla breached. Not all bugzillas by Anonymous Coward · · Score: 0

      You're asking Soulskill to expend effort on something. I wouldn't hold my breath.

  5. Re: Republicans don't give a damn about security.. by Anonymous Coward · · Score: 0

    They hate us. You should never vote for someone that hates you.

  6. Lol by Anonymous Coward · · Score: 0

    People still use Firefox? ....No really, seriously.

    1. Re:Lol by Anonymous Coward · · Score: 0

      People still use Firefox? ....No really, seriously.

      Tell us all the software you use, so that we may laugh at you.

    2. Re:Lol by bob_super · · Score: 3, Interesting

      Noscript + adblock + ghostery + gestures + faviconizetab + tabmixplus + Not_from_Google + Not_from_Apple + Not_from_MS + ...

    3. Re: Lol by Anonymous Coward · · Score: 0

      Is a list of things that will be gone in a year when Firefox removes their current extension API and forces everyone to use their current UX-driven monstrosity of a UI?

    4. Re: Lol by Anonymous Coward · · Score: 0

      Less than a year.

    5. Re: Lol by Anonymous Coward · · Score: 0

      And when they do, it's Pale Moon time.

    6. Re: Lol by Anonymous Coward · · Score: 0

      Mozilla Corporation will be bankrupt within 2 years of ending support for XUL extensions. Mark my words.

  7. Noticeably absent is WHEN this happened by 93+Escort+Wagon · · Score: 2

    Perhaps Mozilla discovered this long ago, but have spent all this time trying to ascertain the political opinions held by the attacker?

    --
    #DeleteChrome
    1. Re:Noticeably absent is WHEN this happened by Anonymous Coward · · Score: 0

      I was waiting for the first post to blame this on SJWs. I knew it would happen. It happened. Huhuhh Eich resigned because he was a bigot, therefore Mozilla = evil, amirite?

      Idiot.

    2. Re:Noticeably absent is WHEN this happened by nickweller · · Score: 1

      "The earliest confirmed instance of unauthorized access dates to September 2014" ref

  8. Re:Republicans don't give a damn about security... by Anonymous Coward · · Score: 0

    My God! You idiot moderators! Can't you enjoy a little sarcasm every now and then? Stop being such politically correct morons!

  9. I hate computers by AndyKron · · Score: 1

    I'm beginning to hate computers with a passion.

    1. Re:I hate computers by amicusNYCL · · Score: 1

      Why? Computers only do what the programmers tell them to. What exactly do you hate about them?

      --
      "Our two-party system is like a bowl of shit looking at itself in a mirror." - Lewis Black
    2. Re:I hate computers by Anonymous Coward · · Score: 0

      probably the same reason we all do.

      They are wonderful when they work. But when they dont. They are frustrating lumps of plastic and sand.

    3. Re: I hate computers by Anonymous Coward · · Score: 0

      This, I find myself wanting to learn more about how to fix engines instead of programming. Which is sad because I've loved computers and all that comes with it for over 16 years. I am just growing tired of it all. I would rather tweak my dirtbike and fix my cars.

      I may be becoming a gear head and not a puter nerd anymore:(

      Maybe I'll learn to write firmware for cars or something. Who knows.

    4. Re:I hate computers by antdude · · Score: 1

      Same here. I used to love computers, but these days I care not for them. Looking at the recent and newer stuff don't excite me anymore like those mobile, GUI, so many bugs, lack of support, security, so many updates, etc. Maybe it is my old age. :(

      --
      Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
    5. Re:I hate computers by antdude · · Score: 1

      Same here. It amazes me how easy they break in software and hardware. They're getting too complex. I prefer older stuff that just work well. :/

      --
      Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
  10. Bugzilla by allo · · Score: 1

    Nomen est Omen.

  11. A return to priorities? by SeaFox · · Score: 2, Insightful

    Gee Mozilla. Better get to work fixing those 185 vulnerabilities now, instead of sitting on them while you work on copying Chrome's look and feel or think of new unrelated tech ventures to get involved in.

    1. Re:A return to priorities? by 0123456 · · Score: 0

      Fixing bugs is boring. Particularly when you're an SJW who wants to Save The World.

    2. Re:A return to priorities? by Anonymous Coward · · Score: 0

      This. And while you're at it, nobody wants multi-process tabs - that's Chrome shit. And a 64-bit version? Forget it. And improving your hardware acceleration? Nonsense. And don't even get me started on all the time you've wasted on implementing HTML5 features just to be more like Chrome. You lazy assholes.

    3. Re: A return to priorities? by Anonymous Coward · · Score: 0

      Then the solution would be to tell mozilla developers that bugs are homophobe sexist patriarchy turned into code

    4. Re:A return to priorities? by Anonymous Coward · · Score: 0

      http://www.engadget.com/2015/0...

      No time to work on bugs when you're busy conducting a witch hunt because "blue-haired" is 100% actual hate speech. That and all their drum beating about diversity and culture, it's a wonder they've managed to get anything done of late.

    5. Re:A return to priorities? by Anonymous Coward · · Score: 0, Interesting

      I work for Mozilla. So I am really getting a kick out of most of these replies. Some of you guys are very good at making it sound like you know what you are talking about. But trust me.... You don't. I think you just want to make yourself sound smart, when in reality you don't know what you are talking about. This is how bad info gets passed around. If you don't know about the topic....Don't make yourself sound like you do. Because some Slashdotters believe anything they hear.

    6. Re:A return to priorities? by F.Ultra · · Score: 2

      Apparently most of the have been fixed a long time ago, the rationale behind the 185 number is that the account was compromised back in September 2013 and according to the user history he had looked at 185 bugs during that time frame.

    7. Re:A return to priorities? by Anonymous Coward · · Score: 0

      *Some* Slashdotters? Yikes, you greatly over-estimate us. The hivemind here is incredible. This is not a place for rational thought or logic. If I had a nickel for everytime people here just come up with some half-baked theory of everything that's wrong with [insert topic here], I'd still not be as rich as Rob Liefeld.

    8. Re:A return to priorities? by Anonymous Coward · · Score: 0

      You clearly have problems that not even the theoretical Mozilla you are arguing exists could solve.

    9. Re:A return to priorities? by tajribah · · Score: 1

      The single fact that there was a high-security bug unfixed for at least 335 days (as admitted by Mozilla's FAQ) tells that there was something very seriously wrong in Mozilla's handling of security vulnerabilities. That is the reality and it should be passed around.

    10. Re:A return to priorities? by Anonymous Coward · · Score: 0

      Mozilla: Mozilla Corporation believe in promoting a tolerant and diverse workplace. Towards that end, employees who express opinions other than those approved by management will be fired.

    11. Re:A return to priorities? by Anonymous Coward · · Score: 0

      Uh-huh, so what do you have to say about this bullshit?. I see bad bugs hang around for years as well.

    12. Re:A return to priorities? by Anonymous Coward · · Score: 0

      Some bugs are harder to fix than others. Accidentally writing a zero byte one past the intended memory range might be easy to fix. (Mozilla received such a bug report, once, that was ultimately determined to be fully exploitable.) An architectural issue requiring a fundamental rethink of a particular area of code will be far harder to fix. If this bug was more similar to the latter than to the former, perhaps 335 days is -- well, more understandable, at least, even if not desirable or fully justifiable.

    13. Re:A return to priorities? by Lennie · · Score: 1

      Do you really believe you can easily find developers that are really good at security code auditing and fixing security issues or use other developers and let them fix these security issues. I don't think these things are related.

      --
      New things are always on the horizon
    14. Re:A return to priorities? by tajribah · · Score: 1

      I accept that some security bugs can be hard to fix. Still, it gives a clear message about the values held by the organization if copying Chrome's UI has higher priority than fixing security bugs.

    15. Re:A return to priorities? by SeaFox · · Score: 1

      Firefox isn't one of those volunteer-staffed community projects. It has a large non-profit with paid developers backing it. Given all the people that use Firefox on a day-to-day basis to carry out sensitive health and financial-related tasks online, is it wrong to think Mozilla should hire a security-focused developer into the fold?

    16. Re:A return to priorities? by Anonymous Coward · · Score: 0

      That assumes developers are fungible, and that the developer who instead copies Chrome's UI, if we call it that, could be tasked with fixing security bugs instead. That certainly isn't the case for, say, an exploitable garbage collector bug.

    17. Re:A return to priorities? by tajribah · · Score: 1

      Well, yes and no... Within a year, almost anybody can learn to fix a garbage collector.

  12. Re: Chrome by Anonymous Coward · · Score: 0

    Firefox isn't open source any more. If you were to build Firefox from source, you would be missing DRM modules and wouldn't be allowed to call it Firefox due to Mozilla's asinine take on trademark laws. Iceweasel is open source, Firefox is not.

  13. Re:Republicans don't give a damn about security... by Anonymous Coward · · Score: 0
  14. bugzilla... by Anonymous Coward · · Score: 0

    got some bugs.

  15. Flip side: Higher priority bugs remain unfixed by davidwr · · Score: 4, Insightful

    The most interesting aspect of this, in my opinion, is that once the vulnerabilities were known to not be private anymore, the vendor (Mozilla in this case) immediately fixed all of them

    A better way of saying what really happened:

    ... is that once the vulnerabilities were known to not be private anymore, the vendor ... was forced to pull resources from more severe but still-believed-to-be-undisclosed bugs to get these patched, resulting in delays in getting those more-severe bugs fixed.

    --
    Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
    1. Re:Flip side: Higher priority bugs remain unfixed by Anonymous Coward · · Score: 0

      You have no proof of that at all. What I think happened is that some programmers who were inactive or working on the next new feature no one wants got reassigned to fixing bugs like they should have been doing all along.
      Severity is something very subjective and full disclosure has a tendency to align the vendor's opinion with the user's opinion, which is a good thing.

    2. Re:Flip side: Higher priority bugs remain unfixed by Anonymous Coward · · Score: 0

      I guess we have to take their word for it since the nature of those other bugs aren't public. Do you trust Mozilla Corporation? Because I don't.

  16. Mozilla has to do a full infrastructure review. by Anonymous Coward · · Score: 0

    Given the nature of this breach, I think that Mozilla's only option is to perform a full security review of their entire infrastructure and all of their products.

    I'm talking about every physical and virtual server that interacts with their network, including all servers, desktops, laptops and mobile devices. I'm talking about every software system, from Bugzilla to source repos to web servers to FTP servers to database servers to every other kind of software system they may be using.

    I think that all of their products, including Firefox, Thunderbird and Rust, should also undergo a line-by-line security review to ensure that they weren't tampered with in any way.

    The results should be presented to the public in a way that lets us know that they've done a thorough job of such a review, so that we can be confident that there are no more issues to be found.

    Will it be costly? Probably. Will it take a lot of time and effort? Probably.

    But if there was one breach, then I think we need some assurance that there weren't others. Given the nature of their products, and how critical security is to pretty much all of them, I think such a review is the only reasonable option.

    1. Re:Mozilla has to do a full infrastructure review. by Anonymous Coward · · Score: 0, Flamebait

      Given the nature of this breach, I think that Mozilla's only option is to perform a full security review of their entire infrastructure and all of their products.

      "We have performed a full security review of our entire infrastructure and all of our products, and we recommend moving to a flat design on a rolling release schedule with a cadence of one release per week. In order to reduce the number of code paths and further simplify the process of regression testing, all variables in about:config will be disabled, and the entire UX will consist only of one hamburger menu. Users who don't believe this represents significant progress are welcome to submit their own bugs to our all-new FlatZilla bug tracking interface, which automatically marks every user-submitted bug as WONTFIX, thereby improving our metric of closing time on bugs and demonstrating Agility as we continue to bring the Web forward."

  17. Re: Chrome by Anonymous Coward · · Score: 0

    Hi. I build firefox from source and call it Firefox all the time. So does the browser, because I enabled the --enable-official-branding flag in my build script.

  18. If they would FIX bugs, this would not happen by swschrad · · Score: 1

    Mozilla has a nasty habit of warehousing bugs that can't get fixed with the wave of a hand. that's why I quit the thing for Chrome a long time ago.

    --
    if this is supposed to be a new economy, how come they still want my old fashioned money?
    1. Re:If they would FIX bugs, this would not happen by niftymitch · · Score: 0

      Mozilla has a nasty habit of warehousing bugs that can't get fixed with the wave of a hand. that's why I quit the thing for Chrome a long time ago.

      There is a rumor that the hack was from a couple personal residences
      commuting distance from NATIONAL SECURITY AGENCY (NSA) HEADQUARTERS.

      But that could be someone pulling yer leg.

      It does tell me that layers of authentication and security for
      companies and agencies very much needs attention.

      We have an Email server that apparently contained email
      at multiple levels. We have Snowden sitting at a desk able to
      take screen shots of anything he cared to. We have hacks
      of federal personnel files, Target and more...

      Sadly Windows 10 could be an improvement but it does put
      critical keys in the hands of a single company. But early inspection
      of policy enforcement has discovered nothing to scream about.
      News at 11:00 on the MS thing....

      This is fire season on the Calif West coast and there are many many bells ringing
      up and down Silicon valley. There is also a run on ear plugs.

      --
      Truth is stranger than fiction, but it is because Fiction is obliged to stick to possibilities; Truth isn't. Mark Twain.
  19. And tonight, somewhere, an NSA agent ... by davidwr · · Score: 2

    ... is crying.

    --
    Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
  20. translation by Anonymous Coward · · Score: 0

    since it was a user password that was stolen and the bugzilla accounts weren't using two-factor authentication.

    we're idiots.

  21. Re: Chrome by Anonymous Coward · · Score: 0

    So how DID you manage to build the closed source DRM modules that are required if you want to officially call your final product "Firefox"? Or did you just download them and use them that way? Firefox these days is exactly as open as Chrome is: you can build something that's almost the real thing from source, but you'll be missing "essential" components.

  22. Is the hacker is gay? by Anonymous Coward · · Score: 0

    Is the hacker gay ? That should be only question they are asking now.

    If it was a womyn, she should be given an award.

  23. When SJW diversity trumps competency... by sethstorm · · Score: 1

    ...this kind of thing will happen. Hopefully they're competent enough to fix it.

    --
    Twitter supports and protects racists - by smearing their critics with the "Hate Speech" label.
  24. Re: Chrome by Anonymous Coward · · Score: 0

    No open source project ever has let people use the exact same name for their fork due to trademark, and just outright the confusion it would cause..

  25. Re: Chrome by Anonymous Coward · · Score: 0

    Except for Linux.

  26. Funny that they made the FAQ a PDF by Anonymous Coward · · Score: 0

    The one bug that is known to have been exploited is a pdf.js vulnerability where a script can search and upload local files. Are they trying to check if it's really fixed?

  27. Poor Mozilla can't catch a break by Anonymous Coward · · Score: 0

    Other then the die hard extension lovers who have always loved Firefox. I am not sure who else really thinks Firefox is worth even having on a device? Bugzilla
    is a joke anyway and I see plenty of bugs get ignored which is why Firefox is so not loved by many anymore. How can you do so many updates and not really fix much?

  28. Re: Chrome by amorsen · · Score: 1

    The Fedora build of Firefox is certainly built from source. It is still called Firefox.

    Fedora is discussing whether it is feasible to continue with Firefox-branded Firefox due to the new signed-addon policy. But for now, you can certainly get your open source Firefox fix that way.

    --
    Finally! A year of moderation! Ready for 2019?
  29. Re:Chrome by Lennie · · Score: 1

    And without Firefox lots of things Chrome/Chromium/Opera doesn't get to be standards.

    Because it's Firefox (gecko) and Chrome/Chromium/Opera (blink) are ahead of the pack. You need at least 2 browser (engine) implementations to make a standard.

    I would prefer multiple open source implementations and standards and not just a single open source implementation.

    Standards is the only way how we can get rid of things like Flash.

    --
    New things are always on the horizon
  30. "Breached" by Linkreincarnate · · Score: 1

    In completely unrelated news their bank account was also breached when a literal ton of money was deposited by Five Eyes.

  31. Re: Mozilla has to do a full infrastructure review by Anonymous Coward · · Score: 0

    Why isn't this marked funny?

  32. Re: Chrome by Gerv · · Score: 1

    The code for the DRM module Firefox uses is not part of the Firefox build system, but is downloaded at runtime. This can be done whether it's a Firefox built by Mozilla or not. So the DRM question has no bearing on whether you can call your version Firefox or not.

    This series of blog posts: http://blog.gerv.net/2010/01/p... explains why Mozilla doesn't let just anyone call their modified version "Firefox".

    Gerv