Bring Down Internet Explorer In Six Words 239
Marcion writes "Some handy Japanese guy called Hamachiya discovered a bug in Internet Explorer. Under certain conditions, an asterisk when used as a wildcard can crash IE as soon as the user attempts to go to another page." The article claims the "five HTML tags and a CSS declaration" crash IE7 as well as IE6, but I couldn't get IE7 to fail. This page says that as of June, IE6 was at about 37% market share and IE7 under 20%.
Hmm.. (Score:4, Informative)
I know it's real subtle... (Score:3, Informative)
Re:If you don't speak Japanese.... (Score:5, Informative)
Ask and ye shall receive
A bit anti-climactic really.
Re:html source is: (Score:3, Informative)
Re:Bring Down A Website In Six Words (Score:3, Informative)
http://www.networkmirror.com/tQxFeWtOc31fVZfD/com
IE Usage @ w3schools? (Score:5, Informative)
Yeah, but don't you think w3schools would be a bit biased? W3schools is a site full of tutorials and information for developers. Developers tend to prefer FireFox due to its robust plugin system and some of the excellent plugins for that system (Firebug, Web Tools, etc.) so I'm not surprised that FireFox has a higher rate of use on such a site. In fact, I am surprised that it's not higher!
Re:Is it crashed or not? (Score:5, Informative)
An exception was thrown that was not properly caught. The error is caused by improper error trapping. Otherwise, the browser would just render things improperly or claim there was an error on the page because it doesn't properly parse and render the style tag.
Funny, but not "Engrish" (Score:3, Informative)
However, it's misleading to call these "Engrish", as that normally refers to the use of bad English (or even pseudo-English) by the Japanese.
By contrast, this is a quaint auto-translation of correctly-written Japanese. Okay, so the "cute" tone is probably down to the differences between Japanese language and culture as well... but it's still not Engrish per se.
So? One can easily crash Firefox too... (Score:4, Informative)
I suspect all of the Mozilla based browsers will effectively die if one throws enough "heavyweight" pages at them (i.e. those which are activity heavy [because there isn't a Javascript/Active HTML/Animated GIF scheduler]) or run out of swap space (again because memory allocation failures are not handled gracefully).
IMO, developers place too much emphasis on feature enhancements rather than making the existing browsers run reliably (bugs shouldn't linger for 3 years), with a minimal machine footprint (Netscape 4.7x required significantly less memory than Firefox) and effective priority scheduling of the "top" window (user responsiveness).
Also crashes Outlook... (Score:4, Informative)
Re:Is it crashed or not? (Score:5, Informative)
When an exception is thrown and is not properly caught. The error is caused by improper error trapping. This is a classic "crash."
Re:Bring down my system in 13 chars. (Score:1, Informative)
Re:Bring down my system in 13 chars. (Score:2, Informative)
Just replace ":" with some word, it will be easier to understand:
kill(){kill|kill&};kill
Re:IE Usage @ w3schools? (Score:3, Informative)
Still, this is a huge shift from the 96% share IE had a few years back. The fact that some sites get 30% Firefox usage (actually I run a small site that gets 46% Firefox) means that web developers can no longer ignore coding to standards. This is a good thing.
Re:If you don't speak Japanese.... (Score:4, Informative)
Hello! Good afternoon!!!!!
I stumbled across a browser crash, so today I'll tell you about it!
Here it is!
<style>*{position:relative}</style><table><input>
Sample (If you're using IE, your browser will close! You have been warned!)
It seems IE6 or programs using IE6 components will definitely crash!
I haven't checked IE7 though!
It seems to be when you have and input or select or such just below a table or tr or such,
and you use the css wildcard * to set everything to position:relative.
By the way, if the input has its style directly set to relative, it doesn't crash. What's up with that?
I don't really get it, but it sure is interesting...!
Anyone out there who loves Firefox or Opera should go spread this all over and decrease IE's market share!!!
Re:Tear in my eye (Score:3, Informative)
This had nothing to do with FOSS, and everything to do with Apple reclaiming a large chunk of its niche who had moved to Windows (as a group, that is; many of the old school Mac users probably didn't migrate, but new users coming into the traditional Mac niches weren't flocking to Mac fast enough to maintain market share) in the absence of anything from Apple that could inspire them to pay the premium.
This was totally unrelated to Linux/FOSS.
Re:Bring down my system in 13 chars. (Score:3, Informative)
Re:Is it crashed or not? (Score:3, Informative)
What you just described is an application or process hanging. The app cannot respond to any user inputs or messages from the OS and the app or even the entire system in the worst case becomes unresponsive.
When an app or process crashes it is no longer running and under a better-designed OS will have its memory cleaned up in garbage collection.
(Developing since 1979)
Re:No. You're kidding. Can't be. (Score:4, Informative)
Umm... 9 days ago?
http://secunia.com/advisories/26201/ [secunia.com]
The vulnerability is caused due to an input validation error within the handling of system default URIs with registered URI handlers (e.g. "mailto", "news", "nntp", "snews", "telnet"). This can be exploited to execute arbitrary commands when a user e.g. using Firefox visits a malicious website with a specially crafted "mailto" URI containing a "%" character and ends in a certain extension (e.g. ".bat", ".cmd")
This command would make firefox go "away"
mailto:test%25../../../../windows/system32/tskill
Re:Tear in my eye (Score:3, Informative)