Slashdot Mirror


Privacy Leak in Mozilla and Mozilla-Based Browsers

Mike S. writes "Mozillazine has pointed users to this story at ZDNet UK which breaks the news about a privacy bug discovered in in all Mozilla builds up to and including 1.2a as well as browsers based on Mozilla such as Netscape 6/7, Chimera and Galeon. The bug allows a web site to track where you're going when leaving the site whether you use a link, a bookmark or type a URL into the address field. This page has a demonstration of the bug and instructions on patching it via a user.js file."

357 comments

  1. The most disturbing thing about this... by Corvaith · · Score: 5, Interesting

    ...is that the bug has apparently been a known one for months, and still hasn't been repaired.

    I love Mozilla. I use Mozilla. This just troubles me greatly. Even now that it's known, I haven't heard anything about a fix. Hopefully it'll be arriving shortly, because I like my privacy.

    1. Re:The most disturbing thing about this... by jmcnamera · · Score: 4, Insightful

      If this bug has really been known for months, are we hypocritical to bash others (always MS) for late fixes?

      Bugs should be publicized immediately so fixes will happen sooner. It's good to first inform those who are responsible for the code so they can have a heads up, but months (if true here) is too long to wait.

      --
      this is not a sig
    2. Re:The most disturbing thing about this... by VoiceOfRaisin · · Score: 1

      ah. the magic of open source i keep hearing about. fast, instant fixes..

    3. Re:The most disturbing thing about this... by Corvaith · · Score: 2

      Quite possibly hypocritical... though, in general, I don't think this is quite the same severity as many of the MS ones seem to be. I'm not even bothering to apply the patch, at the moment, and I'm not so much upset as baffled. Usually, Mozilla's bugs don't stay around this long.

      Which is not to say that they don't frequently disappear and reappear regularly as the flaws are hammered out, but for something to be completely untouched after this long is certainly not usual.

    4. Re:The most disturbing thing about this... by Anonymous Coward · · Score: 5, Insightful

      > This just troubles me greatly.

      Fine, this is not how you'd expect it to work.

      But, GIVE ME A BREAK. Privacy issues on the Web are legend. Cookies, refer, hidden fields, the entire body of software we know as "IE", the list goes on and on and on.

      So, by some new "stupid browser trick" you can now see where people are going -- not just where they've come from (as has always, forever, been the case).

      Oh my.

      If you are worried about "privacy" then you have been using an appropriate "junk busting" proxy from day one.

      If you are not using such a proxy, then you are not now, and never have been, seriously worried about privacy. And, this "horror of horrors" is no more an issue to anyone than the Referrer field.

      This sounds more like Microsoft Marketing pouring though a Bug Base and using the media to turn a mole hill into a mountain.

      Should it be fixed? Yea. So should Referrer be removed from existence. So should alot of much more pressing privacy issues be outright abolished.

      So go back to sleep. If you weren't worried about this yesterday, then there is no reason for you to be worried about it today.

    5. Re:The most disturbing thing about this... by RoundSparrow · · Score: 2, Interesting

      Uh... you need to download the Source Code, not the binary - if you want to review and fix things.
      Last I checked, I can't download Internet Explorer source code and do my own fixes or add my own features.
      There is a difference, take some responsibility.
      People get hung up on open source and forget that the only real difference is the source. Paid support and paid staff often does have benefits.

    6. Re:The most disturbing thing about this... by Anonymous Coward · · Score: 0

      Who cares? This is as dangerous as the HTTP referer.

    7. Re:The most disturbing thing about this... by xswl0931 · · Score: 1

      The great thing about Open Source is that you can fix the bug yourself. So get to it!

    8. Re:The most disturbing thing about this... by minaguib · · Score: 2, Insightful

      Any developer who puts the username and password in a URL should be shot. And any user who sees their password in the URL in plainsight and doesn't complain, or stop using the services, shouldn't be allowed near a computer to begin with.

    9. Re:The most disturbing thing about this... by cpeterso · · Score: 4, Funny


      Mozilla is open source. Why haven't YOU fixed this bug yet?

    10. Re:The most disturbing thing about this... by Anonymous Coward · · Score: 0

      It dosen't trouble me at all.

      The only practical application of this is to tell what pr0n sites you visit, and if your clicking a add.

      Neither really bother me in the least.

    11. Re:The most disturbing thing about this... by Anonymous Coward · · Score: 0

      That's the only answer, huh?

    12. Re:The most disturbing thing about this... by Zigg · · Score: 2

      It seems to me that privacy bugs often get short shrift in Bugzilla. I believe we're still waiting to get inline loads blocked within mail messages (i.e. for web bugs).

    13. Re:The most disturbing thing about this... by Anonymous Coward · · Score: 0

      This is the precise attitude that scares Corporate America.

      Corporate America wants a product. They want it supported. They don't want to become responsible for the product.

    14. Re:The most disturbing thing about this... by SN74S181 · · Score: 2, Insightful

      Usernames and passwords to web sites can be embedded into the URL, and encrypted. This still allows anybody who grabs the URL to get onto a 'secured' page on said website. The BDSM Web Site alt.com uses such a mechanism, and is full of people with all sorts of kinky interests, including 'vulnerable' sexual submissives. The alt.com chatroom uses URL-based 'passwords.' For whatever reason they prefer that to a cookie-based security scheme.

    15. Re:The most disturbing thing about this... by Anonymous Coward · · Score: 0

      Try telling that to Slashteam.

      -klerck (logged out because I've posted more than two comments in the last 24 hours)

    16. Re:The most disturbing thing about this... by Anonymous Coward · · Score: 0

      You have to pay money for that.

    17. Re:The most disturbing thing about this... by Anonymous Coward · · Score: 0

      Because it was kept private for months so people wouldn't exploit it? They should have remembered -- no security through obscurity...

    18. Re:The most disturbing thing about this... by Anonymous Coward · · Score: 0

      Yeah. Good for you. Now crawl back under the rock you came from and let normal people worry about this perfectly legitimate privacy problem, mr. Transparency-all-the-way.

    19. Re:The most disturbing thing about this... by Anonymous Coward · · Score: 0

      Last I checked, I can't download Internet Explorer source code/I.

      Don't worry. It's over your head anyway.

    20. Re:The most disturbing thing about this... by Anonymous Coward · · Score: 0

      Is it me or do more of the posts on Slashdot of the have the distinct odor of astroturf? (jcmcnamara below for another example)

    21. Re:The most disturbing thing about this... by Fastolfe · · Score: 1

      Here, why don't you visit this URL I have here and then click on the auto-login bookmark you have for Slashdot.. There are issues here.

    22. Re:The most disturbing thing about this... by Anonymous Coward · · Score: 0

      Hell, I found this back in 1999. All browsers, except MSIE 5.5, have issues with the implimentation of document.referrer.

      In MSIE 4.0 document.referrer gave you nothing... nothing at all, just a null value.

      In MSIE 4.01 document.referrer gave you the last item, but you could also reference this through the history(-1) value, and you could also get the history(-2,-3,-4...) for a while. One of the security patches fixed this, but said nothing about it.

      Of course, when I was doing this what was I doing? Trying to figure out how to track online users. Go figure.

    23. Re:The most disturbing thing about this... by Anonymous Coward · · Score: 0

      I get around this bug by just using IE, still the beat browser on the planet.

      (Not a troll BTW, I honestly believe this.)

    24. Re:The most disturbing thing about this... by Gerv · · Score: 1, Redundant

      I believe we're still waiting to get inline loads blocked within mail messages (i.e. for web bugs).

      Your annoyance it totally righteous, given the massive effort you made to get this feature implemented. Right? :-)

      View | Message Body As | Simple HTML

      Gerv

    25. Re:The most disturbing thing about this... by Anonymous Coward · · Score: 2, Informative

      > ...is that the bug has apparently been a known one for months, and still hasn't been repaired.

      Oh, give me a break. This flaw is so minor that I am not even going to bother to install the fix (I will wait for the next Mozilla release).

      This bug allows a website to see the URL of the next site you are going to. It is little different from what all browsers have always done, when they provide the URL of the site you came from. If either one worries you, then just click on "home" before typing in a URL.

      So how "disturbed" should you be? Let's put this case into perspective. Let's look at some of the IE security holes that Microsoft is currently sitting on, in some cases for over six months...

      There are currently _19_ unpatched security holes in IE.

      Here are some samples:

      > Who framed Internet Explorer
      > Description: Cross-protocol scripting, arbitrary command execution, local file reading, cookie theft, website forging, sniffing https, etc.


      > MS JVM native method vulnerabilities
      > Description: A collection of at least 10 different vulnerabilities in the MS JVM, escaping the sandbox, local file reading, silent delivery and execution of arbitrary programs, etc.


      > WMP Stench
      > Description: Silent delivery and installation of an executable on a target computer


      > Java XMLDSO base tag
      > Description: Arbitrary local file reading.


      > delegated SSL authority
      > Description: HTTPS spoofing, man-in-the-middle attacks, etc.


      > document.domain parent DNS resolver
      > Description: Improper duality check leading to firewall breach


      > CTRL-key file upload focus
      > Description: Local file reading, downloading and executing arbitrary code.


      > IE https certificate attack
      > Description: Undetected SSL man-in-the-middle attacks, decrypting SSL-encrypted traffic in realtime.
      > Published: December 22 2001 ( Stefan Esser )
      > Published: June 6 2000 ( ACROS )
      > Status: Initially fixed in IE4 and early IE5s by MS00-039, re-introduced by a later patch.


      Arbitrary command execution? Local file reading? Escaping the sandbox? HTTPS spoofing? Firewall breach? Decrypting SSL-encrypted traffic? Yikes!!!

      Of the nineteen open security holes in IE, nine of them allow binary executable code to be run on your computer.

      Compared to that, this Mozilla bug is so minor that it barely deserves mentioning.

    26. Re:The most disturbing thing about this... by sheriff_p · · Score: 2

      I think you misunderstand a few things about the interweb...

      Firstly, the referer [sic] field only contains the URL of a *referring* page, not just any page you happened to be on before. Why? Because sending non-referring page URLs is an invasion of privacy. Furthermore, IE and Mozilla both stop you actually retrieving this data from Javascript, even though you can pass it to certain Javascript functions, showing that again this privacy is respected.

      May I suggest you find out how your interweb browser works before posting in the future? Oh, and read the RFC: it's Referer field, not Referrer field.

      --
      Score:-1, Funny
    27. Re:The most disturbing thing about this... by Anonymous Coward · · Score: 0

      Because I only know how to program in Visual Basic.

    28. Re:The most disturbing thing about this... by Anonymous Coward · · Score: 0

      hello, i am a MS developer on the Internet Explorer project, and i can assure you our code is very well annotated, even a child could understand it. in fact, it may suprise you to learn that 4 of the 6 developers on the project under 10 years old.

    29. Re:The most disturbing thing about this... by Izeickl · · Score: 2, Insightful

      This is his point, open source is praised because anyone can view the source code and fix anything thats broken...you just proved how untrue this is in reality.

    30. Re:The most disturbing thing about this... by trezor · · Score: 1

      So should Referrer be removed from existence.

      You're not a web-developer are you? When creating massive sites I, for once, prefer to check the referer, to know where to return, when I've been trough tons of pages and security precations, because users are too stoopid get it right the first time.

      Just because it can be abused, doesn't mean that it doesn't have any legitemite uses as well.

      --
      Not Buzzword 2.0 compliant. Please speak english.
    31. Re:The most disturbing thing about this... by BigBir3d · · Score: 2

      Uh... maybe he/she is like me, a total and complete non-programmer type. the only reasons i have ever used source is to 'optimize ofr my system', or because there was no other choice.

      i am one of those people looking for a desktop alternative to windows. i don't program. i don't read code. i don't know how. i don't want to, i just want it to work.

      not everyone who uses open source programs or operating systems should be checking/fixing code. that would mean that there is a relatively small, stagnant (ie not growing) population of users. this is not what we want, right?

    32. Re:The most disturbing thing about this... by briglass · · Score: 1

      why was this story a "privacy issue" as opposed to a "mozilla issue"? not that i don't read every story, anyway... but seems like it should be both or instead mozilla. lates

      --

      ----
      "Those who quote others are more likely to one day be quoted" -Tom Planter
    33. Re:The most disturbing thing about this... by prgammans · · Score: 2, Insightful

      Open source allows anyone to fix a problem. Though the amount of time and effort that it will take you to do the fix is something which you have to way against the size of the problem.

      Closed source you can't fix it no matter how big a problem it is.

      I.e. what is the cost of the problem, would it cost you more to fix it than living with it.

    34. Re:The most disturbing thing about this... by Kanasta · · Score: 2

      Are you suggesting, that as Mozilla is open source, that users have no right to complain about major issues such as this?

    35. Re:The most disturbing thing about this... by Anonymous Coward · · Score: 0

      > You're not a web-developer are you?

      Yea, actually I am. And for some of the few paid subscription sites that are actually profitable.

      Yea, actually I see any number of less than well considered "user management" schemes out there. All kinds of "stupid browser tricks" are out there, but it doesn't mean they can't be misapplied. "IT WORKS" rarely means "IT'S RIGHT".

      Did I mention "subscription sites"? You know, where people pay for passwords and I really, really, have to know what I'm doing. If I don't keep it all utterly safe, user-friendly, browswer agnostic, ad-nausium -- then we don't get paid.

    36. Re:The most disturbing thing about this... by RoundSparrow · · Score: 1

      Yes, but you can hire three different people to try and have the code fixed...

      With MS - you can only hire one company.

      The difference between open source and closed source - IS THE SOURCE! Nothing else, quality is not assured - just the chance that you have more control.

  2. Yawn. by Fished · · Score: 0, Insightful

    Should it be fixed? Yes. Is it a big deal? Not unless you're doing something nasty. Bottom line is that I don't really care who knows what websites I go to, because I keep my web accesses legitimate and vanilla. Who's got time to crack, pr0n, or spod when trying to raise a family? Geesh.

    --
    "He who would learn astronomy, and other recondite arts, let him go elsewhere. " -- John Calvin, commenting on Genesis 1
    1. Re:Yawn. by agentZ · · Score: 3, Insightful

      Doing illegal things isn't the only way this could be a problem. For example, let's say I use the
      Google Browser buttons after reading your web page to execute a search. I may not want you to know that after reading your web page I executed a search for "anonymous STD testing Chicago."

      It's not "nasty" per se, but I sure don't need to broadcast that to the world.

    2. Re:Yawn. by Anonymous Coward · · Score: 0, Funny

      Um, excuse me but you must have sex (with another person) in order to contract an STD. Therefore, I think you are completely safe and will be for a long long time.

    3. Re:Yawn. by Anonymous Coward · · Score: 0
      Who's got time to crack, pr0n, or spod when trying to raise a family?

      me

    4. Re:Yawn. by jhunsake · · Score: 0, Offtopic

      That, or sit on a public toilet.

    5. Re:Yawn. by jnana · · Score: 3, Funny

      Did your wife buy that excuse when you tried it on her?

    6. Re:Yawn. by noshellswill · · Score: 0

      But whatever, who knows what - it should be your call, who knows what. Right?

    7. Re:Yawn. by NineNine · · Score: 2

      This same post under an article that says "IE has a security leak" would be modded to -1. It IS a big deal. Especially, since it STILL hasn't been fixed. The responses would say, "This wouldn't happen under Open Source". Somebody would fix it." Well, it IS Open Source, and it still hasn't been fixed.

    8. Re:Yawn. by superyooser · · Score: 1
      In the case of most Westerners, I agree with your sentiments. However, people in non-free countries could have legitimate concerns. You've probably seen the stories here on Slashdot about how the communist government of China had gone so far as to ban Google. As you know, countries run by communists, Muslims, and other types of oppressive rulers persecute people for doing many activities that would be considered perfectly legal and ethical in Western countries. For example, if somebody in [oppressive country] were on the government web site and typed in your link, www.extremehope.org, the government could track it, and that person might get in a heap of trouble just for trying to access such information.

      Also, keep in mind that there are lots of people fighting for just causes (various freedoms and rights) that are opposed by the evil ruling powers in their countries (China, Taiwan, Tibet, Zimbabwe, etc.). The Internet can be a powerful tool for garnering outside support for revolution. The most famous example, I think, is the Free Tibet Campaign.

      Granted, even without the bug they could track this particular browsing behavior by using other means. This bug really isn't a big deal. I'm just taking you to task that only "bad" people should be concerned about privacy. In the U.S., I generally agree with you. But if someone's ideas, which may be considered "legitimate and vanilla" to us, are frowned on by his corrupt government, he can possibly look forward to having a noose around the neck or a bullet in the head (or worse). And there's usually no trial beforehand, except maybe a kangaroo court). When a totalitarian government wants to end a dispute, it always prefers the gun over the gavel.

    9. Re:Yawn. by koh · · Score: 1

      -- In the U.S., I generally agree with you.

      Last time I checked, the countries you consider as suffering from "evil rulings" (China, Taiwan, Tibet et al.) didn't have the DMCA.

      --
      Karma cannot be described by words alone.
    10. Re:Yawn. by Anonymous Coward · · Score: 0

      Actually I just tried that exact search a number of times. It doesn't actually work! If you enter "anonymous STD testing Chicago." and then press the search button the exploit says the following: You went to the following url after your last visit to this page: url=http://members.ping.de/~sven/mozbug/refcook.ht ml

      What really bothers me is when I mispell a URL in IE and it goes to the MS search page and keeps track of how much of an idiot I am.

    11. Re:Yawn. by superyooser · · Score: 1
      That is funny. Yeah yeah, the grass always looks greener on the other side of the fence, doesn't it?

      You need a broader perspective, my friend.

      If the U.S. was like said countries and you were a U.S. citizen, you might be receiving a flogging at this very moment for your criticism of your government. That is assuming that you are allowed to access /. in the first place.

  3. Dear Slashdot morons by rebrane · · Score: 5, Interesting

    Do not link to BugZilla from the front page. Not only is it extremely impolite to overload their system with a bunch of hits from people who have no actual interest in the page, but they have disabled links with a slashdot referrer anyway. I'm sure some clued person will go to the bug report and relay any pertinent information in the comments anyway.

    1. Re:Dear Slashdot morons by Anonymous Coward · · Score: 0

      But those of us who both play with our refer strings and are interested enough to follow the link totally deserve to see it.

    2. Re:Dear Slashdot morons by Neon+Spiral+Injector · · Score: 5, Funny

      Have they also disabled people leaving Bugzilla to go to Slashdot? Okay, I know that was bad.

    3. Re:Dear Slashdot morons by Anonymous Coward · · Score: 0

      what makes you think so butthead? Just because you think you are interested enough does not mean diddly. you don't *deserve* a thing since you are dealing with an open project with zero liability inferred...

    4. Re:Dear Slashdot morons by LegendLength · · Score: 1

      Ahh. Nothing brings out the trolls like a fresh Mozilla bug.

    5. Re:Dear Slashdot morons by Anonymous Coward · · Score: 0

      but they have disabled links with a slashdot referrer anyway.

      haha, I have referrer disabled, thanks to mozilla!

  4. Easy work-around for now by RPoet · · Score: 5, Informative

    People will tell you to disable Javascript alltogether for protection, but it's better to just disable the onunload event. Just put the following line into your user.js file:

    user_pref("capability.policy.default.Window.onun lo ad", "noAccess");

    You won't miss those ununload events anyway :)

    --
    "Oppression and harassment is a small price to pay to live in the land of the free." -- Montgomery Burns.
    1. Re:Easy work-around for now by RPoet · · Score: 0, Redundant

      Sorry, a space snuck into the line. It's supposed to read:

      user_pref("capability.policy.default.Window.onun lo ad", "noAccess");

      --
      "Oppression and harassment is a small price to pay to live in the land of the free." -- Montgomery Burns.
    2. Re:Easy work-around for now by packeteer · · Score: 2

      Slashdot has a bug with strings of chars longer than a certain amount. Look at my sig... that space is not there but nomatter what i do its always there. How do we get this fixed?

      --
      unzip; strip; touch; finger; mount; fsck; more; yes; unmount; sleep
    3. Re:Easy work-around for now by Anonymous Coward · · Score: 0

      It's not a bug, it's a feature...

      It's to prevent page widening posts.

    4. Re:Easy work-around for now by dbaron · · Score: 3, Interesting

      This workaround will only disable one of the ways the bug can be exploited (albeit the easier way to exploit it). Based on my reading of the bug, it can also be exploited through timeouts, although methods for doing so are probably less reliable.

    5. Re:Easy work-around for now by bcrowell · · Score: 3, Informative

      Where is your user.js file supposed to be (on Linux)? Slocate tells me I don't have one. Should I create one somewhere with only this line in it?

    6. Re:Easy work-around for now by xanadu-xtroot.com · · Score: 3, Interesting

      It's not a bug.

      This was the solution to a hack, actually (IIRC). The Page Widening Trolls (TM) like to make a string of text thousands of characters long so there's a real nasty side-scroll. By adding in that space every X nuber of characters, it becaome imposible for the trolls to make the window side scroll.

      Browse /. at 0 or -1, you'll still see some of them.

      --
      I'm not a prophet or a stone-age man,
      I'm just a mortal with potential of a super man.
    7. Re:Easy work-around for now by maw · · Score: 4, Informative

      You should have a file called prefs.js somewhere within your $HOME/.mozilla directory. You can set user_prefs there.

      --
      You're a suburbanite.
    8. Re:Easy work-around for now by JoeF · · Score: 1

      If you run an adblocker like WebWasher you can disable the onload and onunload events already. I do that by default.

    9. Re:Easy work-around for now by dbaron · · Score: 1

      The user preferences file should be
      ~/.mozilla///prefs.js

    10. Re:Easy work-around for now by dbaron · · Score: 1

      er, ~/.mozilla///prefs.js

      (Why don't < and > work when I select "Plain old Text"?)

    11. Re:Easy work-around for now by *xpenguin* · · Score: 0, Troll

      Or, instead of modding up this karma whore, you could read the last part of the page which tells you exactly the same fix.

    12. Re:Easy work-around for now by ocelotbob · · Score: 1

      RTL. You're going to have to create it in ~/.mozilla/$user/some_pseudorandom_string.slt (ignoring any spaces). I can't tell you the exact string because it will vary, but that should let you find it fairly easily.

      --

      Marxism is the opiate of dumbasses

    13. Re:Easy work-around for now by teslatug · · Score: 4, Informative

      better not to set them in prefs.js ,but in user.js (create new file if not there) as the settings in the prefs.js file might get overwritten

    14. Re:Easy work-around for now by superpeach · · Score: 3, Informative

      Yes, create one
      If you just use mozilla as it is then you create your user.js in ~/.mozilla/[your_username]/[some random directory name]/user.js - the path up to user.js should exist already if you have used mozilla, and hopefully only 1 with a wierd random name :)
      If you use galeon, then it goes in ~/.galeon/mozilla/galeon/user.js

    15. Re:Easy work-around for now by Capsaicin · · Score: 1
      Where is your user.js file supposed to be (on Linux)?

      Depends whether you're using Netscape, Mozilla, Galeon, whatever. It should be in the same directory as prefs.js, should be easy to find.

      find ~ -name '*.js'
      --
      Better to be despised for too anxious apprehensions, than ruined by too confident a security. --Edmund Burke
    16. Re:Easy work-around for now by jesser · · Score: 1, Troll

      Just because it's intentional, doesn't mean it's not a bug. The space-adding hack breaks code, breaks plain-text urls (exacerbated by the "Slashdot doesn't automatically turn URLs into links" bug), generally frustrates people, and can be fixed.

      Slashdot's use of tables for layout is the only reason "page-widening trolls" exist. If Slashdot used a simple layout or a CSS layout, a single wide post would not cause other posts to wrap off of the screen. Slashdot's use of tables also makes IE users wait for the entire page to load before they can read the first comment, but the space-adding hack is the most visible result of using tables for layout. See also: More reasons to avoid using tables for layout rather than only using tables for tabular data.

      --
      The shareholder is always right.
    17. Re:Easy work-around for now by BlueGecko · · Score: 2

      You need to create one. The file is intentially not created by default, as it's only for your own prefs. Find yours prefs.js file and put your user.js file beside it. This prevents you from having to modify the prefs.js file directly.

    18. Re:Easy work-around for now by Anonymous Coward · · Score: 0

      CSS? But Taco's copy of "Teach Yourself HTML in 24 Hours" by Sam's puiblishing doesn't go into CSS.

    19. Re:Easy work-around for now by Blkdeath · · Score: 1
      The space-adding hack breaks code,
      What sort of code does it break, exactly?
      breaks plain-text urls (exacerbated by the "Slashdot doesn't automatically turn URLs into links" bug)

      IMHO, I'd prefer that plin-text not be HTML-ized. Those sorts of features are the ones that tend to lead to strange scripting vulnerabilities being executed on hapless viewers.

      If Slashdot used a simple layout or a CSS layout, a single wide post would not cause other posts to wrap off of the screen.
      What kind of layout would you prefer, based on the varying nature of /.'s content delivery?
      Slashdot's use of tables also makes IE users wait for the entire page to load before they can read the first comment,
      If I'm not mistaken, that rendering issue dissapeared in IE 5 (or was it 5.5?). It was Netscape Communicator that had issues with tables (ie; pages with table layouts that were missing a single </TABLE> directive would show as blank, waiting for the entire page to download (including all images if HEIGHT and WIDTH weren't used), etc.)

      I've used IE on dialup to visit large(r) pages using table layouts, and haven't noticed a problem. If it does still exist, however, isn't that more of a browser deficiency than a website problem?

      See also: More reasons to avoid using tables for layout [webmasterworld.com] rather than only using tables for tabular data.
      Most of the reasons given lend to poor website design, not the use of tables. I've always opposed static pixel width/height designes in almost all circumstances, regardless of the use of tables. All sites I design use percentages, or wildcards (SIZE="120,*") if, for example, I have 120px navigation buttons.

      If you design a website properly, it'll look good at 640x480 through to 1600x1200 (with the only problem at the higher resolutions being lack of content making paragraphs/sections look really thin, IME), regardless of window size, browser accessories, colour depth, etc..

      It just goes to prove the old addage; it's easier to do it right the first time, etc..

      --
      BD Phone Home!

      Shameless plug. Like you weren't expecting it.

    20. Re:Easy work-around for now by Anonymous Coward · · Score: 0

      If Slashdot used a simple layout or a CSS layout, a single wide post would not cause other posts to wrap off of the screen.

      Yeah, but then Slashdot wouldn't be readable to people who use bog-standard, half-assed browsers on third-rate operating systems installed in their copious free time on computers built in their parent's garage by shoplifting parts from CompUSA. In other words, about half of all Slashdot readers.

    21. Re:Easy work-around for now by Anonymous Coward · · Score: 0

      I can see why this was modded down, but actually, posting this solution here might be useful, especially if the ORIGINAL page has been slashdotted.

      On the other hand I think all three solutions should be posted at the same time, to preserve the gist of the article.

    22. Re:Easy work-around for now by Anonymous Coward · · Score: 0

      If there's a better explanation of why Mozilla sucks donkey cock, I haven't heard it. Manually entering preference settings into cryptic configuration files that don't even exist by default. Get your heads into the 21st century, you fucking losers.

    23. Re:Easy work-around for now by Saxerman · · Score: 2
      Just because it's intentional, doesn't mean it's not a bug.

      Sure it does. If it's intentional we call it a 'feature' not a bug. Or, as we say in the shop, "The only difference between a feature and a bug is that a feature has documentation."

      --

      A steaming cup of soykaf would be real wiz right now.

    24. Re:Easy work-around for now by packeteer · · Score: 2

      oic now... thanks for the info. although i now think this is not a bug i still wish that slashdot didn't have to do that. and yes i have seen the page widening trolls usually linked to goatse.cx... not fun but there has to be another way...

      --
      unzip; strip; touch; finger; mount; fsck; more; yes; unmount; sleep
    25. Re:Easy work-around for now by Anonymous Coward · · Score: 0

      The point is that they're user prefs, you hapless twit. It's up to the user to have preferences. True, many hapless twits don't want to be able to configure their browser and plug security holes, but for the rest of us typing out a user.js is no big deal.

    26. Re:Easy work-around for now by DrSkwid · · Score: 1

      locate only indexes files readable by nobody

      --
      There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    27. Re:Easy work-around for now by trezor · · Score: 1

      So you don't know html, that's it? *grin*

      --
      Not Buzzword 2.0 compliant. Please speak english.
    28. Re:Easy work-around for now by trezor · · Score: 1

      And I don't know how to read, evidently :)

      --
      Not Buzzword 2.0 compliant. Please speak english.
  5. No Big Deal by md17 · · Score: 3, Interesting

    I very highly doubt that any site that I visit will be exploiting this bug. Who would waste the time to do this when only about 1% of their visitors will be susceptible to the user tracking. Yeah, I am concered about privacy, but is this really news? Thanks /. for keeping me informed.

    1. Re:No Big Deal by VoiceOfRaisin · · Score: 2, Informative

      youre right, its not news. it would only be news if it was in internet explorer, correct?

    2. Re:No Big Deal by ALoverOfPeace · · Score: 1

      Security through Obscurity?

      Isn't that the same concept everyone here bashes Microsoft for? Sure it's not exactly the same, but the only reason this bug isn't that big of a deal is because Mozilla is a rather obscure browser.

    3. Re:No Big Deal by Anonymous Coward · · Score: 0

      Eh.. no. Obscurity inferrs that it is something not widly used. People bash Microsoft for LACK of security, or failure to fix things. And before you say that this has been a problem for months (which it obviously has), look at the difference between this bug and IE problems. Most Mozilla bugs have to do with reading a profile, or something similar. MS bugs tend to have more to do with executing arbitrary code and such.

    4. Re:No Big Deal by Eloquence · · Score: 1
      You may not have noticed it, but sites differ in their target audience. I would very much doubt that only 1% of Slashdot's or K5's visitors use Mozilla, for example.

      So be careful the next time you visit that open source news site ..

    5. Re:No Big Deal by NineNine · · Score: 1

      inferrs that it is something not widly used.

      You're right. That's why he said that Mozilla is "obscure". It's not widely used.

      Did you forget to take your meds today?

  6. I'm not real upset by this. by Bryan+Bytehead · · Score: 2, Interesting

    I do everything in Mozilla in tabs. I open new sites in tabs, I'll even load other pages in tabs (middle click is your friend). As a result, they can't spy on me, because I don't go anywhere in that tab once I get there. If (and that might be a pretty big if) that is how you do your browsing, this bug isn't a big deal.

    --
    Bryan
    1. Re:I'm not real upset by this. by Lemmy+Caution · · Score: 1

      I only drive my car forward. I never use reverse. As a result, a defect which causes my car to explode only when it goes in reverse doesn't effect me. If you drive the way I do, that defect isn't a big deal.

    2. Re:I'm not real upset by this. by PimpNinjaWannaBee · · Score: 0

      The "bug" is there even if you open and go back in a different tab/window. Try it out and youll se.

  7. HTTP_REFERER by nick_davison · · Score: 5, Interesting
    The bug allows a web site to track where you're going when leaving the site whether you use a link, a bookmark or type a URL into the address field.

    It always bemuses me that people seem to think these things are new. Tracking exits is relatively simple and as for how people access your site, just check HTTP_REFERER. Typed URLs and bookmarks show no referer, links show you who sent them to your site. Granted, it's not 100% infalible, but it works on any browser. I'd rather trade 80% accuracy 100% of the time than 100% accuracy on 5-10% of hits.

    From time to time, it still amuses me to be watching the logs while I'm chatting to a visitor via Messenger and tell them what system they're running, what their screen res is, color depth, what enabled/disable features they have and the path they've taken through the site. If you're really that bothered, JavaScript even lets you track their mouse's movement around and how they scroll up/down the page and then play it back on your own PC, telling you things like how fast they read and what they paid attention to.

    1. Re:HTTP_REFERER by dbaron · · Score: 1

      This particular thing is new (to some extent, but see below) since it's tracking the reverse of what is tracked through the HTTP Referer header.

      However, it's also worth noting that some sites get this information already (especially when money is at stake) by making external links go through a local URL that redirects to the off-site URL.

    2. Re:HTTP_REFERER by harvardian · · Score: 2
      HTTP_REFERER tells you where you came FROM to get to the page in question (and only if the user clicked a link). The bug tells you where you're going TO.

      This is significantly more of an invasion of privacy than you make it out to be. If a website owner knows that I clicked a link on cnn.com to get to your page, that's no big deal. With this bug, however, a web page can track if I, out of my own whim, decide to go to porn.com after visiting your site. This is decidedly unexpected behavior, since if I'm entering in addresses into the goto bar myself, I don't expect anybody to be tracking my behavior.

    3. Re:HTTP_REFERER by singularity · · Score: 4, Informative

      As with a lot of browser-based things that show up on Slashdot, I feel the need to chime in with a different perspective, from a browser that does a lot of these things correctly.

      iCab, on the Mac, has a setting (and has had it almost since its very first versions) to only allow the Referrer: to be sent only when in the same domain (or even never sent). So Sony.com can trace how I look through their site, but cannot see that I came to Sony's site from a link on slashdot.org

      I could even set it to never send it, as well.

      --
      - (c) 2018 Hank Zimmerman
    4. Re:HTTP_REFERER by Kashif+Shaikh · · Score: 1

      If you're really that bothered, JavaScript even lets you track their mouse's movement around and how they scroll up/down the page and then play it back on your own PC, telling you things like how fast they read and what they paid attention to.

      Seems like Javascript was designed from ground up to be window-spamming and user tracking friendly....enter conspiracy theorists...

    5. Re:HTTP_REFERER by alanjstr · · Score: 2

      The problem with this bug is that they can tell where you're going next, regardless of whether you click a link, use a bookmark, or type the URL in yourself.

    6. Re:HTTP_REFERER by chris_mahan · · Score: 1

      Especially if a bunch of sites (scumbags) get together and automatch each other's referer and onunload logs. Then they can actually track users across domains.

      --

      "Piter, too, is dead."

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

      Youd be surprised how many pr0n sites that setting breaks. :(

    8. Re:HTTP_REFERER by olethrosdc · · Score: 1

      Hm, so if you do something like:

      ftp://blah:pass@site.com

      they can capture it? (?.. - ) Cool, I love internet protocol integration under a single application!

      --

      I miss my rubber keyboard.(Homepage)

  8. more news by Anonymous Coward · · Score: 0

    apparently this bug has been exploited by doubleclick, who provides the ad services on slashdot.

  9. Open source security by Anonymous Coward · · Score: 0
    I thought open source software was supposed to be secure because of the massive "peer review" concept.

    Unforunately, it turns out its just less secure, because hackers and script kiddies can look right there at the source code and figure out how to break into the system.

    1. Re:Open source security by victorvodka · · Score: 1

      Conversely, when we use Microsoft products, only the imminently trustworthy folks at Microsoft know what exploits they can use against us.

      --

      The flag just makes more sense than the constitution. - Judas Gutenberg

    2. Re:Open source security by Anonymous Coward · · Score: 0

      Patient victorvodka suffres from paranoid delusions; treat with 5 mg of Haldol along with 2 mg of Ativan p.o. q 30 minutes prn. If patient still hears voices after 30 minutes, repeat treatment. If symptoms still persist, we're going to have to pull out the Thorazine: 50 mg intramuscular injection every six hours until patient shuts the holy fuck up.

  10. Time for conspiracy theory... by wray · · Score: 0, Offtopic

    Is is possible that Microsoft is funding the project to under open source? Is it possible that the only reason the Mozilla project got done so fast is that it had Microsoft money backing it? Hmmmm... something to think about

    --
    Guess what? I got a fever! And the only prescription.. is more cowbell!
    1. Re:Time for conspiracy theory... by Anonymous Coward · · Score: 0

      I was beginning to wonder when the lawsuit is coming for Microsofts apparent monoploy of the deployment of bugs. They just seem to have the entire market wrapped up, and now their funding other projects just so they don't have a perceived monopoly? That is some dark shit. They be some clever, clever suits.

    2. Re:Time for conspiracy theory... by Anonymous Coward · · Score: 0

      And Buzz Aldrin punched this guy in the nose for saying "He didn't go to the moon". I suppose Bill Gates will wind up on day punching some guy in the nose for "NOTsetting up Mozilla for a fall"

    3. Re:Time for conspiracy theory... by wray · · Score: 1

      Good grief moderators --- too late now, but this was meant to be FUNNY --- I guess I have to make this more obvious because everybody wants to see TROLL.

      Give me some love. :-)

      --
      Guess what? I got a fever! And the only prescription.. is more cowbell!
  11. I care much more that enigmail doesn't work by drinkypoo · · Score: 2

    At least for me. I tried the windows enigmail on 1.0a, 1.1a, and now 1.2a, and none of them work. GnuPG is installed in c:/gnupg where it belongs... I thought this shit was supposed to be seamless.

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    1. Re:I care much more that enigmail doesn't work by archen · · Score: 1

      Heh, that's what I was thinking. Too bad they couldn't throw some of us a bone and at least just give us a crap NSIS install. Course many open source projects tend to be exactly the same way, so I suppose it shouldn't be too surprising.

    2. Re:I care much more that enigmail doesn't work by Wonko42 · · Score: 2

      Funny, it worked just fine for me on the latest nightly build on Windows.

    3. Re:I care much more that enigmail doesn't work by Wonko42 · · Score: 2

      Ahem. Why don't you just click on the "Install" button for the appropriate Enigmail version on their website? That's it. Voila. Enigmail is being installed. Who needs a seperate installer? The functionality is built into Mozilla.

    4. Re:I care much more that enigmail doesn't work by drinkypoo · · Score: 2
      Uh, BZZT. As I said above I ran the install on three different versions of mozilla and none worked. It's nice that it works for some people, but it definitely isn't working for everyone.

      My problem isn't with XPI though, it's with enigmail itself. The install supposedly completed, it just doesn't work.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    5. Re:I care much more that enigmail doesn't work by Wonko42 · · Score: 2
      My point was that if the XPI won't install, then a Nullsoft installer certainly isn't going to do any good.

      You did remember to completely exit and then restart Mozilla, right? Sometimes it leaves a process hanging around for a while. Also, I seem to recall someplace on their website mentioning that some versions of Mozilla that were installed with the installer have problems.

    6. Re:I care much more that enigmail doesn't work by drinkypoo · · Score: 2

      Yeah, I restarted mozilla a few times, and did it on different versions. So far, color me unimpressed. Maybe I'm unimpressed with Mozilla, though, and not enigmail.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    7. Re:I care much more that enigmail doesn't work by Wonko42 · · Score: 2

      I guess it's a pity you can't get it working. I really like it so far.

    8. Re:I care much more that enigmail doesn't work by archen · · Score: 1

      Actually I was referring to gpg not Enigmail. While the enigmail installer works fine for me, installing gpg didn't go so smoothly. As someone who doesn't like everything stuffed on the root directory of their C drive, I found that gpg basically just did whatever it wanted to. And to CHANGE the options you have to manually enter keys into the registry. As much as I like manually dumping crap into the registry, I'd rather that they gave me an installer to do that much.

  12. I'm surprised.. by Frank+of+Earth · · Score: 2, Insightful

    .. how many people are saying "no big deal". If the article stated:

    "The bug in Internet Explorerallows a web site to track where you're going when leaving the site whether you use a link, a bookmark or type a URL into the address field"

    you would hear a dplethora of privacy zealots bitching and moaning how this is typical M$ practice and blah blah fucking blah.

    Because of a /. article and because I'm OS/Software egnostic, I tried Mozilla 1.0 which was a horrible product. I could repeatedly lock up the browser simply by going into the preferences. Maybe it's been fixed 1.0.1, but I'm not willing to waste my time, especially since IE runs just fine.

    I have excellent Karma, so if you can't handle the truth, mod me down, I don't give a shit, I'm just sick of the "hippicratical oath" /. editors have taken.

    1. Re:I'm surprised.. by quinto2000 · · Score: 2
      It is actually kind of a big deal, but I'm not even going to bother patching it. I actually find OnUnload events to be handy as long as "open unrequested windows" is disabled.

      So: people on Slashdot like Mozilla. This bug isn't a big enough deal to really affect anyone, so they don't complain.People on Slashdot hate Microsoft. The bug still isn't a big enough deal to do something about if you're affected, but you can point and laugh at Microsoft about it nonetheless.

      --
      Ceci n'est pas un post
    2. Re:I'm surprised.. by superpeach · · Score: 1

      Well, on Slashdot this week the theme is news for other nerds, stuff that doesnt matter as much. The week started off with the OpenSSL bug, followed closely by the mozilla bug. Anyway, its ok for open source software to have bugs - because everyone checks the code line by line before they use it ;). Actually, I guess that is an ok kind of excuse, i'm sure some people who are really worried about privacy issues and stuff would check at least some of the code (by 'some people' I dont mean the people who whine about it when it shows up on slashdot, I mean the ones who know what they are talking about, and probably have something big to hide). And no, this doesn't mean microsoft is bad for not releasing all their source :) people who are concerned should just not use IE.

    3. Re:I'm surprised.. by Anonymous Coward · · Score: 0

      > how many people are saying "no big deal". If the article stated:...

      Heck, it probably wouldn't have been posted. You know, finding privacy busters in IE just isn't news anymore. It is an EULA required feature.

    4. Re:I'm surprised.. by Anonymous Coward · · Score: 0

      Hey, here's a great idea! If you don't like the way slashdot operates, how about you leave instead of bothering us with your whining?

    5. Re:I'm surprised.. by denny_d · · Score: 1

      yeh, people on slashdot like mozilla...hell, it's where I found out about the 'bug', cked the mozilla site but not a ripple over there yet... slashdot beats the press...again

    6. Re:I'm surprised.. by Joe+Tie. · · Score: 1

      Because of a /. article and because I'm OS/Software egnostic, I tried Mozilla 1.0 which was a horrible product.

      With an attitude like that, you most certainly are not "OS/Software agnostic". What you are is no different than people who give a broad statement that windows is a horrible product because their non updated, mismanaged, windows95 using computers crashed.

      I'm just sick of the "hippicratical oath" /. editors have taken.

      And what would you rather have had happen? Wouldn't you have been "bitching and moaning" about the slashdot bias if this article hadn't been posted? Do you honestly think these "Oh, I use windows and no one here understands me!" posts which pop up every time a problem with an open source project occurs are any less annoying than the knee jerk anti microsoft postings? Take a look in the mirror, your post is the exact other side of the coin to the ones you're complaining about.

      --
      Everything will be taken away from you.
    7. Re:I'm surprised.. by Osty · · Score: 1

      And what would you rather have had happen? Wouldn't you have been "bitching and moaning" about the slashdot bias if this article hadn't been posted?

      I think what he's getting at is that the editors need to be consistent. Either no unwarranted bitching about Microsoft in the article (screw the comments, there's nothing anyone can do about those), or bitch equally about other topics. For instance, if this were an IE problem, the Slashdot article would've mentioned that the problem has been known for months and nothing's been done about it yet, but since this is about Mozilla, and Slashdot likes Mozilla, there's no mention at all about this.


      Bitch or don't bitch, but do it equally. Since this site is read by quite a few people, and many use it as a major source of news, the best thing would be to present a professional front and don't bitch at all (save it for the comments). <rant>Editors, like it or not, your little site isn't so little anymore. You can't have your cake and eat it too. Either you're a respectable, legitimate news clearinghouse (whether that's what you want or not), or you're not. If you are, let's see less bias, better spell checking, no duplicated stories (except in Slashback), fact-checked articles, due diligence about small sites with respect to the Slashdot effect, and so on. If you're not, fine. But don't represent yourself as if you are.</rant>


      And just to head off the trolls -- Yes, I know I can simply not read Slashdot. That's a valid solution, but I doubt you'd really like what the site becomes if everyone who has a grievance with the management just up and left.

    8. Re:I'm surprised.. by foobar104 · · Score: 2

      With an attitude like that, you most certainly are not "OS/Software agnostic".

      His comment sounded pretty objective to me. Have you ever used Mozilla? Assuming the answer is yes, have you ever used a state-of-the-art browser like IE 5 or 6 or OmniWeb 4.1? Mozilla would have been great if it had been called Netscape 5.0 and released in early 1998. Since this is 2002 and the world has moved on, Mozilla sucks pretty hard.

    9. Re:I'm surprised.. by Anonymous Coward · · Score: 0

      It's 'hypocritical', and the Mozilla bug doesn't approach the severity of those suffered by IE. And I haven't had a Mozilla lockup since around .6 . Blah fucking blah indeed.

    10. Re:I'm surprised.. by robson · · Score: 3, Insightful

      Mozilla would have been great if it had been called Netscape 5.0 and released in early 1998. Since this is 2002 and the world has moved on, Mozilla sucks pretty hard.

      Since you sound like an otherwise reasonable person, I can't help but think that you simply haven't given Mozilla a chance. Having used all of the major browsers available, I prefer Mozilla. Not because it's open-source, not because it's an underdog, but because I like it. If you'd said, "Mozilla doesn't offer enough for me to switch," that would've made sense; however, I can't see how anyone who'd used Mozilla (1.0+) could think it "sucks pretty hard."

    11. Re:I'm surprised.. by foobar104 · · Score: 2

      Thanks for the benefit of the doubt. Sometimes I'm reasonable, sometimes less so. Only time will tell if I'm being reasonable right now, or if I'm in my "Zippy the Pinhead" mode.

      She DID it with TWO STACKS of old PHONE BOOKS and a COPY of the MOZILLA source code in BINARY!

      (Oops. Sorry.)

      Why Mozilla Sucks Hard
      An Essay by Foobar104.


      (Okay, not so much an essay as just a list, in no particular order. Also, I make no guarantee that this is my complete list of gripes. If you refute all of these, I will either just ignore you and pretend I never came back to this thread, or I'll respond with, "Yeah, but what about x and y? Bet you think Mozilla sucks now, don't you!?")

      1. On both platforms I've tried-- Windows 2000 and Mac OS X-- Mozilla is significantly slower than the browser of choice on that platform. Browsers of choice being IE and OmniWeb, of course. Does it render pages faster? Who the hell cares? How fast it renders pages has no affect on me at all if I refuse to wait the eight to twelve seconds it takes to launch the application or the five seconds it takes to open a new window.

      2. Mozilla's user interface does not follow the HCI standards of any known platform. It's equally quirky and wrong on Windows, Mac OS 9, or Mac OS X.

      3. The Mozilla preferences dialog is completely screwed. There are dozens-- maybe as many as a hundred-- preferences listed in that dialog, grouped in categories that make little sense if any. And, on that subject, don't anybody ever say the words "edit your user.js file" to me again, okay? If I wanted to fart around with config files, I'd just write my own browser. This is my home machine, and I expect to be able to use it without firing up a text editor.

      4. The Mozilla toolbar is broken and can't be fixed by mere mortals. By which I mean this: I want a home button on my toolbar, but Mozilla doesn't let me put one there. I want to show only icons in the menu bar, but Mozilla won't let me do that, either.

      5. Text fields-- both plain text fields and textarea fields-- are broken. What do I mean by "broken?" I mean that these things do not work correctly. What am I, Bugzilla?

      6. The sidebar "feature," which no right-minded person would ever find useful, is so bloated and overbuilt that it must take up a significant fraction of the total size of the application, both in terms of megabytes on disk and megabytes of RAM when running.

      7. Speaking of megabytes, who told the Mozilla "team"-- and I use the word loosely-- that they could ship a 35 MB web browser that eats up as much RAM as Microsoft Word and Microsoft Excel combined? OmniWeb is 8 MB, and that's for the version with i18n.

      8. "New Window" is on a fucking submenu. That's absurd. Have those guy really never read the Apple Human Interface Guidelines? No matter what OS you write software for, that book is the bible, man.

      That's it. I'm done now. Mostly because I'm just bored.

    12. Re:I'm surprised.. by recursiv · · Score: 2

      bravo!
      The last time I used mozilla was admittedly a long time ago, but it was slower than a donkey's ass on christmas, and I haven't had any reason to go back and look at it again, because IE seems to be getting better and better.

      --
      I used to bulls-eye womp-rats in my pants
    13. Re:I'm surprised.. by Cl1mh4224rd · · Score: 1

      Slashdot "beat the press" because, well... No one really feels this is an issue to create a media orgy over.

      Unless Slashdot is the only news site you read, you know that much of the news they post is, on average, two days old.

      That being said, Slashdot [b]isn't[/b] a news site. It's more like portal. How many stories here are Slashdot originals?

      --
      People will pass up steak once a week, for crap every day.
    14. Re:I'm surprised.. by Anonymous Coward · · Score: 1, Interesting

      Well, for your UI issues you might have tried Chimera on your Mac. Galeon on a Linux box is slick and without a doubt the best browser I have ever used.

      I have not found OmniWeb to be faster than Mozilla on the ibook, but it sounds like you have an issue with RAM and that is not really an issue in our house.

      Okay, I am not a great fan of the Mozilla Navigator's prefs menu, but once you learn it and set your prefs you can mostly forget about it. And about creating a user.js file, it's not that difficult, and once you do it you'll have a better browsing experience with little hassle. I love having a config file that I can just backup and drop in a new installation. What's so upsetting about a config file? With a sane file manager and a text editor it's trivial.

      What about the positives of Mozilla? Tabbed browsing? No pop-ups? Pipelining? Are you saying nothing about Mozilla interested you?

    15. Re:I'm surprised.. by Anonymous Coward · · Score: 0

      Ah, but there is an important point you're missing when you say that people would complain more if it was IE that had the bug:

      Before IE became dominant, there wasn't one browser that was almost universally used, (no, not even Netscape - it was the most popular, but had nowhere near the 95% or so usage that IE does). Most people strongly believe that Microsoft deliberately tried to force IE on to people, so that they could profit from it. Personally, I think that that practice is a bit unethical, but if they are going to try to force IE on to the marketplace, they most certainly SHOULD make it a decent browser.

      Mozilla, Netscape, and just about every other browser is there as an option - it's not being forced on you, and infact you're not even really being encouraged to use it. If AOL, for example, is going to bundle Mozilla with their service, I would expect them to work hard at alerting people to security vulnerabilities that are found in Mozilla, but the Mozilla team do what they do free of charge.

      The bottom line is that if you own a licensed copy of IE, you PAID for it somehow, even if that was within the cost of your machine. If you own a copy of Mozilla, or practically any other browser, you might have paid for the CD, but you certainly did not pay for it in the same sense that you paid for IE.

      If you're going to become an illegal monopoly, then you should at least be a responsible illegal monopoly. A care-free illegal monopoly deserves all the criticism it gets.

      If you're a charitable organisation, then people have got a lot less reason to complain.

      If you're just a for-profit company, (analogy with Opera), then you have a moral, if not legal, duty to provide a reasonable service.

    16. Re:I'm surprised.. by Malcolm+Scott · · Score: 1
      I tried Mozilla 1.0 which was a horrible product. I could repeatedly lock up the browser simply by going into the preferences.

      In which case, find a way to reproduce the bug, go to Bugzilla, and file it. Most likely it's an issue with your configuration though.
      IE runs just fine.

      And has many, many more security flaws than Mozilla. There isn't a major news event every time Microsoft releases a minor security update on Windows Update. True, Mozilla isn't flawless. But it's way better than IE.
    17. Re:I'm surprised.. by oojah · · Score: 1

      4. The Mozilla toolbar is broken and can't be fixed by mere mortals. By which I mean this: I want a home button on my toolbar, but Mozilla doesn't let me put one there.

      Have you tried Navigator preferences "Select the buttons you want to see in the toolbar"?

      Roger

      --
      Do you have any better hostages?
    18. Re:I'm surprised.. by Frank+of+Earth · · Score: 2

      With an attitude like that, you most certainly are not "OS/Software agnostic". What you are is no different than people who give a broad statement that windows is a horrible product because their non updated, mismanaged, windows95 using computers crashed.

      No, I didn't say Linux was a horrible product. In face, I love Linux and install Cygwin tools on my windows pc just so I can use similar tools.

      What I did say is that /. promoted Mozilla like it was the next IE killer, so I installed it and it consistently crashed on my system. Based upon the other posts, there was quite a few common problems.

      I can give 2 sh*ts who makes the software, just as long as it performs well and is relatively cheap to own [free is the best obviously]

    19. Re:I'm surprised.. by Frank+of+Earth · · Score: 2

      NO, it's hippocratical oath. Sort of a play on words of the Doctor's oath.

    20. Re:I'm surprised.. by orkysoft · · Score: 1

      The Home buttons gets placed in the small toolbar, while the other buttons get placed in the big one with the location and the Back/Forward/Reload/Stop buttons.

      --

      I suffer from attention surplus disorder.
    21. Re:I'm surprised.. by trezor · · Score: 1

      When it comes to performance, IE is admittable good. Quick to use, quick to start. But what would you expect when it is buildt into the kernel?!?

      When it comes to security, there probably isn't a browser on earth that is near. In the means of known, unfixed security-issues.

      When it comes to standards, it pollutes the net, by introducing non-standard html, which makes the standard-abiding browsers look buggy.

      When it comes to standards, if IE was the only browser to be used, eventually, due to everyone's eventual adaption to the M$-HTML, where would the internet and www's-platform independency be?

      When it comes to moral, it is bad for your karma

      Now you choose.

      --
      Not Buzzword 2.0 compliant. Please speak english.
    22. Re:I'm surprised.. by oojah · · Score: 1

      Yeah, fair point.

      --
      Do you have any better hostages?
    23. Re:I'm surprised.. by orkysoft · · Score: 1

      FYI, I've been using Mozilla since version 0.6, and am fairly happy about it. I don't use most of those optional buttons anyway.

      --

      I suffer from attention surplus disorder.
    24. Re:I'm surprised.. by foobar104 · · Score: 2

      What about the positives of Mozilla? Tabbed browsing? No pop-ups? Pipelining? Are you saying nothing about Mozilla interested you?

      (Replying to an AC? Bad habit...)

      Tabbed browsing does absolutely nothing for me. I guess I have different habits than the tabbed browsing fans.

      Pop-ups? Haven't seen one since I turned on OmniWeb's "Scripts are allowed to open new windows only in response to being clicked" feature.

      So yeah, basically I'm saying that nothing about Mozilla interests me. If it disappeared tomorrow, I don't think the world would miss it. No disrespect intended to the people who've worked hard on it, but guys: you've wasted your time and effort. Sorry.

    25. Re:I'm surprised.. by foobar104 · · Score: 2

      First, that only allows you to turn the mandated buttons off, not add ones that aren't presently allowed. And, as somebody else pointed out, there is no home button on the toolbar under any circumstances. There's a link on that oh-so-unnecessary "favorites bar" or whatever they call it.

    26. Re:I'm surprised.. by SiChemist · · Score: 1

      I am a recent Mozilla convert. I changed over from Internet Explorer one day after a malicious web site hijacked my browser and reset my home page and default search engine. All because I mistyped a URL in the address bar and got a disreputable site. At the beginning of your post you say:

      If you refute all of these, I will either just ignore you and pretend I never came back to this thread, or I'll respond with, "Yeah, but what about x and y? Bet you think Mozilla sucks now, don't you!?"

      So my comments are more for people who read your post and wonder if you have reasoned criticisms (I think mostly not) or if you are just blowing hot air.

      1. On both platforms I've tried-- Windows 2000 and Mac OS X-- Mozilla is significantly slower than the browser of choice on that platform. Browsers of choice being IE and OmniWeb, of course. Does it render pages faster? Who the hell cares? How fast it renders pages has no affect on me at all if I refuse to wait the eight to twelve seconds it takes to launch the application or the five seconds it takes to open a new window.

      I've only used Mozilla on Windows 2000, so I can't comment on the Mac version. My question on this topic is "Did you enable quicklaunch?" The reason that IE starts so fast on the Windows platform is that a large portion of it is loaded into memory on bootup! Mozilla has an option to load portions of itself into memory on boot to make it start faster. I don't use it myself, but it's there if you want. As for the "new window" complaint, I'll address that in my last comment.

      2. Mozilla's user interface does not follow the HCI standards of any known platform. It's equally quirky and wrong on Windows, Mac OS 9, or Mac OS X.

      Since you make no specific legitimate complaint here ("quirky and wrong" doesn't count), I can't address this point. I can point out people who like Mozilla's interface for each person who doesn't like it. I would hazard a guess that you prefer the interface that you are used to, and don't like it when an application doesn't clone it.

      3. The Mozilla preferences dialog is completely screwed. There are dozens-- maybe as many as a hundred-- preferences listed in that dialog, grouped in categories that make little sense if any. And, on that subject, don't anybody ever say the words "edit your user.js file" to me again, okay? If I wanted to fart around with config files, I'd just write my own browser. This is my home machine, and I expect to be able to use it without firing up a text editor.

      Again, you make a blanket statement without mentioning any specific gripes. I will say that most people that I know LIKE having many choices. I don't know why you throw in the "edit the user.js file" red herring, but I will say that it's nice to be able to take even finer control of your browser if you are willing to delve into the config files.

      4. The Mozilla toolbar is broken and can't be fixed by mere mortals. By which I mean this: I want a home button on my toolbar, but Mozilla doesn't let me put one there. I want to show only icons in the menu bar, but Mozilla won't let me do that, either.

      You're complaining that you can't make it look EXACTLY like Internet Explorer? There's a "home" button on the Personal Toolbar! Mozilla has a "skinnable" interface, so it is possible to customize it a great deal more than your current browser.

      5. Text fields-- both plain text fields and textarea fields-- are broken. What do I mean by "broken?" I mean that these things do not work correctly. What am I, Bugzilla?

      Another vague criticism. At least here you admit your inability to articulate exactly what is wrong. "They don't work." is just bitching, it isn't a reasoned comment.

      6. The sidebar "feature," which no right-minded person would ever find useful, is so bloated and overbuilt that it must take up a significant fraction of the total size of the application, both in terms of megabytes on disk and megabytes of RAM when running.

      Is this just a wild-assed guess? "Bloated and overbuilt?" I guess you've looked through the source code to make this determination?

      7. Speaking of megabytes, who told the Mozilla "team"-- and I use the word loosely-- that they could ship a 35 MB web browser that eats up as much RAM as Microsoft Word and Microsoft Excel combined? OmniWeb is 8 MB, and that's for the version with i18n.

      I'm not sure that I understand why you make this criticism. Why compare the footprint of Mozilla to MS Word and Excel? Since I don't have either of these applications on my home machine, I can't verify your figures. I've never used OmniWeb, and so I have no comment on it.

      8. "New Window" is on a fucking submenu. That's absurd. Have those guy really never read the Apple Human Interface Guidelines? No matter what OS you write software for, that book is the bible, man.

      Browsing in separate windows in Mozilla is ignoring one of its best features: "tabbed browsing." I used to use IE in multiple windows too, but tabbed browsing kicks the holy hell out of the old method. (I expect the next version of IE will have it.) There is no way that I can describe how much simpler and faster it is, those of you who haven't tried it and still have an open mind should just try it for yourself.

      I want to just quickly mention a few of the real innovations that Mozilla supports: Pop-up blocking, mouse gestures, (overall)better security and extensibility that means there are continually new features as add-ons. Take it from a former diehard IE user: If you haven't tried Mozilla, you don't know what you're missing!

    27. Re:I'm surprised.. by foobar104 · · Score: 2

      I've only used Mozilla on Windows 2000, so I can't comment on the Mac version. My question on this topic is "Did you enable quicklaunch?"

      I guess you're not getting my point. I don't care why Mozilla is slow. The mere fact that it's slow is enough to get me to remove it from my system. To think that there's a "make run faster" preference somewhere... that's just nuts. If you can make it go faster, you should. It shouldn't be an option, especially one that isn't on by default.

      This, more than anything, is evidence that the Mozilla team isn't really interested in building a browser that people will actually want to use. They're just building a browser for themselves.

      I would hazard a guess that you prefer the interface that you are used to, and don't like it when an application doesn't clone it.

      No, no, no. Both Mac OS X and Windows have user interface guidelines. Applications that don't follow them are quirky and wrong. In their mad rush to create a browser than runs on lots of platforms, they decided to ignore platform-specific user interface guidelines. If I'm using Windows, I want to use programs that work the way Windows programs should. If I'm using a Mac, I want to use programs that work the way Mac programs should. I don't want to use a program that looks and feels like a half-assed port.

      I will say that most people that I know LIKE having many choices.

      Then I would say that most of the people you know are atypical. The first thing I want to do every time I fire up a new build of Mozilla-- which has been more times than I care to admit-- is turn off that damned home page. In order to do so, I have to navigate through a baffling list of checkboxes and radio buttons. That's broken and wrong.

      There's a "home" button on the Personal Toolbar!

      So you're saying the only way I can get a home button on the toolbar (or, rather, a toolbar) is to have a second toolbar open all the time? If any reasonable person stopped for just a minute to think about that, they'd realize how absurd it sounds.

      Mozilla has a "skinnable" interface, so it is possible to customize it a great deal more than your current browser.

      Skins schmins. I've already complained about how Mozilla doesn't look and feel like a native application. What makes you think I'd want to throw a "skin" on it that makes it look even less like a native application? Besides, find me a skin that puts a home button on the toolbar and I'll shut up.

      Another vague criticism. At least here you admit your inability to articulate exactly what is wrong. "They don't work." is just bitching, it isn't a reasoned comment.

      Try 'em. Use 'em. If you decide that they're not broken, good for you. I've decided that they're broken. I'm sure lots of other people share that opinion. If you want to ignore it, be my guest.

      I guess you've looked through the source code to make this determination?

      Yup.

      Why compare the footprint of Mozilla to MS Word and Excel?

      Because Word and Excel are big programs that each do a hell of a lot more than Mozilla ever could. The fact that Mozilla eats more RAM than either of them should be an embarrassment.

      Hell, most of that RAM probably goes to chrome, anyway.

      Browsing in separate windows in Mozilla is ignoring one of its best features: "tabbed browsing."

      Advocating tabbed browsing is ignoring one of my best features: I don't like it.

      There is no way that I can describe how much simpler and faster it is

      It's simpler and faster because Mozilla is such a pig at opening new windows, right?

      Pop-up blocking, mouse gestures, (overall)better security and extensibility that means there are continually new features as add-ons

      (1) I haven't seen pop-ups since I installed OmniWeb, which disables them all by itself.

      (2) Mouse gestures? You're kidding, right? You think that's usable? That's a gimmick for people who are impressed by gimmicks. It's right up there with speech and handwriting recognition: useless 99% of the time.

      (3) "Better security and extensibility" is an ironic comment considering we're writing this in context of an article about a security bug. Sounds like Mozilla is calling IE black here. And extensibility? Who the fuck cares about extensibility in a web browser? The browser should be small in size, lightweight in RAM, reliable, and fast. All four of those were sacrificed in building Mozilla.

      The Mozilla project is a failure. It has failed to produce a usable web browser, even after all these years.

    28. Re:I'm surprised.. by SiChemist · · Score: 1

      Hmmmmm. I guess we have to agree to disagree :p

    29. Re:I'm surprised.. by Anonymous Coward · · Score: 0

      If you can make it go faster, you should. It shouldn't be an option, especially one that isn't on by default.

      Does this mean you have a computer with 4Gb of memory and every application you have installed open and ready to run? After all, you can make it faster that way, so why not do it?

      The fact that making Mozilla faster by automatically loading parts of it at startup means that you loose some memory in the process seems to be lost of you.

    30. Re:I'm surprised.. by robson · · Score: 2

      (Okay, not so much an essay as just a list, in no particular order. Also, I make no guarantee that this is my complete list of gripes. If you refute all of these, I will either just ignore you and pretend I never came back to this thread, or I'll respond with, "Yeah, but what about x and y? Bet you think Mozilla sucks now, don't you!?")

      Well... I was going to refute each of your points, but I don't suppose that would be very constructive use of my time ;)

    31. Re:I'm surprised.. by Anonymous Coward · · Score: 0

      More likely you just can't, you bloody poof.

    32. Re:I'm surprised.. by Shrique · · Score: 1

      Well it sounds like your one of those 1/10th of 1% of the people that this wasn't designed for. Go use your damn IE and have a blast. I personally like the way Mozilla works and have never had a complaint.

      Oh and I don't like to have to install another app just to make sure the browser I'm using isn't spying on me. It's an extra bit of thing that he developers should have thought through from the getgo and added that in. Blah blah blah MS sucks.

    33. Re:I'm surprised.. by surfimp · · Score: 1
      First off, I like that you're taking to time to point out what you dislike about Mozilla, rather than simply claiming "It sucks!" That's reasonable and meritworthy, considering the "social milieu" that is /.

      I guess you're not getting my point. I don't care why Mozilla is slow. The mere fact that it's slow is enough to get me to remove it from my system. To think that there's a "make run faster" preference somewhere... that's just nuts. If you can make it go faster, you should. It shouldn't be an option, especially one that isn't on by default.

      Under Windows, a portion of IE (Windows Explorer) is kept loaded at all times so that the web browser can "magically" launch, nearly instantaneously. However, this means that when you're not using IE to browse the web, you're still losing some memory to it's background processes.

      As I understand it, the Mozilla development team felt that users should have a choice as to whether or not they wanted a portion of Mozilla running in the background at all times. For me, a person who uses Mozilla exclusively (because I like it, not because "it isn't IE"), they provided (for Windows, at least) the Quick-Launch feature (Edit > Preferences > Advanced > Enable Quick Launch).

      This, more than anything, is evidence that the Mozilla team isn't really interested in building a browser that people will actually want to use. They're just building a browser for themselves.

      You're absolutely correct. From the Mozilla FAQ:

      1.1. For whom is Mozilla 1.0 intended?

      Mozilla 1.0 is a fully functional technology demo for those interested in seeing what can be done with Mozilla technology, and those who want to create Mozilla-based products and packages. The intended target audience is the development community.


      They really aren't trying to win a browser war with IE, but I'm sure they're pleased that they've gotten so much positive press lately, since the 1.0 release. But I think that statement pretty much explains why Mozilla looks & works the way it does, and why it's skinnable, and so forth: it's most definitely not intended as a general-consumption web browser, but rather a development platform for future applications. I'm just glad that I, as a certified member of the unwashed masses, get to use the browser! :)

      Advocating tabbed browsing is ignoring one of my best features: I don't like it....It's simpler and faster because Mozilla is such a pig at opening new windows, right?

      If you love opening new windows so much, and are complaining about having to go File > New > Navigator Window in Mozilla, then I suggest you learn a very simple hotkey: CTRL + N. All the new windows you could ever want. I'm sure you knew this already, and don't meant to insult your intelligence by suggesting it, but it is the "easy" solution to your problem, no matter which browser you use. (It works in IE too, and the key combo is printed right alongside the "New Navigator" window in the Mozilla submenu).

      (3) "Better security and extensibility" is an ironic comment considering we're writing this in context of an article about a security bug. Sounds like Mozilla is calling IE black here.

      Actually, the Mozilla development team doesn't seem to spend much time at all thinking about IE, at least as far as I can tell. And the security "hole" we're talking about here is really much, much less severe than many (most?) associated with IE; it's not going to let someone run malicious code. And you have to wonder how many sites would actually try to leverage this hole, and what possible use they'd get from any information gleaned from it...

      "Oh, going back to Slashdot, I see...well, no suprise there, considering you're a Mozilla user..."


      The Mozilla project is a failure. It has failed to produce a usable web browser, even after all these years.

      Oh, that's just silly. This entire post was read & replied to using Mozilla. I have the Mozilla FAQ open in one tab, the post of yours to which I'm replying in another, and this tab, in which I'm typing my reply. Clearly I'm getting some usability out of this browser.

      However, as mentioned before, the point of the Mozilla project is not to produce a web browser, despite your obvious misconception to the contrary. The point is clearly stated in their FAQ above. I think they're achieving their stated objectives admirably, and hence, the project is not a failure.

      But if you prefer SmartTags and truly serious security holes, I invite you to continue using IE. It's your choice, and no one (from Mozilla.org, at least) is holding a gun to your head ;)
    34. Re:I'm surprised.. by CoreWalker · · Score: 1

      You, my friend, sound like a troll of the most obnoxious kind; slightly intelligent. Why do I call you a troll? Because your arguments boil down to this:
      "I don't like the way they do things. Since I don't like the way they do things, most people (at least the ones who matter) don't like they way they do things. All of the people who like the way they do things are in the minority and therefore stupid and insignificant. The browser should only do the things that I think it should do, and it should do all of those things by default. Anyone who wants something different is an alien and shouldn't be allowed to use a browser anyway."
      Do you work in marketing? Maybe for a big record label?

    35. Re:I'm surprised.. by foobar104 · · Score: 2

      Well it sounds like your one of those 1/10th of 1% of the people that this wasn't designed for.

      Your biggest mistake here is saying that Mozilla was designed. It wasn't. It grew. And like all software that just grows, it ended up terrible.

    36. Re:I'm surprised.. by Anonymous Coward · · Score: 0

      Yeah, you sound seriously "egnostic".

      You should see a doctor about that...

  13. Re:make up your mind slashdot by Anonymous Coward · · Score: 0

    Don't you mean "Make up my mind slashdot!"

    (Duh. Cars are secure [locks built in] or insecure [can lock up on slippery roads and crash]... personally I use them, but I really wanna know... should I drive or not?)

  14. This is not the same as Referer tracking. by Chuck+Chunder · · Score: 2

    It's more or less the inverse, this bug enables the referer to know where they refered you to.
    Of course, if you really wanted to do that then in most cases you'd just set up a bounce script on your server, much like freshmeat does, so that it would work on anyone.

    --
    Boffoonery - downloadable Comedy Benefit for Bletchley Park
  15. The problem with this bug by Chuck+Chunder · · Score: 4, Insightful

    Is that as breeches go it is a fairly minor one with a trivial work around, yet it remained confidential in bugzilla.
    If it isn't a big enough security hole to warrant instant attention then it should not be hidden in bugzilla, so anyone can have a whack at fixing it.

    --
    Boffoonery - downloadable Comedy Benefit for Bletchley Park
    1. Re:The problem with this bug by Wumpus · · Score: 3, Interesting

      The workaround is to disable the onunload handler. This is the kind of workaround that breaks legitimate applications.

    2. Re:The problem with this bug by jesser · · Score: 4, Insightful

      If it isn't a big enough security hole to warrant instant attention then it should not be hidden in bugzilla, so anyone can have a whack at fixing it.

      The bug was public for two months before it was marked as security-sensitive. There isn't an army of coders who spend all of their time fixing known minor privacy bugs. The bug had the "privacy" keyword for almost two months before it was marked as security-sensitive, so it would not have been invisible to such an army.

      I'm not saying it was a good idea to make it security-sensitive after it was open for a while. It wasn't a good idea in this case, because someone who had seen the bug while it was public decided to make it public again. I'm just saying that leaving it open probably would not have led someone to fix it immediately.

      --
      The shareholder is always right.
    3. Re:The problem with this bug by Blkdeath · · Score: 1
      The workaround is to disable the onunload handler. This is the kind of workaround that breaks legitimate applications.
      Perhaps my lack of knowledge of JavaScript (I've never used it much beyond very simple applications; changing list boxes based on a selection, mouseovers, etc..), but what exactly constitutes a legitimate use of onUnLoad?

      I've always seen it used to provide more pop-ups (which, of course, I have disabled anyways) and do other nasties with cookies, re-directs, etc..

      --
      BD Phone Home!

      Shameless plug. Like you weren't expecting it.

    4. Re:The problem with this bug by foobar104 · · Score: 5, Interesting

      Perhaps my lack of knowledge of JavaScript, but what exactly constitutes a legitimate use of onUnLoad?

      I'll give you one example. My company sells software with web front-end interfaces. One of the techniques we use is implementing a close-to-log-out feature. In other words, when you close the main app window, a handler fires that closes all daughter windows of the main app window and ends the user's session. That depends on onunload().

      We also use onunload() to make sure the application doesn't get confused if a user closes a window on which the application depends. When the users closes a window-- an alert dialog, say-- the onunload() handler checks to make sure that everything is as it should be. If it isn't, an error condition is established. Without onunload(), our application would be much less reliable in those kinds of situations.

    5. Re:The problem with this bug by Blkdeath · · Score: 1
      I'll give you one example. My company sells software with web front-end interfaces.
      Ok, those are certainly good examples. Myself, I prefer to rely on the user closing their session(s) properly, and timeouts to close them if they don't, but I suppose that is a relatively valid application.

      I've still yet to learn about a valid WWW application of this handler, however. Of course, without it, the pr0n industry might be a bit worse off. ;)

      --
      BD Phone Home!

      Shameless plug. Like you weren't expecting it.

    6. Re:The problem with this bug by foobar104 · · Score: 4, Insightful

      Myself, I prefer to rely on the user closing their session(s) properly....

      I mean no offense, but that's a terrible idea. I say that only because we had a pretty serious debate-- okay, shouting match-- about this in a team meeting about a year ago. On the one hand, there were us-- the managers-- saying that the software had to be resilient in the face of inconsistent or wrong user input. On the other, we had the engineers who said things like, "Browsers just don't work that way," and "Of course it's going to break if you do something stupid," and "We have to rely on the user closing their session properly." The bottom line is this: users don't do what you tell them. If you tell them not to close the window, they'll close it anyway. Your app has to be able to deal with things like that, just as it has to deal with "no such file or directory" or "out of memory." Without onunload(), it'd be impossible to write a non-trivial, resilient web application.

      Okay, end of rant. ;-)

    7. Re:The problem with this bug by Blkdeath · · Score: 1
      The bottom line is this: users don't do what you tell them.
      LOL.. Don't I know it. :> That's where my timeouts come in. If users don't learn to close their session, they'll just have to re-enter their password (oh, and close all n subsidiary windows while they're at it..) to get back in.

      My (potential) problem with relying on onunload() to end a session is the instability of ${GUI_INTERFACE} causing a browser to go, quite frankly, tits up. If the browser goes without notice, it can't call the handler regardless, so the timeouts would be used regardless.

      I programmed for just long enough to learn about babysitting users. ;) One of the most important things I learned during my time was to never rely on;

      • The client
      • Anything client-side

      to handle anything, period. Centralize, and trust in the servers was always my mantra.

      To each his own, of course, and if you're not having problems with your method, all the power to you. Perhaps one day I'll find need of it myself, who knows. :)

      --
      BD Phone Home!

      Shameless plug. Like you weren't expecting it.

    8. Re:The problem with this bug by sheriff_p · · Score: 2

      Another good example is an HTML IRC client that a friend of mine wrote. It worked by having a frame that was always being written to (the main IRC window if you like), and an IRC process on the server. When you typed in what you wanted to say, the script would send your data to the running IRC process. To avoid zombie IRC processes, onUnload spawned a window (a popup too, at that) which closed the process down nicely.

      --
      Score:-1, Funny
    9. Re:The problem with this bug by psoriac · · Score: 1

      I'll second that, I developed a web interface used to configure my company's product that uses onunload in pretty much the exact same way.

      --
      I browse Slashdot at +3, Funny
    10. Re:The problem with this bug by Idaho · · Score: 4, Insightful

      The workaround is to disable the onunload handler. This is the kind of workaround that breaks legitimate applications.

      Are you going to tell me there actually are legitimate uses for unonload!?

      I use the internet since 1996 and have yet to come across the first site that uses this 'feature' *cough* in a usefull, non-irritating manner (i.e. something else then opening a bazillion new popups as soon as you close the previous one)

      I can not imagine why onunload exists in the first place - 2nd, I can not imagine why people would ever leave it on if they can turn it off.

      But maybe that's just because my imagination is so limited :)

      --
      Every expression is true, for a given value of 'true'
    11. Re:The problem with this bug by radish · · Score: 2


      In an application I am working on, we have a popup configuration system which allows you to decide what content you want on the main page, reorganise it, change layouts etc. Once you are done editing you can close the popup, an onUnload then fires to force the main window to refresh (so you get to see the new layout).

      --

      ---- Den ene knappen er powerknapp, den andre er Bender voice knapp "Bite My Shiny Metal Ass"

    12. Re:The problem with this bug by peterarm · · Score: 1

      But if they disable onunload, aren't you screwed then if you're relying on it working? Surely there must be a more robust way?

    13. Re:The problem with this bug by gosand · · Score: 2
      I mean no offense, but that's a terrible idea. I say that only because we had a pretty serious debate-- okay, shouting match-- about this in a team meeting about a year ago. On the one hand, there were us-- the managers-- saying that the software had to be resilient in the face of inconsistent or wrong user input. On the other, we had the engineers who said things like, "Browsers just don't work that way," and "Of course it's going to break if you do something stupid," and "We have to rely on the user closing their session properly."

      Will you be my manager?

      Honestly, I have never seen management side against engineering on issues like this. When it comes to issues like this, it always seems to be someone from QA (me) who has to propose these scenarios that "will never happen". Usually management just wants to get the thing out the door. Getting the customer not to do "something stupid" is a training or documentation issue.

      I do stupid things every day. That's my job.

      --

      My beliefs do not require that you agree with them.

    14. Re:The problem with this bug by foobar104 · · Score: 2

      But if they disable onunload, aren't you screwed then if you're relying on it working? Surely there must be a more robust way?

      If ours were an application designed for public use over the Internet, I'd say yes... and no. Yes, we'd be screwed if clients connected to the application using unsupported browsers with key features disabled. And no, there's no more robust way in that situation, other than just redesigning the whole app to remove the dependency on multiple windows, which our market research (yeah, you heard me) tells us is a big part of the application user experience.

      But the good news is that this app is not meant for public use, and we have a certain degree of control over the client environment. That is to say, we tell our customers that their client systems must be such-n-such. To the extent that it's possible, we prevent the customers from making honest mistakes by checking user agent headers and whatnot. If somebody wanted to deliberately conceal their browser type by modifying the user agent header, they could log in to the application and create an error condition by doing something that we assume they can't do. At which point they would have done nothing but succeeded in annoying us.

    15. Re:The problem with this bug by WWWWolf · · Score: 1
      One of the techniques we use is implementing a close-to-log-out feature.

      Never EVER depend on Javascript to implement security. =( The only thing that web stuff should use Javascript in security field is pre-submission verification of data.

      There are easier ways to implement the behavior you described - store session ID it in a cookie that expires when browser is closed, or pass session ID in the URL.

    16. Re:The problem with this bug by ichimunki · · Score: 1
      So the problem really is that Mozilla/NS/Galeon does not provide per site settings for JavaScript. Both IE and Konqueror have the ability to limit scripting based on URL or domain. And until Mozilla has the same feature built in there is no way to turn this on for a legitimate use such as the one you mention and turn it off elsewhere by default... which goes against the old security maxim of default deny for everything that is not explicitly allowed.

      At least Galeon, unlike Mozilla (at least the version of Mozilla I'm running) has a menu command to easily turn JS on and off, which is better than nothing.

      --
      I do not have a signature
    17. Re:The problem with this bug by foobar104 · · Score: 2

      Where did I talk about security? "Log out" in this context simply means closing all the windows associated with an application session at once. If the user has three windows open, closing any of them closes all of them. This isn't a security thing at all; it's a user interface feature that keeps the app from leaving orphaned windows open.

    18. Re:The problem with this bug by SA3Steve · · Score: 1

      There are definitely legitimate uses for this fuction. I have seen it used in some ASP apps for saving changes, notifiying the user if unsaved changes exist before they navigate away, etc...

      For every feature you find useless, there are most likely lots of users who actually do use it. There are plenty of features that I turn off on my machines only to find the person in the next office using all the time.

    19. Re:The problem with this bug by zurab · · Score: 2

      Without onunload(), it'd be impossible to write a non-trivial, resilient web application.

      What a load of crap! Nothing personal but I've been designing and developing web applications since Hector was a Pope (tribute to Chick) and this statement just doesn't sit well with me. Now, I don't know what your developers have been telling you on what is possible and what is not, but here is my reaction:

      First of all, you need to understand that the protocol over which most web applications operate, namely HTTP, was not specifically made for a mostly session-centric web applications. Hence, the web apps that need to track user sessions to accomplish their tasks need to implement their own session management, or use existing ones such as the implementation in ASP (from MS) or in PHP, or any other.

      Now, an implementation of a session management that is to operate over a non-session based protocol does present some issues. One of them being, the server, which assigns a unique session ID to clients and tracks the client sessions, has no way of knowing whether the client session is still "active" or not. This is usually resolved by either (a) having a logout link/button for a user to tell the server the session is over, or (b) a server-side session timer, i.e. if a client does not perform any action on the server for X period of time, the session is closed or deleted by the server, the impact being forcing the client to reestablish or create a new session. This system works fairly well for most web apps out there.

      The problem occurs in cases where session holds an expensive load (memory or processor time) for each session on the server and/or the sessions are licensed to you in a limited quantity by your proprietary software supplier. These sessions are so expensive on the server that users are often asked/required to logout when they are done with their tasks, mostly because it is extremely expensive to wait for the session to time out. Let me first tell you - this is a wrong way to implement a web application, the problem lies right there in the design. So, to hide this problem and make the web app with such design slightly less expensive to run, the requirements state that the "onunload" event be implemented to close the session on the server. But this is only a partial way of covering up the design problem at the root. In fact, users do a lot more than close the browser or go to some other site after they are done with their tasks with your web app. 1. They just leave the browser running; 2. they open a new window and browse somewhere else; 3. they minimize the window and play solitaire; 4. they lock the workstation and go to lunch; 5. browser or OS crashes, etc. These are the events that nobody can do anything about. Again, because (1) HTTP protocol is not session-centric, and (2) your web app design is flawed.

      So, back to your original statement: Yes, it is possible as well as customary to write a very complex web application without using the onunload event! Correct the root of the problem - create non-expensive sessions, store the data properly if you need to recreate sessions, set the reasonable timeout on sessions, and, do not limit your app functionality by purchasing or licensing a limited number of "sessions" (as that term is defined by your proprietary vendor) when possible.

    20. Re:The problem with this bug by Anonymous Coward · · Score: 0

      You wanna resiliant web application? And you use JavaScript?! So that your code breaks terribly and in subtle and confusing ways with every point release of every browser out there? Righto!

      We also do a web enabled application. Our #1 commandment: NO CODE RUNNING ON THE CLIENT.Sure it is harder to design the app in a way that the lack of interactivity does not become an obstacle and a nuisance, but it CAN be done. It can even be done so it works very nicely, thank you. We have no need to worry about Java, JavaScript, OCXs and all the other brain-dead gimmicks and half-aborted eye candy turned database access systems. Even ole HTML interpretation differences can be brought under control. Just so you know.

    21. Re:The problem with this bug by g0at · · Score: 1

      ...aaaaaaand... so how do you deal with things when the user has javascript turned off? Or has onunload() turned off? Sounds to me like you would no longer have a non-trivial, resilient web application.

    22. Re:The problem with this bug by foobar104 · · Score: 2

      Dude, before you get all smug, read this.

  16. Already fixed in Suse 8.0 by erik_fredricks · · Score: 2, Informative

    The YOU online updater in Yast has been set up to automatically download and install the patch for a coupla months now. Of course, it only applies to the default 0.98 Mozilla version included with the distro, but for those who haven't upgraded, it's there.

    --

    THE GOOD HUMOR MAN CAN ONLY BE PUSHED SO FAR
    Bart Simpson on chalkboard in episode 2F18

  17. Metered bandwidth by yerricde · · Score: 1

    Yea. So should Referrer be removed from existence.

    I respectfully disagree. Without the Referer: header, how is a developer supposed to know whether or not somebody else is leeching his bandwidth by linking directly to an image or to a large zip file, so as not to run into problems with metered bandwidth?

    --
    Will I retire or break 10K?
    1. Re:Metered bandwidth by Anonymous Coward · · Score: 0

      Well, that's why you put things on the web (a public forum)... For other people to point their browsers at.

      If you want to manage your access/popularity, you can implement user accounts. You can program for a "deep link redirection to a home page". You can implement URL encoding with your "friendly" sites.

      Anyway, Referer is already optional. I happen to run junkbuster - you get no stinking Referer from me.

    2. Re:Metered bandwidth by Anonymous Coward · · Score: 0

      Simple: when you hand out a URL to some kind of content that might be referenced by someone else, embed a variable. On the flip side, don't hand out the content unless that variable is valid - expire them every couple of days and you're done.

      Obviously this breaks caching, but you'll be hard pressed to find something else that works as well without any referer data.

    3. Re:Metered bandwidth by lostchicken · · Score: 2

      Server side systems.

      I don't know if something exists yet (if not, off to Apache module programming land for me), but the server should make sure that an IP has gotten an HTML page before it fetches an image or other large binary.

      The referer: header is good for keeping people in sites, but there is no need for the system to keep track of people coming from other sites, and being to identify those sites.

      --
      -twb
    4. Re:Metered bandwidth by DrPascal · · Score: 1

      This is absolutely true when catching the casual "hotlinker", but it's quite simple to tack on Referer headers with programs like wget, and most sites Referer checkers are more than satisfied with the exact same URL of the file you are downloading as the referer. For example, if I wanted to get http://www.download.com/downloadme.file, throwing in "Referer: http://www.download.com/downloadme.file" usually does the trick. It could easily be thrown into a script, and would be great for batch processing (getting many files without clicking through many pages of the same site).

      --
      DrPascal: Not the language, the mathematician.
  18. Muwahahaha by evilviper · · Score: 4, Informative

    Well, this just proves my point. Javascript should be disabled. (check my older posts, it's there somewhere).

    Anyhow, I think everyone should look into Privoxy [privoxy.org]. In my setup, I have all on(un)load tags removed, and the refer forged to report the it as root of the current server.

    It's quite nice. You simply setup a regex to replace/remove any HTML, you can configure that feature on a site-by-site basis, and do so using a simple web-editor.

    So, check it out, and take back full control of your browser.

    --
    Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    1. Re:Muwahahaha by Anonymous Coward · · Score: 0

      and the refer forged to report the it as root of the current server.


      Can you paste the lines to achive that feature? Thanks!
    2. Re:Muwahahaha by Anonymous Coward · · Score: 0

      Privoxy does indeed do a great job. This problem is fixed right out of the box (ie., the default config).

      I'm not sure some people would even consider this a bug though. Everyone seems to want to track what you're doing and what services you use.

    3. Re:Muwahahaha by NineNine · · Score: 1

      Well, this just proves my point. Javascript should be disabled

      Mozilla has a big hole in it, so instead of using a working browser, people should cripple their browsing experience? That's stupid. If the transmission in your car broke, you'd probably just drive around all day in first gear, right? C'mon, that's a fucking copout.

    4. Re:Muwahahaha by evilviper · · Score: 2

      No, it's not just Mozilla... Every single web browser I have ever even heard of has at least one huge, known, javascript flaw.
      The last time I brought this up, someone said the same thing about the Opera/Internet Explorer Javascript exploit.

      Besides, my more general problems concern that javascript gives anonymous webmasters the ability to use your processor for juat about anything they want...

      If they just wanted to annoy you, they can popup infinite windows (even with Mozilla configured to block them) to eat up your memory and CPU. They can have an infinte loop of javascript alerts (meaning all open browser windows lockup, and you are forced to kill your browser).

      Hell, a webmaster could even use javascript to record every movement of your mouse on every webpage they maintain...

      Considering that I've only ever seen ~2 useful applications of javascript, it doesn't even warrant a debate.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    5. Re:Muwahahaha by sheriff_p · · Score: 2

      A very nice plan, unless a website is using the Referer field for authentication, and then you're blocked out. Ach-well, if taking control of my browser means being locked out of many of the sites I visit, then I guess I'm happy being exploited by those evil people who *gasp* know which site sent me to them.

      --
      Score:-1, Funny
    6. Re:Muwahahaha by NineNine · · Score: 1

      Considering that I've only ever seen ~2 useful applications of javascript, it doesn't even warrant a debate.


      Well, then, have fun with the circa 1995 web sites you're playing with.

  19. Not so sure by einhverfr · · Score: 1

    [If the artible stated:]
    "The bug in Internet Explorerallows a web site to track where you're going when leaving the site whether you use a link, a bookmark or type a URL into the address field"

    you would hear a dplethora of privacy zealots bitching and moaning how this is typical M$ practice and blah blah fucking blah.


    I am not so sure.

    When Brian Valentine's email was leaked to the Register, I was amazed how many people on /. said, "It looks like a normal sales memo-- no big deal" when the Register was using it as evidence of the Vileness of Microsoft(tm).

    In general I think slashdot is a bit more diverse than you think.

    --

    LedgerSMB: Open source Accounting/ERP
  20. Not to knock Mozilla but... by FyRE666 · · Score: 3, Interesting

    The last few builds have introduced more bugs than ever. It seems to me that spangly new features are being introduced at the expense of the browser's stability and performance.

    For instance, the new keyboard stuff in 1.2a (ok, it's an Alpha I know), had screwed up Javascript's keydown events - the browser intercepts them first, then passes the event to the scripting engine so if a key is held down you get the anoying error "bell" as the buffer is filled. Keyboard events->javascript is/was also broken completely in the Mac/Linux port from 1.1. 1.2a is also slower than 1.1 at rendering dynamic content - especially content that involves keyboard input (like games) due to the problem above.

    Also when will they fix the damned image clipping bug in linux that's been there for 2 sodding years now?!! For those who haven't seen it, when clipping an element containing images that have transparency, everything except the images will be clipped, completely ruining the layout of dynamic scripts.

    I guess no-one wants to work on the boring stuff like making it work when there's sidebars, tabs and themes to be had...

    </rant>

    1. Re:Not to knock Mozilla but... by Anonymous Coward · · Score: 1, Informative

      well, I think that you solved your own problem. If you don't need the extra features, don't use the alpha builds, they ARE unstable by nature. Use the 1.0x series, that is stable.

    2. Re:Not to knock Mozilla but... by Anonymous Coward · · Score: 0

      And you've contributed what to the project? Those who do do, those who can't rant.

    3. Re:Not to knock Mozilla but... by FyRE666 · · Score: 2

      ...don't use the alpha builds, they ARE unstable by nature. Use the 1.0x series, that is stable.

      Yes it's stable, but it's also too slow to take seriously. 1.1 wipes the floor with 1.0 in terms of rendering speed with dynamic content. I need to know the direction the browser is taking all the time as I maintain a javascript API for game-writers. I have to know what's changing before the stable release.

      At the moment I'm becoming so despondant with more and more things becoming broken, and consequently having to add more and more code forks that dropping all Mozilla support until they fix things is looking more likely.

      I hate IE only sites more than anything, but the Mozilla developers are making it very hard to support their browser. I'm not the only scripter saying this either. They just don't seem interested in addressing the problems reported to them (as I do frequently on Bugzilla, taking time to create examples and documenting the problem, though it gets me nowhere).

    4. Re:Not to knock Mozilla but... by BZ · · Score: 2

      The number of people who know enough about the view manager to fix that clipping bug is about... 2. Of these two, both are full-time students (one's a grad student who spent the summer actually trying to make progress on his thesis). So they just haven't had the time to get into this problem....

    5. Re:Not to knock Mozilla but... by roca · · Score: 2

      You're lying. I'm not a full-time grad student, and if I had a bug number for this guy's bug, I'd fix it.

    6. Re:Not to knock Mozilla but... by ealar+dlanvuli · · Score: 2

      Anyone using a non-major release dosen't need supported. I've seen nightly builds that wouldn't let me hit the back button before, these things are *not* ment for grandpa to be browsing in.

      You have no obligation to support anything but major releases, and they will always be easy to support, end of story.

      --
      I live in a giant bucket.
    7. Re:Not to knock Mozilla but... by Anonymous Coward · · Score: 0

      I guess that would be bug 78497 - and you said you'd fix it, not reassign it :P

    8. Re:Not to knock Mozilla but... by asa · · Score: 2

      For instance, the new keyboard stuff in 1.2a (ok, it's an Alpha I know), had screwed up Javascript's keydown events....

      Say it with me again, slowly this time. "Aaalphaaa". Now, one more time. "Aalphaa". Again. "Alpha". Feeling better? Urge to rant fading? Gooood.

      --Asa

    9. Re:Not to knock Mozilla but... by Anonymous Coward · · Score: 0

      COme back and say that when it's released with that and 100 more bugs in it like every soingle other mox release in the last several years.

    10. Re:Not to knock Mozilla but... by yakovlev · · Score: 1

      Do you get pre-release builds of IE?

      If you do, and they are higher quality than the pre-release builds of Mozilla that you are using, then I can at least understand your frustration.

      If you don't get pre-release builds of IE, then why are you upset about the instability of Mozilla pre-release builds? The other platform that you cite gives you NO access to "know the direction the browser is taking all the time."

      So, unless you get pre-release builds of IE that are more stable than the pre-release builds of Mozilla, then Mozilla gives you more of a choice. You can either have no idea of the future state of the browser (as you do with IE) or you can get alpha builds that break things, as alpha builds tend to do. If you choose the former, then just support Mozilla 1.0 and ignore the later versions until an official release arrives. If you choose the latter, then you'll have to put up with changing versions and compatibility, but realize that you have chosen this instability in exchange for information about upcoming but unreleased products.

    11. Re:Not to knock Mozilla but... by FyRE666 · · Score: 2

      For the record, I consider every version of IE a "pre-release". The difference is, I don't care enough about MS to rant about it's unnumerable problems - I could list them, but they have enough money already that I don't feel like giving them free feedback. Let them pay for testers.

      My point is that the bug count appears to be climbing as each release appears from my point of view. I don't care about the aesthetics - I'm only interested in the layout/scripting side. The clipping bug remains, the keyboard bug remains and in fact appears to be getting worse as the new features are added.

      If I didn't give a shit about Mozilla I wouldn't even take the time to mention my problems - I'd just stick with another browser and ignore it as too many others do already. But I don't, I've encouraged plenty of people to switch - at least for the email client (which itself saves me having to reinstall Win whenever another virus of the month is installed by some... well... idiot).

  21. Mozilla .... you are the weakest link by Boogey · · Score: 1, Funny

    The latest reason to switch to Konqueror.

    1. Re:Mozilla .... you are the weakest link by Anonymous Coward · · Score: 0

      With no XSLT? I don't think so.

      Welcome to the new web.
      Konqueror and Opera are not included.

    2. Re:Mozilla .... you are the weakest link by Glytch · · Score: 2, Offtopic

      Either that, or Opera.

      I'd switch to Konqueror in a heartbeat if it supported a way to hand off the URL of a link to another program, though. I love Konqueror, but I love Downloader for X more.

      Offtopic, but did are KDE developers going nuts on optimizations? Built 3.0.3 yesterday, and it just flies on my old K6-500.

  22. Re:A happy thing about this... by noshellswill · · Score: 0

    Two checkmarks, and I think PROXO kills this onload/onunload crap dead. Doesn't everyone use it?

  23. (meta) Plain Old Text vs. Extrans by yerricde · · Score: 1

    (Why don't < and > work when I select "Plain old Text"?)

    1. Use the Preview button to avoid submitting comments with mistakes.

    2. According to this FAQ page, Plain Old Text only converts newlines to <br>. You're looking for Extrans, which also escapes &, <, and >.

    --
    Will I retire or break 10K?
    1. Re:(meta) Plain Old Text vs. Extrans by Anonymous Coward · · Score: 0

      1. Use the Preview button to avoid submitting comments with mistakes.

      Shut the fuck up, you arrogant, pedantic motherfucking son of a whore. You're sitting in a big glass house with a handful of rocks, do you realize that? Fucktard.

  24. My advice-- by einhverfr · · Score: 3, Insightful

    If you think that all that matters is whether the /. community things something is secure or not, then you are looking in the wrong place.

    In the real world, there will always be security problems. THe real issue is the scope of those problems. I happen to think that Mozilla and open source software in general tends to be more secure (aside from old versions of BIND and all versions of Sendmail).

    If security is what you want, do a risk assessment, and look at the actual ways that different products will mitigate those risks. If you use Linux because it is "More Secure" then you are asking for trouble. So, you need to make up your own mind and determine what you need to do.

    In other words, don't follow someone's oppinion until you understand why they think that way and whether it applies to your situation.

    --

    LedgerSMB: Open source Accounting/ERP
    1. Re:My advice-- by packeteer · · Score: 2

      Ok fair enough... decide for myself. But the reason i asked is because this seems to not be a very large problem and i wanted to know other's opinions on it. All software is insecure to some degree and what i really wanted to know was what exactly should i be worried about and what should i do. from reading other posts this seems to not be a big enough deal to do anything.

      --
      unzip; strip; touch; finger; mount; fsck; more; yes; unmount; sleep
  25. O wow... by miketang16 · · Score: 0

    Eh.. it's not that bad of a bug, but I patched it already. I love Mozilla it's so great. You get everything that every other browser has PLUS more. And it's open source! What more could you ask for?

    --
    -------
    "In times of universal deceit, telling the truth becomes a revolutionary act."
    -- George Orwell
    1. Re:O wow... by Anonymous Coward · · Score: 0

      You could ask for it to suck less. Alas, only commercial software-- built by professionals, for professionals-- can approach an acceptable degree of quality. But since you're probably a mouth-breathing loser who sleeps in his mom's basement and who has never had a job that doesn't come with its own paper hat, you have neither the money nor the means to obtain the money to buy commercial-- i.e., good-- software.

      So what more could you ask for? Nothing at all. You've got everything you deserve.

  26. Explanation of exit tracking by yerricde · · Score: 2

    It's more or less the inverse, this bug enables the referer to know where they refered you to.

    Grandparent was talking about the CGI scripts used to track users who click an outward link on a web site. (Some Slashdot users abuse those scripts to create a link that appears to go to Yahoo! but really goes to Goatse.cx.) However, this bug in Mozilla gives a site's scripts access to a clicked bookmark or to a URL entered in the location bar.

    --
    Will I retire or break 10K?
  27. Umm, I cannot reproduce this... by jonadab · · Score: 1

    The demonstration doesn't work for me.
    Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2a) Gecko/20020910

    Maybe it's something about the way I'm using tabbed browsing, or
    my cache settings (once per session), but I can't get the demo
    to work at all. It always gives the URL of the demo as referer.
    Yes, I have cookies enabled (though I limit their max lifespan).

    Weird.

    --
    Cut that out, or I will ship you to Norilsk in a box.
  28. You can't put ads in a zip file by yerricde · · Score: 1

    Well, that's why you put things on the web (a public forum)... For other people to point their browsers at.

    But when other people link directly to non-HTML files, your advertisers don't pay you. That's why GameFAQs.com allows linking only to HTML pages.

    I happen to run junkbuster - you get no stinking Referer from me.

    Many popular download sites (fileplanet, gamespy, gbadev.org, etc.) happen to run a leech script - you get no stinking cool apps from them.

    --
    Will I retire or break 10K?
    1. Re:You can't put ads in a zip file by commodoresloat · · Score: 2
      But when other people link directly to non-HTML files, your advertisers don't pay you.

      Without the Referer: how do they know where the links are coming from?

      That's why GameFAQs.com allows linking only to HTML pages.

      Exactly - a solution that doesn't involve Referrer.

    2. Re:You can't put ads in a zip file by yerricde · · Score: 1

      [Allowing links from outside GameFAQs.com to link only to HTML pages is] a solution that doesn't involve Referrer.

      Without the Referer: header, how is the GameFAQs server supposed to know if a link is from outside or not?

      --
      Will I retire or break 10K?
    3. Re:You can't put ads in a zip file by commodoresloat · · Score: 2

      It doesn't need to; it just needs to know whether the client is asking for .html or .htm .... right?

    4. Re:You can't put ads in a zip file by Anonymous Coward · · Score: 0

      fileplanet, gamespy

      I go out of my way to not use these whores' services. Fuck them and thier "sign up for free" to access files that belong in the public domain when free= get put on 15 different spam lists.

      It was much easier when you could just get files from a directory on an ftp, now its http asp bullshit.

    5. Re:You can't put ads in a zip file by lamp77 · · Score: 1

      No, cause then your browser goes to get the images linked from that html, that's where the referrer comes in. Remeber, pages are many files, not just an 'html' file

    6. Re:You can't put ads in a zip file by commodoresloat · · Score: 2

      D'oh! yeah I did nknow this; just wasn't thinking. It still seems there should be a way to tell wihtout Referrer: since a single image requested by a user-agent that isn't requesting html files could be blocked. It's been a while since I messed with apache settings and I guess it shows; heh.

    7. Re:You can't put ads in a zip file by elphkotm · · Score: 1

      YEAH! Screw them and giving away all that bandwidth and server resources! OMG How dare they actually require you to try to help them make money! AND GOD FORBID if they ever wanted to actually CHARGE us money, oh my eff!!

      --

      <Amanda`> I just went out to the parking lot in my bathrobe to exchange warez CDs.
  29. cookie, cookie, cookie by Parsec · · Score: 2, Interesting

    For this demonstration, the image loaded is really a script that sets a cookie with the request referer.

    I just said "no" to the cookie dialog and that appears to have broken the example.

    If you're going to raise a stink about your browser's security, why are you accepting any and all cookies?

    1. Re:cookie, cookie, cookie by lamp77 · · Score: 3, Informative

      Dude, the first line reads

      For this demonstration, you need to enable cookies. The bug itself does not require cookies to be enabled, however.

      I think that explains the situration pretty clearly.

  30. I can't get the demo to work... by symbolic · · Score: 2


    I looked at my settings, and was amused to find that I had disabled javascript's ability to create/mess with cookies. I'm happy the Mozilla team partioned the javascript functionality like this, because (it appears anyway) that until a bug fix is available, you only have to disable this one aspect of javascript.

    1. Re:I can't get the demo to work... by superpeach · · Score: 3, Informative

      The bug has nothing to do with cookies, the cookie is just so that the demo site can tell you where you went after visiting there. The problem is with the window.onunload javascript function - so either that needs to be disables, or all of javascript (the instructions are on the demo page for how to only disable onunload). All that stopping javascript playing with cookies will do is stop the demo from being able to tell you where you went, the server operators can still find out if they wanted.

  31. Moron moderators: by Anonymous Coward · · Score: 0

    How in the hell do you go from funny to offtopic, when the post is clearly related to the one that is funny?

    1. Re:Moron moderators: by foobar104 · · Score: 2

      How in the hell do you go from funny to offtopic, when the post is clearly related to the one that is funny?

      Funny trumps off-topic. A post that's both funny and off-topic will be moderated as funny. A post that's merely off-topic-- without being funny-- will be moderated off-topic.

      This should be obvious. Perhaps your trouble is that you're an idiot?

    2. Re:Moron moderators: by Anonymous Coward · · Score: 0

      im an idiot, and i understand it.

  32. user.js fix by kbolton · · Score: 1

    user_pref("capability.policy.default.Window.onunlo ad", "noAccess");

    while you are at it, throw in these to stop pop-ups:
    user_pref("dom.disable_open_during_load" , true);
    user_pref("dom.disable_open_during_close", true);

    1. Re:user.js fix by Anonymous Coward · · Score: 0

      If you cant get anything better than a 28Kbps connection, those popup disabling optiong could end up being more annoying than the popups themselves. So many sites now use popups when they are not needed, and they also have wanky flash animations and big images to load. Disabling popups would mean waiting a few minutes for the entire page to load before you can do what you wanted to do. This page is an example, although this is one of the quickest to load.

  33. Fix explained in demonstration page by Fastball · · Score: 2

    If you care to follow that link...

  34. Re:Is there? by Anonymous Coward · · Score: 0

    Just in case you're not being funny, Google out PAN (for pimp-assed newsreader).

  35. I use Netscape 3.0.1 ONLY (check my referral) SAFE by Anonymous Coward · · Score: 0

    I use Netscape 3.0.1 ONLY (check my referral) SAFE AS ALWAYS

    All versions vefore 3.0.1 gold for mac and after 3.0.1 have security issues. (java, email, exploits, javascript, cookies, etc).

    3.0.1 has no problems and the Mac OS 8.6 (also in use as I type this) also has no security weaknesses according to bugtraq.

    I use many OSes, and many browsers for SSL related activities (rare), but only surf the net using 3.0.1

    I said I would upgrade if ANY BROWSER LASTS 2 YEARS WITHOUT A SECURITY INCIDENT.

    I have restated my vow every year since 1995.

    And I laugh my ass off when IE and netscape have weakenesses in then that my trusted 3.0.1 browser is immune to. Too bad netscape did not ever release its source code, and only releases its stillborn buggy code to the mozilla effort.

    Hurray for IE and Mozilla security defects! They vindicate my security aware habits!

  36. Yet another reason 2 switch 2 Internet Explorer by Anonymous Coward · · Score: 0

    Yet another reason 2 switch 2 Internet Explorer

  37. Chimera Users by imag0 · · Score: 1

    If you use Chimera in OS X, browse to your:
    /Users/*your username*/Library/Application Support/Chimera/Profiles/default/*salted name*.slt/ directory and edit the prefs.js file with vi, or BBEdit (which is the default editor on mine).
    Add the line:
    user_pref("capability.policy.default.Window.onunlo ad","noAccess");
    To the bottom on the file,save your changes and restart your browser. Careful of the space slashcode likes to put in there! Should be no spaces in the line you past into the file.

  38. Re:Open source security Right on Man by Anonymous Coward · · Score: 0

    Thats why there are these kinds of hacker problems everyday in the open source world. Every day. Now if the source were closed none of these problems would exist.

  39. I hate to defend Microsoft... by coene · · Score: 4, Insightful

    But why is it when its an IE bug, its a "Severe Security Exploit", and when its a Mozilla bug, its a "Privacy Leak"...

    George Carlin said it best, that we think in language. Changing the rhetoric that is used to describe the problem doesent change the problem. You can be Anti-Microsoft all you want, but that is worth NOTHING if the software that you choose to use exhibits the same problems, and you are not honest about them.

    Again, I'm not taking Microsoft's side -- there aren't sides to take. Open Source software needs to be just as accountable as commercial software if it's to be taken seriously.

    1. Re:I hate to defend Microsoft... by brettlbecker · · Score: 3, Insightful

      There is a bit of a difference between allowing a server to track your next site from their own site and a hole in IE allowing a hacker to enter and exploit your system, or a hole in OE that allows viruses to propgate, using your machine like a 2-dollar whore. You're right on two points-- it is still privacy. But there is a distinct difference between someone watching you to see where you live and the act of breaking in to your home to steal your underwear. And yes, open source software needs to be just as accountable. And I'm sure they will be... they'll fix this problem. Whatever the semantics, it is still a problem and it will still be fixed.

      --
      "We must still have chaos within in order to be able to give birth to a dancing star." --Friedrich Nietzsche
    2. Re:I hate to defend Microsoft... by jesser · · Score: 2

      But why is it when its an IE bug, its a "Severe Security Exploit", and when its a Mozilla bug, its a "Privacy Leak"...

      Umm, maybe because this bug isn't severe? It only lets a malicious site find out what URL you visit immediately after leaving the site. I'm much more concerned about IE's policy of allowing sites to read from and write to the clipboard than I am about this bug.

      --
      The shareholder is always right.
    3. Re:I hate to defend Microsoft... by evilquaker · · Score: 1
      But why is it when its an IE bug, its a "Severe Security Exploit", and when its a Mozilla bug, its a "Privacy Leak"...

      Probably because when it's IE, it really is a severe security exploit (i.e. a remote hole), and when it's Mozilla, it really is a privacy leak (someone can find out one page that you visited).

      --
      To within half a percent, pi seconds is a nanocentury. -- Tom Duff
    4. Re:I hate to defend Microsoft... by caferace · · Score: 2
      Hmm. Take a look at the few posts above yours. Several of them describe how to fix the problem. Immediately. All you have to do is hack the prefs.js file, restart the browser and you're all set.

      Now explain to me how you could do the same thing with IE.

      I'll not be holding my breath....

    5. Re:I hate to defend Microsoft... by tres3 · · Score: 1

      Is this what George Carlin meant when he said your possessions are stuff and others are shit. Hense the two sayings: "Hand me my stuff." and "Get your shit."

    6. Re:I hate to defend Microsoft... by geekoid · · Score: 2

      Orwell said it first. That is what 1984 is about, controlling pepole with language.

      second, this is something all browsers do. Some browser have the ability to turn it off. I have actually used this feature for web based apps I've written for internal use.

      That said, I would like the ability to easily turn it off. Mostly so People I know that don't know how to code can turn it off.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    7. Re:I hate to defend Microsoft... by unixfd0 · · Score: 1

      But why is it when its an IE bug, its a "Severe Security Exploit", and when its a Mozilla bug, its a "Privacy Leak"...

      Slashdot (to me) is a basically a digest of the day's events. If people take news about Mozilla from Mozilla.org then the headlines are going to be less severe than if they took the headline from Microsoft.com. Half of all the "Severe Security Exploit" headlines about IE are magically changed to "Insignificant Privacy Leak" on MS sites. It just depends on where you get your news...you have to make the distinction for yourself ;)

    8. Re:I hate to defend Microsoft... by NineNine · · Score: 1

      Well, MS wouldn't let a hole go unpatched for 3 months. I'd click on Start, Windows Update. Or even better, it's set to automatic, and it'd be patched automatically before it's a problem. No need to wait around for months, then when it doesn't show up (the patch, that is), edit some obscure text file.

  40. Re:I use Netscape 3.0.1 ONLY (check my referral) S by Anonymous Coward · · Score: 0

    You are an idiot. While Netscape 3 may be bug free, it is nowhere near the current level of standards on the internet. Many sites use CSS, Flash, JavaScript, etc. that your pathetic browser does not support.

  41. Once again...Opera by Anonymous Coward · · Score: 0

    I say try Opera, they seem to be less bug ridden than Mozilla and IE recently!

  42. TEST REPORT: This bug is mostly FUD by Anonymous Coward · · Score: 0, Interesting

    After testing the bug site listed, it looks like this privacy leak doesn't actually follow you around, but, only reports the NEXT PAGE you look at.

    I jumped around to various pages, and, it only recorded the mozilla.org link. AFAIK, you only get the very next page linked from the exploiting referrer.

    So, unless slashdot is a participant in this scheme :), you would need a bunch of websites to be running this exploit and sharing data to get much info out of it.

    Severity = TAFNAB

  43. Why don't _you_ decide instead? by ebbomega · · Score: 2

    Honestly, this is a _NEWS_ site, not a list of programs you're supposed to use. So, there's some _good_ stuff out there about Mozilla, there's also some bad stuff.

    Just be thankful it's open-source, because that means that there's a couple million people who can help fix it.

    --
    Karma: Non-Heinous
  44. Ignorant Open Source Fools by Anonymous Coward · · Score: 0

    Opensource has the same problems as proprietary. It is irresponsible for opensource users to think that problems will be fixed *immediately*. Anyone who thinks that opensource is a be all and end all and all problems found will be fixed as soon as discovered needs their freakin head checked, then fired if they're involvement has to do with a production environment.

  45. Oops, maybe not by bahamat · · Score: 1

    I don't know about any of the rest of you, but I use galeon, and I tried a link, a bookmark and typing my own url. Each time returning to the page that suposedly demonstrates this exposure I got url=unknown.

    1. Re:Oops, maybe not by superpeach · · Score: 1

      Did you make sure you reloaded it? :) oh.. and did you have images enabled (might make a difference, not sure)

  46. Doesn't apply to me! by Anonymous Coward · · Score: 0

    I stopped the link page from loading, leaving the original URL in the url box, click there, hit enter, and voila -- no HTTP_REFERER!

    Since I am so smart, obviously I am not a slashdot moron, the redirect doesn't apply to me, and neither does your comment! ppppphhhttt!

  47. bug? by bilbobuggins · · Score: 4, Interesting
    I don't understand how this is a 'bug'.

    First of all, this does not allow someone to track where you're going but rather where you went. I know that sounds like nitpicking, but really it's the difference between a bug and a correct protocol implementation.

    The method described is to check the referrer on requests sent to a particular server after the user has left a page on that server. Surprise! the referrer is now their current location i.e. where they went after your site.
    Would you expect any different?
    It's matter of micro-seconds and request timing.
    Ok, maybe they could make sure all requests generated by an 'onunload' event are handled before the request to the following page, but personally I would consider that a judgement call and not 'bug'.

    Also, I've noticed people here don't seem to give a hoot that your entire history of where you came from can be far more easily tracked!

    1. Re:bug? by pbryan · · Score: 2

      This is a bug and it does allow someone to track where you're going. The proof of concept page clearly states that the "referer of the http request for this image will be the page you are visiting next , not this page " (emphasis is theirs). I expect that when JavaScript is executing for the page I am leaving, that it have no idea where I am going. Anything otherwise is a breach of privacy, and should be considered a bug.

      --

      My car gets 40 rods to the hogshead, and that's the way I likes it!

  48. Easy Fix! by zeekiorage · · Score: 1

    Here is an easy fix,

    1. In Mozilla goto ...
    'Edit | Preferences | Advanced | Script & Plugins'

    2. Uncheck the following checkboxes ...
    'Ceate or change cookies' and 'Read Cookies'

    After changing this goto the demo page again to verify! The demo will not work anymore.

    1. Re:Easy Fix! by moogla · · Score: 3, Insightful

      NO.

      The implementors of the demo were lazy (having no server-side scripting) and used a cookie to record the information leaked by onUnload. You are in no way protected by disabling cookies.

      That just breaks the demo, the vulnerability is still there.

      --
      Black holes are where the Matrix raised SIGFPE
    2. Re:Easy Fix! by Anonymous Coward · · Score: 0

      zeekiiorage -- Please pull your head out of your butt. The test page plainly states that it requires cookies, but the the actual exploit does not.

    3. Re:Easy Fix! by zeekiorage · · Score: 1

      Sorry! Didn't read the note at the top of the demo page!

  49. a better Referer: header? by yerricde · · Score: 1

    it just needs to know whether the client is asking for .html or .htm .... right?

    It needs to know if the request for a .png or a .zip came from within the site or from outside. That's only possible with HTTP's Referer: header. However, the Referer: header could be improved: reveal only the referring hostname, not the referring page.

    --
    Will I retire or break 10K?
  50. Dear BugZilla morons by MicroBerto · · Score: 2, Troll
    No. If this bug was fixed months ago when it was first detected, then there would have been no problem. However, the slashdot ultimatum was issued and appropriately followed through.

    We will not tolerate ourselves to look stupid while accusing other companies of leaving security holes for months, and then doing it ourselves. Do it again, and we will slashdot you again. And yes, we will defeat your referrer. Thank you, have a nice day. :)

    --
    Berto
    1. Re:Dear BugZilla morons by Anonymous Coward · · Score: 0

      Unfortunately, FreeBSD's platform list does not say anything about the Commodore 64. It is hardly a replacement for LUnix, then.

    2. Re:Dear BugZilla morons by Anonymous Coward · · Score: 0

      w00t!

    3. Re:Dear BugZilla morons by shren · · Score: 2
      Chill!

      It's not a "we get to rape your local filesystem" bug. It's a "web surfing history" bug. It's not that scary.

      I prefer to look at the bright side. It's fixable with a userland .js file with no recompiling. That's sort of neat.

      --
      Maybe the state's highest function is to grind out insoluble problems. (Zelazny, Hall of Mirrors)
  51. Re:I'm surprised.. (corrected) by Anonymous Coward · · Score: 0

    .. how many people are saying "no big deal". If the article stated:

    "The bug in Internet Explorer allows a web site to track where you're going when leaving the site whether you use a link, a bookmark, or type a URL into the address field."

    You would hear a plethora of privacy zealots bitching and moaning about how this is typical MS practice and blah blah fucking blah.

    Because of a /. article and because I'm OS/Software agnostic, I tried Mozilla 1.0 which was a horrible product. I could repeatedly lock up the browser simply by going into the preferences. Maybe it's been fixed 1.0.1, but I'm not willing to waste my time, especially since IE runs just fine.

    I have excellent Karma, so if you can't handle the truth, mod me down. I don't give a shit. I'm just sick of the "hypocritical oath" /. editors have taken.

  52. Moz 1.0 + user.js on Win XP by surfimp · · Score: 1

    On XP, your user.js file goes in the following directory:

    C:\Documents and Settings\\Application Data\Mozilla\Profiles\default\.slt\

    (You will need to enable "Show Hidden File Types" in order to view the Application Data folder)

    Just open up Notepad (or whatever) and created a new file, naming it user.js. In order to fix the privacy bug, all you need is the following line:

    user_pref("capability.policy.default.Window.onun lo ad", "noAccess");

    Hope that helps!

  53. That should be "umount", not "unmount"... by Chuck+Messenger · · Score: 1

    ...(like the subject says)...

    1. Re:That should be "umount", not "unmount"... by Anonymous Coward · · Score: 0

      yeah, hes a Mandrake user...what do ya expect ?

  54. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  55. Re:I use Netscape 3.0.1 ONLY (check my referral) S by saskboy · · Score: 1

    I do not see how one is an idiot for maintaining operability with old technology. The wheel works fine for me, do you think the new Octagon wheel will be an improvement?

    --
    Saskboy's blog is good. 9 out of 10 dentists agree.
  56. So block the referer by Anonymous Coward · · Score: 0

    user_pref("network.http.sendRefererHeader", 0);

  57. Hello by Anonymous Coward · · Score: 0

    Yes, I agree with this guy. You are, indeed, a fucking idiot.

  58. Mod Parent Up! by cscx · · Score: 2

    Any developer who puts the username and password in a URL should be shot. And any user who sees their password in the URL in plainsight and doesn't complain, or stop using the services, shouldn't be allowed near a computer to begin with.

    See parent comment aboot Slashcode.

  59. So What ??? by Anonymous Coward · · Score: 0

    Big deal, they can tell where you are going. How's that a problem unless you are logging onto a site that has your name & address. After all tracking IP addresses and who uses them among millions of dialup users should stretch thin any org. And if they are that good, you are hosed anyway. Plus, that IP information should be protected by your ISP. Pffft :p

  60. Re:I use Netscape 3.0.1 ONLY (check my referral) S by foobar104 · · Score: 2

    Heh. This post reminds me of the old Far Side cartoon. A caveman is trying to sell another caveman a car. In the background you see lots of Fred Flintstone-style caveman cars, each with square wheels. The car in the foreground has triangular wheels. The salesman is saying, "This new, improved model. Has one less bump."

    Yeah, I'm off-topic. I'm way the fuck off-topic. I'm so off-topic, I'm not even going to mention the topic (although I could, just to stay topical). Mod me down if you want. I've got karma to burn, and I'm feeling grouchy and self-destructive.

  61. Not to defend either one, but.. by Reziac · · Score: 2

    I'd define the terms thus:

    Privacy leak: lets someone else see what I'm doing or where I'm going. Does not let them see into my system.

    Security exploit: lets someone else see the contents of my HD.

    Severe security exploit: lets someone else *manipulate* the contents of my HD, pilfer my credit card number, or something else on that order.

    --
    ~REZ~ #43301. Who'd fake being me anyway?
  62. Re:Here's a solution: by foobar104 · · Score: 2

    Conclusive proof! Making a disparaging comment about Mozilla-- or Linux, or Gnome, or KDE, or any of that shit-- is, prima facie, enough to get moderated down on Slashdot. Somebody threw this AC a downmod just because he said that one option-- and possibly the best one-- was not to use Mozilla.

    I will mail one crisp new American dollar, postage paid, to the first person who moderates this comment down. Send your claim to foobar104@yahoo.com.

  63. blame slashdot by Anonymous Coward · · Score: 1, Interesting
    >> But why is it when its an IE bug, its a "Severe Security Exploit", and when its a Mozilla bug, its a "Privacy Leak"...


    It isn't "Open Source's" fault. Slashdot is to blame. They are just extremely biased toward open source.


    Slashdot really sucks nowadays. There are better alternatives. Check out


    Quit Slashdot Movement.

    1. Re:blame slashdot by PurpleBob · · Score: 1

      I hate to burst your bubble, but reading Slashdot and all the comments waiting for the opportunity to tout your movement doesn't especially sound like "quitting Slashdot" to me.

      But then, you're not the first person to post "Hey look at me! I've stopped reading Slashdot! Ain't I special?!" without noticing the inherent contradiction.

      --
      Win dain a lotica, en vai tu ri silota
  64. Where is the power of the OSS? by Anonymous Coward · · Score: 0

    So, I guess that this is another selling point that the OSS movement will use in the future to push OSS on everybody.

    That you as an individual don't have to wait around for some slow lazy company who is only interested in receiving you checks to get off their duffs to write a fix.

  65. Re:I use Netscape 3.0.1 ONLY (check my referral) S by saskboy · · Score: 1

    Don't feel bad about being OT. It made me laugh.
    In fact I'll follow in your fine tradition of making people laugh, and not mention how this fits in to the topic either.

    --
    Saskboy's blog is good. 9 out of 10 dentists agree.
  66. fuck you slashdot! by Anonymous Coward · · Score: 0

    Yeah, troll whatever..Truth is, if this was a story about a security hole in all versions of IE that had been known for months there would be 500 comments already. You really need to change your slogan to "MS SUCKS! LINUX ONLY MATTERS!". The slashdot community's bias is just as evil as MS's monopoly. Go fuck yourself slashdot for parading as a place for real news while in reality you all are nothing more than a bunch of linux cheerleaders.

    -AC cuz I dont need a crap account.

  67. oops, will have to quit mozilla now by kousik · · Score: 1

    Too bad I have to quit moz to get the prefs in. Isn't there a JS
    which can patch the hole without having to quit? Sucks.

  68. OT: Idea share? by Xerithane · · Score: 0, Offtopic

    I'm currently developing a javascript based framework that relies on a few open child windows. Creating a list of open windows has been done, but I'm not exactly happy with the codebase. This is my first experience with JavaScript. What method do you use for knowing which child windows have been open and their status?

    --
    Dacels Jewelers can't be trusted.
    1. Re:OT: Idea share? by foobar104 · · Score: 2

      In all honesty, I don't think we do. Our app is meant to be fairly modal; i.e., when a daughter window opens, the user is expected to deal with it, then close it, then go back to the main window. So we don't need to keep track of several open windows at once.

      Sorry I couldn't help more.

  69. Because unlike IE I can uninstall Mozilla by Vicegrip · · Score: 2

    Nothing gets my goat more than having crappy software shoved down my throat with a "and you will like it" to wash it down.

    I'm tons more willing to cut some slack to a free and open source project for a minor issue than to let off some corporation responsible for riddling my machine with security problems I can't uninstall-- and routinely refuses to fix ina timely manner.

    --
    Do not spread "09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0" over the internet, thank you.
  70. Re:this is redundant -- by Anonymous Coward · · Score: 0
  71. Ignorance and Foolishness rated as Insightful by Anonymous Coward · · Score: 2, Informative

    The poster asks:

    > But why is it when its an IE bug, its a "Severe Security Exploit", and when its a Mozilla bug, its a "Privacy Leak"...

    And it is currently rated as "Score:5, Insightful".

    I fear that Slashdot's moderation facility is being used by Microsoft as another FUD tool. While some posters try to moderate honestly, Microsoft astroturfers moderate each others' posts up, thus increasing their karma, and giving themselves more power to moderate.

    There is no objective basis by which the above post could be considered "insightful".

    In fact, the above post is completely stupid.

    The post suggests there is something wrong when some IE vulnerabilities have been rated "Severe", while this Mozilla vulnerability is just rated as a "Privacy Leak".

    Let's consider that.

    Should this Mozilla problem be considered as "severe"? Hardly. As others have pointed out, providing the URL of the site you are going to is not that different from what all browsers have always done when they provide the URL of the site you came from. In fact, the problem is so minor that I am not even going to bother installing the fix until the next browser release comes out. When referring to this problem, the words "Privacy Leak" are, if anything, too strong.

    On the other hand, let's consider some of the _19_ currently unpatched security holes in IE.

    Here are some samples:

    > Who framed Internet Explorer
    > Description: Cross-protocol scripting, arbitrary command execution, local file reading, cookie theft, website forging, sniffing https, etc.


    > MS JVM native method vulnerabilities
    > Description: A collection of at least 10 different vulnerabilities in the MS JVM, escaping the sandbox, local file reading, silent delivery and execution of arbitrary programs, etc.


    > WMP Stench
    > Description: Silent delivery and installation of an executable on a target computer


    > Java XMLDSO base tag
    > Description: Arbitrary local file reading.


    > delegated SSL authority
    > Description: HTTPS spoofing, man-in-the-middle attacks, etc.


    > document.domain parent DNS resolver
    > Description: Improper duality check leading to firewall breach


    > CTRL-key file upload focus
    > Description: Local file reading, downloading and executing arbitrary code.


    Arbitrary command execution? Local file reading? Escaping the sandbox? HTTPS spoofing? Firewall breach? Should any of those be considered "severe"? You betcha!

    In fact, of the nineteen open security holes in IE, nine of them allow binary executable code to be run on your computer.

    So clearly, the original poster is an idiot. Objectively, his post should be rated "Score:-1, Troll".

    I would say that the posters who moderated his post up are even bigger idiots, but I don't believe that to be the case. Instead, I figure they're probably professional liars, being paid by Microsoft.

  72. I AGREE WITH THIS POST! by Anonymous Coward · · Score: 0

    i agree with this post.

  73. Solution for windows machines by Master+Of+Ninja · · Score: 1

    I tried the test and I think the problem is basically caused by the HTTP referrer field (as another post mentioned below). This isn't exactly a new exploit (from my understanding) but a function of the the HTT-Protocol that not many people seem to know about.

    If you've got a windows machine machine you can get the Agnitum Outpost firewall. Not only is it a good firewall (Zonealarm screwed up my machine) but it can block ads , content (based on what sites you tell it to block) and can block referrers. You can also write plugins for the firewall to do other functions. (PS I don't work for these people - i just use and like the firewall)

  74. Re:Here's a solution: by Anonymous Coward · · Score: 0

    Conclusive proof! You're a fucking idiot. Shut the hell up before you hurt yourself.

  75. Re:this is redundant -- by Dahan · · Score: 2

    I find it unconscionable that such a gaping hole has been allowed to remain over a month... shame on the Mozilla team :(

  76. That site... by Cl1mh4224rd · · Score: 1

    You know, it really bothers me when a site designer can't be bothered to set a background color for the page, and just assumes the visitor's default window background is white.

    People who do that need to be smacked around a bit.

    --
    People will pass up steak once a week, for crap every day.
  77. Congratulations... by Cl1mh4224rd · · Score: 1

    You managed to discover the obvious.

    --
    People will pass up steak once a week, for crap every day.
  78. cbe by Anonymous Coward · · Score: 0

    Interestingly, the onunload fix suggested by the
    referred page breaks cbe (crossbrowser) features.
    Haven't had the time to look into exactly what
    breaks, but my (quite standard) popups stopped
    popping up...

  79. Unfair Moderators by Anonymous Coward · · Score: 0

    Ah, now we see the violence inherent in the system. Come and see the violence inherent in the system. Help! Help! I'm being repressed!

    Oh, what a give away. Did you here that, did you hear that, eh?.... That's what I'm on about -- did you see him repressing me, you saw it didn't you? See that?

    ----

    Yeah, it's a sad day for slashdot when a post like yours gets modded -1 troll and the parent is +5 insightful. Almost makes me feel like creating a user name and doing some serious karmawhoring, but what kind of crap would a person have to spew to earn mod points from this bunch?

  80. wget -e http://gspy.com http://gspy.com/app.zip by DrSkwid · · Score: 2

    many popular leech scripts allow you to set the referer for when you want to leech those cool apps.

    If it wasn't for referer the revenue streams of many Internet companies would disappear. And not just annoying stuff like ads and pop-ups.

    Knowledge of traffic patterns and their journey is an important part of knowing how to promote your site. You can work with your cross linked sites to best position those links. For us the referer field is just as important as our hit counts, if not more so.

    --
    There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    1. Re:wget -e http://gspy.com http://gspy.com/app.zip by Anonymous Coward · · Score: 0

      > Knowledge of traffic patterns and their journey is an important part of knowing how to promote your site.

      Good for you. I'm glad you get all that really great data from me. Now, what about me and my concerns that where I've been is none of your damned business.

  81. nop, we need the search terms by DrSkwid · · Score: 2

    Not just the refering host.

    I have, and never will have, any intention of mapping search terms to users but which search terms drive traffic to our site is a vital piece of information for us.

    On a serious site search engine positioning is a daily job. Spending $50 on some shareware search engine submission program and running it they day you finish your web site just isn't enough.

    The data we get from our refering page information is what helps us keep a top ten google psotion for our chosen key words.

    I would guess that 90% of web design houses know next to nothing about web positioning. [which is great news for us :]

    --
    There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
  82. Bottom line - disable stupidity in your browser by Anonymous Coward · · Score: 0

    I wish Java, Javascript, Plugins, etc, etc had never been invented.

    How many real uses of Java and Javascript are there? Remember the first few years of it - just about every home page had a hello world program on it. WOW! I'm really excited. It only took about an hour to download over my 28.8K modem, which was almost brand new at the time.

    Anything remotely useful you can do in Javascript, I can do *better*, on the server, using PHP or Perl. Before you ask, I don't have to time to prove that, so please don't post URLs saying, "I bet you can't do that in PHP, it *has* to be done client side".

    As for plugins, read this:

    I DO NOT INSTALL PRE-COMPILED BINARIES FROM AN UNTRUSTED SOURCE ON ANY OF MY MACHINES.

    An untrusted source means:

    source != distribution CD

    If you want me to use your plug in, GPL it, and give me the source. Then I will consider it. Until then, NO WAY.

    So, if I visit a page that needs flash, and calls me an idiot for not downloading it already, I click back. End of story.

    I browse without Javascript, Java and without Plugins. I don't visit sites that need them. Tell me what I'm missing out on.

    Here's a good example - Slashdot is perfectly usable without:

    Java
    Javascript
    Any plugins
    Cookies

    It even works fine in Lynx.

    OK, you can't log in without cookies, but that could be implemented in other ways.

  83. Disable referrer by Anders · · Score: 2

    Opera lets you turn off the referrer entirely. I always use that, for privacy reasons. Besides, it lets me use the Bugzilla links that people say are designed to be unaccessible from Slashdot :-).

    What good is the referrer supposed to do, anyway? I always found it disturbing to be able to see in my logs which IMAP folders people use with their webmail.

  84. Solution for NTLM Authorization Proxy Server by bugbuilder · · Score: 1

    Some users need to use NTLM Authorization Proxy Server because their admins don't allow any client except IE.

    Just add the two last lines at the beginning of client_header_fix function in client.py :

    def client_header_fix(self):
    ""
    self.logger.log('*** Trying to fix client header...')
    # Remove referer
    self.client_head_obj.del_param('referer')

  85. OT: page width by Anonymous Coward · · Score: 0

    The real fix would be to have an option in the browser to wrap long text lines.

    There are many hundreds of sites, mostly mail archives, that this would make readable. Expecting all of them to fix their code is nice, but it's unlikely to happen.

  86. Depends on the OS he's using by Anonymous Coward · · Score: 0

    unmount is used by Syllable As it also uses bash and GNU toolsets, his .sig is perfectly valid.

  87. Re:I use Netscape 3.0.1 ONLY (check my referral) S by Anonymous Coward · · Score: 0

    Bollocks to that. I telnet to port 80 and read the raw HTML with more! Who needs all these fancy hypertext things anyway?

  88. Mozilla can already disable the bug by jlv · · Score: 2
    Unlike the original (and usual) JavaScript sins (bugs) of accidentally or unintentially exposing too much information, this is an actual bug wherein the internal form the referrer is stored in is getting corrupted. As I've been there before (http://www.schooner.com/~loverso/javascript/) - this is very similar to the flaw that allowed a script to upload files from you in Netscape 2.0.

    The nice thing is that Mozilla has a workaround, one that basically kills of a whole potential series of exploits.
    user_pref("capability.policy.default.Window.onunlo ad", "noAccess");
  89. Workaround less draconian than disabling onUnload? by Jobe_br · · Score: 1

    Another workaround for this bug exists that for some may be less draconian than disabling the onUnload Javascript handler. This *should* have the same effect as using a proxy that strips REFERER headers from your requests:

    user_pref("network.http.sendRefererHeader", 0);

    Placed in your prefs.js (or whichever .js file you want to store it in.

    Cheers.

  90. Question: how many servers exploit THE BUG by flamelord · · Score: 1
    Question: how many servers exploit the bug to collect the information on the user's next site?? And which organization have been exploiting this bug for months??? For example, does Slashdot collect info on the site I point to after visiting /. ?? It would be interesting to find out.

    It seems there is a huge effort to invade privacy recently, and I wonder what purpose this effort serves?

  91. HTTP_REFERER is a GOOD THING by mcrbids · · Score: 2

    When you click on a broken link and get an "oops!" page, remember that HTTP_REFERER tells the site where you came from, so that the broken link can be fixed.

    It's standard on many of my sites to do this - it's a very good thing IMHO - improving customer experience is good, and we certainly don't CARE who you are!

    --
    I have no problem with your religion until you decide it's reason to deprive others of the truth.
    1. Re:HTTP_REFERER is a GOOD THING by Otto · · Score: 2

      If your webmaster doesn't regularly look at your own site and knows those links are broken, then you need a new webmaster.

      I block referrer entirely for a couple of reasons:

      1. I don't care for sites to give me different content based on where that content is linked from. That's the most common use for referrer and it's a jerky thing for a website to do.

      2. I see this all the time: Online forums, people linking images from outside websites, perhaps even their own, and then endless complaints about about the red X or broken image icon or a "tripod" icon or some such. I never see those problems, instead I see the actual image they meant to link to.

      And so it's handy to do. And for all you onUnload() chaps, I disabled that too. If a web application *requires* onUnload(), then that web application is written poorly. If it just adds functionality, then fine. But 99.999% of the use of onUnload() is annoying ad popups and thus is always disabled.

      --
      - Give a man a fire and he's warm for a day, but set him on fire and he's warm for the rest of his life.
    2. Re:HTTP_REFERER is a GOOD THING by bleeeeck · · Score: 2
      If your webmaster doesn't regularly look at your own site and knows those links are broken, then you need a new webmaster.
      Yea, maybe on your "I Love My Cat" web site.

      A couple of my web sites have ~50,000 pages each. They are database driven and pages are added and deleted each week when the database is updated. Without the Referer: header, I'm unable to notify a site that a page that was there a month ago no longer exists

    3. Re:HTTP_REFERER is a GOOD THING by Otto · · Score: 2

      Sure you can. You can put a redirection up that says to any incoming vistors getting 401's, "hey, this page has moved" or you can just force the redirect upon them with a Location: header. What's so hard about that?

      If your site changes structure so often that deep linking to it is inappropriate because of shifting pages, then you should disallow such deep linking in the first place by redirecting such direct links to the home page or by providing a means to redirect deep links to the moved page.

      Or if it's database driven and pages are generated by an app based on the inputs in the URL, then what's the big deal? You're not shifting structure, are you changing all your page indexing schemes once a month? If old pages disappear, then where is the data that used to be on them? What exactly is disappearing? Is the info moving anywhere? Is there an appropriate place to link them to? Why not write your app such that if it has no data it redirects them to where the data is, likely is, or maybe even does a search for the user?

      --
      - Give a man a fire and he's warm for a day, but set him on fire and he's warm for the rest of his life.
  92. Re:this is redundant -- by Shrique · · Score: 1

    Gaping even, huge even. At the moment it doesn't really matter. mozilla has such a small % of hte whole thing even if someone did actually try to exploit it they wouldn't get enough information to really use it.

    Ah who the hell cares.

  93. Re:Here's a solution: by Anonymous Coward · · Score: 0

    I repeat your own post back to you.

  94. here's the path for Mac OS X. by jerkyjunkmail · · Score: 1

    here's the path for Mac OS X.

    $HOME/Library/Mozilla/Profiles/default/.slt

    --

    --
    What is pirate software? Software for inventory of stolen treasure?
  95. Privoxy by fm6 · · Score: 2

    Well, Privoxy looks like it'd be a lot of work to configure. On the other hand, it's got good pretty good docs, and working with it will probably teach you a lot about how http works in the real world. Which is actually the main reason I just downloaded it.

  96. i'm sorry - i'm demoting this bug to "minor" by erikdotla · · Score: 1

    Hover your mouse over links such as those at fark.com. You'll notice they run them all through a GO script to track where you go, then forward you there. It's almost invisible, it is invisible to new users. If a webadmin wants to track this, this is the best way - not to rely on a transient browser anomaly. "Anomaly" is a better term for this.

    The above could be obfuscated further by altering the status bar text to the "destination" link rather than the actual, tracker-link.

    I do not consider this a security flaw since web admins have the ability to track where you're going WITHOUT this anomaly using server-side.

    There are several other ways: Remember that the link is on the page that they control. An OnClick event that runs a function that talks to a server CGI to log which link you clicked, your IP, date time, is easily done.

    Some might think the resources used for such an implementation are more intensive: They need to run you through a CGI. But a CGI needs to read your cookie, and also relies on you coming back (what if you don't? The data is lost.) Anyone exploiting this isn't thinking through their implementation, and their solution will not work for most browsers, and will soon quit working altogether.

    Another argument: The difference with server side tracking is that, when you return, they don't know "who" clicked "which" link. Also false. I can cookie you with a unique identifier, and log your linkhit against that cookie ID, and when you return, tell you which link you clicked.

    Let's summarize: If this bug is fixed, but you leave cookies, status-bar-text-changing, and javascript on, I can do the same thing. If anyone doesn't believe me, you don't know much about scripting and I am willing to make a page proving this - you're welcome to come and test it with your "patched" Mozilla browser.

    So this is a security threat, how? Creating the user.js file is as simple as turning off cookies, or editing the various other script settings to combat the deceptive tactics used by webadmins to track you.

    If I was on the BugZilla team I'd be demoting this defect to "anomaly, minor" or whatever lowest possible rating it has.

    Erik.LA

    --
    # Erik
    1. Re:i'm sorry - i'm demoting this bug to "minor" by erikdotla · · Score: 1

      I would like to retract my post after discovering that this exploit includes the ability to see what's in the location bar, which is a more serious bug. I read several pages about it before seeing that part of it.

      --
      # Erik
  97. Not a bug! by SJS · · Score: 1

    Sheesh.

    This isn't a bug. If you have Javascript enabled, you should expect to have little to no privacy anyway. (Just as you should expect popups, popunders, porn-adverts, memory leaks, and system crashes.)

    I mean, what's the recommended solution?

    In the meantime, Neuhaus said the vulnerability can be worked around by switching off Javascript.
    That's right. Do what the security-minded folks have been saying for years. Disable Javascript. Don't use it. Don't visit sites that require it.

    And if you don't, well, don't whine about it.

    --
    Pick One: http://www-rohan.sdsu.edu/~stremler/sigs/sigs.html (Note - disable Javascript first!)
  98. Slashdot is hopelessly hypocritic by thinktank2 · · Score: 0

    The people here shout as if the world is moving to hell, when a microsoft security hole news breaks up. But the same people pass of lame excuses and make security holes in OSS a non-issue. This is hopelessly hypocritic. Open Source software can only grow better when their users demand carefulness on the developers part, Not by fanatically supporting an OSS product unacknowledging its security weak points. Shame on you people!

  99. no big surprise by jdkane · · Score: 1

    So why should I care if a website knows I leave it and go to SlashDot. Doesn't everybody?

  100. Mozilla http referer by Anonymous Coward · · Score: 0

    Ben Bucksch in Bugzilla posted to add the following to your user.js: pref("network.sendRefererHeader", 2); // 0=don't send any, 1=send only on clicks, 2=send on image requests as well

  101. Legitimate Popups by fm6 · · Score: 2
    Your post points up the fact that not all popups represent attempts to spam your desktop. On the other hand, most "legitimate" popups are just lazy web design, as this page demonstrates.

    Be that as it may, there are times when I need to allow popups in order to get full use out of a site. What's needed is a simple popup policy engine, something like the cookies privacy engine in IE. In particular, I'd like to impose a global limit on popup frequency, so a site can't force me to accept all their crap just to get single popup window that I want to see. The simplistic "no popups" option in Mozilla is not useful for most of us.

  102. Last post! by Anonymous Coward · · Score: 0

    This post is off-topic. And the moderators will never know.