Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

10-Day Patch Guarantee Not Mozilla's Policy

Posted by kdawson on Mon Aug 06, 2007 09:33 PM
from the pajama-party-policy dept.
narramissic writes "Mozilla has officially backpedaled from a pledge made at Black Hat by the company's director of ecosystem development, Mike Schaver, to fix any critical security bugs in the browser within 'Ten ****ing Days.' On Friday, Mozilla security chief Window Snyder wrote in a blog posting that the 10-day pledge is not Mozilla's policy, saying 'We do not think security is a game, nor do we issue challenges or ultimatums.' And today, the open source browser maker issued a statement retracting the pledge."
+ -
story
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • It's Shaver (Score:5, Informative)

    by Anonymous Coward on Monday August 06 2007, @09:36PM (#20137727)
    And he's already explained how his comment got out of hand [off.net] and what he really meant by it.
  • For me, I always thought that Mozilla was a small and nice open source company. These days, it feels to me as if Mozilla is starting to blend into the corporation scene just like any other evil corporation. The whole Firefox naming debacle on Debian, and now this. Now that they're controlling a big market of the web browsers space, should we continue trusting them? Would it be time to look at Konqueror or other browsers?
    • I don't think that that follows. They've made a few mistakes, and this was one of them. They shouldn't make ultimatums like that. That said, I have a feeling that they'll continue to be a lot more responsive on the patching front than Microsoft, and I think that the point has been made, even if they won't stick to a set time-line.

      The Debian thing is not a strike against Mozilla. Their stance is correct and clear. You can't have someone else using your trademark to cover something that they are supporting. If the Debian team introduces a bug or something into their build of Firefox, Mozilla's brand will suffer. That's why Mozilla wanted Debian to rebrand it.
      • by Anonymous Coward on Monday August 06 2007, @10:09PM (#20137993)
        Yeah, that explains why all those Linux(TM) distributions can't use the trademark "Linux" - after all, almost all of them patch the Linux kernel. Or why the distributions have to rename KDE or GNOME. Or any other piece of open source software.

        No, the reason Mozilla forced Debian to rename Firefox is even stupider than that. Debian fixed their build process. They didn't actually patch the browser. They simply corrected the build process to work under Debian. That was enough to prevent them from using the name "Firefox".

        Personally I can't wait until WebKit and Konqueror finish remerging code. Once Konqueror gets a Windows build, it's game-over for Firefox. It's a better browser - it just hasn't, until recently, run on Windows.
        • The Mozilla folks were being silly about the use of their trademark.

        • Once Konqueror gets a Windows build, it's game-over for Firefox. It's a better browser - it just hasn't, until recently, run on Windows.

          I happen to agree it's a much better browser, and a very good file manager, among other things, BUT there's nothing to make me think that once it becomes popular enough, the exact same thing won't happen to it. Popular software gets sucked into the corporate venus fly trap faster than a trailer park gets sucked into a tornado. The nice thing about all this open source though, is that nobody can claim exclusivity. We can always make something similar, a little bit better, and put a different name on it. I was under the impression that's the idea behind GPL and BSD and Creative Commons, etc. to begin with. So we can simply forget about the guy who takes a wrong turn, instead of following him over the cliff.
        • by _Sprocket_ (42527) on Tuesday August 07 2007, @12:32AM (#20138743)

          No, the reason Mozilla forced Debian to rename Firefox is even stupider than that. Debian fixed their build process. They didn't actually patch the browser. They simply corrected the build process to work under Debian. That was enough to prevent them from using the name "Firefox".
          Is it just that, though? Before the whole Icedove rename, I had two copies of Firefox on my Debian desktop. One was the Debian package. The other was from Mozilla. I had the Mozilla version because something broke in the Debian package. It had something to do with my laptop's Xorg config (I have a config that allows dual screens when docked and just the single screen when not). When it wasn't docked, Debian's Firefox would run but wouldn't show. The Mozilla version came up without a problem. I could never figure out why (wish I could - then I would have filed a bug report).

          I bring this up because this was going on around the same time the whole rename issue was getting a lot of attention. It seemed to me that Debian was introducing changes that Mozilla wasn't - as demonstrated by my own odd behavior of the two Firefox installs. Of course - I don't know enough about the bug I had or the issue in general to really know for sure. Maybe someone else can take a swing at it?
        • by trifish (826353) on Tuesday August 07 2007, @07:57AM (#20140705)
          The thing is, if you allow different products from different sources to be publicly distributed under a single trademarked name, the trademark becomes dilluted and can be declared invalid (by court, trademark dispute board, etc.) That's what the law says, there's not much you can do about it.

          BTW, that's why the "Linux" trademark wouldn't surive a test in court now. It doesn't identify a single product from a single source. It's dilluted and invalid.
        • Re: (Score:3, Informative)

          Yeah, that explains why all those Linux(TM) distributions can't use the trademark "Linux" - after all, almost all of them patch the Linux kernel. Or why the distributions have to rename KDE or GNOME. Or any other piece of open source software.

          Actually, all those guys have to get a license for the Linux trademark from Linus - or whoever Linus appointed to manage the trademark. It's just that there are not that many strings attached to said license.

          Mozilla is certainly free to license their Firefox tradem

      • by Kjella (173770) on Monday August 06 2007, @10:25PM (#20138113) Homepage
        The Debian thing is not a strike against Mozilla. Their stance is correct and clear. You can't have someone else using your trademark to cover something that they are supporting.

        That wasn't really the problem, I think there were a few disagreements on some defaults Debian had set, but in general I don't think Mozilla would have any problem rubbing-stamping it like they do with other distros' versions. Where it really broke down wasn't really a practical problem, it was more policy vs policy.

        Mozilla's policy is that they must approve anything using the trademarked name and logo, so that they can stop bad versions with spyware, adware and such.
        Debian's policy is that they must be able to apply security parches immidiately without approval from any third parties.

        In themselves, both admirable policies but the road to hell is paved with good intentions. In practise there wouldn't have been any problem getting security patches into Debian's version in a timely fashion with Mozilla's blessing, but one of the policies would have to make an exception. Neither Mozilla nor Debian were willing to bend on their principles, and so Iceweasel was born. Yes, it's a policy aberration but I don't feel one side was being more unreasonable than the other.
        • Re: (Score:3, Informative)

          There has been much information about this. The reality is that much of the information is wrong or only partially complete. There were at least 3 problems, only one of which did not seem resolvable.
          • Debian has a policy of not introducing new upstream versions into a stable release. Instead, any necessary security changes are backported. MoCo's policies tend to counter this. But this was not too major an issue, and could likely have been resolved.
          • Debian distributed Firefox with some patches. MoCo's policy
          • by Kjella (173770) on Tuesday August 07 2007, @01:29AM (#20138959) Homepage
            The real problem was that Debian was using the Firefox logo with modified Firefox code (as in: Debian patches not in official Firefox build), witch is against Mozilla policy.

            That's where it started, not where it ended. It went something like:
            Moz: "You're using some mods to Mozilla with the official logo, stop it."
            Deb: "Ok, but some of these changes we want/need to do."
            Moz: "Submit them to us and we'll approve them. Oh and those won't go through."
            Deb: "Ok, we can drop those. We'll sumbit the rest."
            Moz: "Good. And you must also submit any updates to us first."
            Deb: "In general ok, but security patches we'll push immidiately."
            Moz: "No, you must. Mozilla policy."
            Deb: "Not acceptable. Debian policy."

            I think my post was fairly accurate only I didn't include the backstory, there was dialog to fix the rest but the policies were the deal-breaker.
      • Yes, because a bug in the Debian copy of Firefox will totally destroy the Mozilla brand everywhere.
    • by tm2b (42473) on Monday August 06 2007, @11:04PM (#20138315) Journal

      These days, it feels to me as if Mozilla is starting to blend into the corporation scene just like any other evil corporation
      Somehow you edited out the rest of this sentence. Here, I'll fix it for you:

      These days, it feels to me as if Mozilla is starting to blend into the corporation scene just like any other evil corporation who gives away their source code for free.
      HTH. HAND.
      • You've never tried to work with wu-imapd or daemontools, have you? The restrictive licensing on both of those not only prevents forking, but prevents the application of packaging or internal compatibility patches.
    • It's a mistake to put your unconditional trust in any organization or institution, no matter what branding or happy face they show to the world. Organizations follow their own inner logic and patterns and have their own psuedo-biological agendas. I'm not saying that organizations are inherently evil, rather that they are inherently amoral. Nor am I suggesting that they have a mind of their own. Rather, what passes for a mind is a sort of weighted group consensus made up of individuals and blocs within the o
    • "My band, they sold out MAN. What a bunch of sellouts MAN. Before I was the only cool person to like this band, and now that they haven't changed and have become people, I can't use that to make myself seem really cool MAN."

      Ugh. You just liked FF because no one was using it. You'll leave anything that becomes popular, because popular things can't be cool, MAN.
  • On Friday, Mozilla security chief Window Snyder wrote in a blog posting that the 10-day pledge is not Mozilla's policy, saying 'We do not think security is a game, nor do we issue challenges or ultimatums.'

    Upon hearing the news of this "flip-flopping," President Bush confidently stepped in for the Mozilla group and challenged the black hats to "bring it on."

  • by infonography (566403) on Monday August 06 2007, @09:44PM (#20137793) Homepage
    Making that sort of pledge is rather rash. I am not saying it can't be done, but I don't see it as simple to fix anything anytime.

    Questions you have to ask are;

    Is it really a bug?

    Can it really be reproduced?

    etc etc

    Being timely in bugs is good. But not all crashes are the result of bad software. You have to be sure your fix doesn't turn another thing into a bug. They would soon end up chasing after every little bit of dust and lose sight of their real work.
    • Also, how seriously messed up is it? A security bug can either be a detail, or it can throw the entire architecture behind a system into question by exposing flaws inherent in the fundamental way it works. Just look at all these AJAX problems we're having. A security hole might even force a company to shut everything down while they do a massive panicky conversion of tons of code. And bug fix code is usually the shittiest code of all; I bet half these patches tear open more holes than they close.
  • Clarification (Score:5, Informative)

    by nacturation (646836) <nacturation@gmail. c o m> on Monday August 06 2007, @09:44PM (#20137803) Journal
    On this blog entry [ckers.org] Mike Shaver clarifies:

    (I thought I commented here on Friday, but I was working from my Blackberry, which is not especially web-friendly. Bleh.)

    Glad you enjoyed the party, Robert. To clarify, I was making a personal commitment, not a Mozilla one, that you could redeem that card if there was a vulnerability that you believed needed to be turned around in 10 days. I didn't consider at the time that it would be taken as a Mozilla policy statement -- even *I* don't make new policy announcements at late-night parties in Vegas :) -- but it seems to have been read that way, which I can understand in hindsight. I'm sure I'll be answering for my potty mouth and apparent lack of clarity for a while...
    Also spelled out on his own blog [off.net].
     
  • Easy solution... (Score:5, Insightful)

    by Actually, I do RTFA (1058596) on Monday August 06 2007, @09:57PM (#20137897)

    My mayor ran on the promising of "fixing any pothole within 24 hours of discovery." Of course the roads are still filled with potholes. Turns out, it was 24 hours of any confirmed pothole, which is trivially easy as the pothole confirmation team is as slow/backed up as the pothole filling team.

    • by myowntrueself (607117) on Monday August 06 2007, @10:02PM (#20137947)
      My mayor ran on the promising of "fixing any pothole within 24 hours of discovery."

      Dude we could do with that kind of attitude here.

      Except it'd be more like "I have a pot *hole* right here. In my pipe. Please fill it in. With pot. Thanks."
        • by Gazzonyx (982402) on Monday August 06 2007, @11:45PM (#20138505)
          I don't smoke any more, but of my 'IT type' friends who still do (all in their early to mid 20's, mind you - 1 is 21 working on his masters), well... I spent the night working on my Solaris server trying to get NFS, LDAP, MySQL and Samba to play nicely with a BSD box, Mac, XP, and Gentoo inside segmented routed networks. Granted, I failed miserably, but I'm fairly sure my friends spent their night sharpening their skill set by getting high, eating munchies, and watching Sponge Bob's Square Pants before passing out at 10pm.


          As an aside, it always seems the network and hardware geeks are the ones who smoke pot, and the database and BSD guys who like their vodka. The C/C++/Java programmers (this is my category, usually) are chain smokers - Marlboro Reds in a soft pack style, and caffeine junkies. How many of you have a Mountain Dew can that you're drinking next to an empty Mountain Dew can - and both are still cold to the touch? Yeah - all the programmers.


          And the Mac guys generally seem to be clean cut replicas of Jeff Goldblum, for the most part. They're health conscience, and probably taking on a good number of sunshine units from those freakin' 45 inch MacBook Pro screens as they tend to be fans of irony. Mac guys also probably currently have a half gallon of water, in a jogging harness, on their desks right now... probably the cleanest desks on /. for that matter.
          Oh, and I think the Amiga guys are in to acid or something - that's why they've been in their garages for the last 15 years hacking away. Poor guys don't even know their wife unplugged the monitor 3 years ago.

        • Re: (Score:2, Insightful)

          by Anonymous Coward
          Most of the comments come from stoned or drunk coders really. You can't be in a sane state of mind to think that posting to slashdot is a good idea.
        • So, how many people on Slashdot smoke pot, anyways? I'm kind of curious how prevalent it is in the IT industry.

          Is it possible to keep your mental edge and smoke pot at the same time? That should really be an Ask Slashdot...
          It worked for Mr. UK-NASA-UFO-Hacker. It could work for you.
    • My mayor ran on the promising of "fixing any pothole within 24 hours of discovery." Of course the roads are still filled with potholes. Turns out, it was 24 hours of any confirmed pothole, which is trivially easy as the pothole confirmation team is as slow/backed up as the pothole filling team.


      You must be from Houston...

      I've actually seen construction crews create potholes and then not fix them. And the heavy metal sheets they place on the concrete roads are worse than the original hole.
  • by thanksforthecrabs (1037698) on Monday August 06 2007, @09:59PM (#20137921)
    ...we still have companies like Google that can set good examples.
    • On most days. Google's cooperation with Chinese censorship is troubling: so is the lax overall security of their mail services, which are easily obtained without a warrant or verifiable judicial review under the US "Patriot Act" legislation. So I do wonder at what happens behind closed doors there.

      Their overall reputation is good, but let's be clear that they're aggressive.
  • by Locutus (9039) on Monday August 06 2007, @10:24PM (#20138093)
    to hold up to the 10-day pledge but in the end, if something major holds back a fix, are we all going to bash them for missing the 10-day pledge? I doubt it. After all, we are not talking about Microsoft. These people are trying to do the best job possible and don't have to consider how the browser fix would interfere with some feak'n gumball machine driver that has IE code in it.

    But she's right in that they really shouldn't be making statements like that without having discussed this with their team and doing so could be considered a challenge to others. Not something you want to do with a company willing to pay billions just to purchase marketshare let alone how much they'd be willing to put into ads and other FUD should a fix take 241 hours.

    LoB
  • by shish (588640) on Monday August 06 2007, @11:07PM (#20138341) Homepage
    Are the censored four letters "work"?
  • Well Doh' (Score:3, Insightful)

    by rdebath (884132) on Tuesday August 07 2007, @02:48AM (#20139277)
    The stupid thing is it is a statement of policy, it's just that it's not in marketing speak.
    If your brother says something like that you know you'll get either that or a good excuse. The good excuse is always an unwritten option, it's just with professional liars that you have to tie them to the every single written word because trying to pin them to a statment is like trying to pin live eels!
    • Firefox is not all open source projects. Mozzila may have grown to big to fast by I hardly see the entire foss taking the stance that end users should fix bugs.
    • I was wondering the same thing.

      Then I read he was at a Pajama (pyjama?) party and it all made sense.