Forum Moderators: open
Enter this your browser:
http://www.msn.com@www.yahoo.com
similar though:
enter this in our browser:
http://www.[YOUR_COMPETITOR_SITE].com@www.[YOUR_SITE].com(replace the brackets and the text) and guess what you'll get, your competitor's domain in the address bar with your content!
similar similar though:
enter this in your browser:
http://www.[YOUR_COMPETITOR_SITE].com@www.[SOME_CRAPPY_SITE_FROM_YOUR_SITE'S_/_YOUR_COMPETITORS_SITES_TOPIC].com(again replace the text and the brackets) and guess what you'll get? a crappy site on your competitors domain!
I could go on this forever...
;)
Sid
<script type="text/javascript"> document.write(unescape('http://www.google.com%01@www.yahoo.com')); </script> There are a ton of articles covering this.
[edited by: encyclo at 10:13 pm (utc) on Dec. 15, 2003]
B. Not so sure why all of those examples are funny -? Funny in that it's a joke, or is pulling something over one someone? Weird, maybe. Maybe funny if you place such a link on your site and people believe they are going to a competing site but get a crap site instead? Some will see through it, others will think "gee, his link is not working right" and they will assume you've messed up. I would....
C. I suspect it's not so much a bug as the side effect of a feature - the ability to go to protected sites, or FTP addresses using a string with your name and password piped in. In other words, I can access a protected site simply by typing in the string with the address, my user ID and my password. This seems to be similar.......
Shadows Papa
This is all also another reason to NOT use IE. Firebird showed the entire link string, with Yahoo's fav icon. IE is the most unsecure browser ever created. That's because they try to be all things to all people.
Shadows Papa
ftp://username:password@domain.name/path/to/directory
The "bug" seems to be a typical M$ attempt to 'stupify' the interface by hiding the username:password details from the user.
There's an open source patch for this: http*//security.openwares.org/
AAArrrggghh! This "patch" has been called a trojan elsewhere, and apparently includes at least one buffer overrun itself. Here's a hint - never apply "fixes" from untrusted sources. IE needs to be fixed by Microsoft, not by some unknown company with an unknown agenda.
Actually it's not a trojan. It phones home only the urls which are of this syntax, so for general surfing there is no data sent.
I think my point still stands - the fact that users are happy to install any old patch or program from any old source is why spyware, scumware, viruses and trojans are so widespread. How much expertise does this company have in how IE works, seeing that IE is a firmly closed-source product? How can they be sure that it won't break other programs? Even if they are acting in pure good faith, they are very unlikely to have the capacity to produce a good patch. IE can only be patched by Microsoft because only Microsoft has the source code. As for the "phoning home", I would consider that to be underhand - perhaps not a trojan, but certainly scumware or adware.
If you want a decent, fully verified, quality patch for this bug, try one [mozilla.org] of [opera.com] these [mozilla.org].
encyclo, I'm already using Opera and Firebird as my main browsers. I offered the address because I thought that it would interest the folks around here, most of whom I believe have enough experience to make an informed decision to use it or not.
It's got a buffer overflow vunerability, memory leak problems, and a "liveupdate" backdoor that people didn't notice at first. Not a good thing and I hate how this only encourages long delays by Microsoft.
Anything other than a genuine patch by the real supplier of original software should ever be applied. And only after much testing!
(and such a patch isn't needed if folks don't blindly click links in email or pages they can't trust 100%)
Shadows Papa
(former IT Analyst/computer anti-virus and security manager)
It's not a bug!
The @ in the url tells the browser (ANY browser) that you're trying to access a site that requires a username:password combination.
Once access has been granted, IE will no longer display the username:password as part of the url. This is in intentional feature that was added for the same reason that a password field displays *s instead of the real password.
It's not a bug!The @ in the url tells the browser (ANY browser) that you're trying to access a site that requires a username:password combination.
You simply don't understand the bug. Sure, the @ in URLs is used for specifying user names and passwords (although no, it doesn't work in all browsers).
The bug is that if you include a null character "%00" in a URL, then everything after the null character will be hidden away and never shown to the user.
So this:
[microsoft.com%00@www.kernel.org ]
Will open up kernel.org but only display "http://www.microsoft.com" in the address bar for IE.
So this:
[microsoft.com%00@www.kernel.org...]Will open up kernel.org but only display "http://www.microsoft.com" in the address bar for IE.
Opening [microsoft.com...]
(3 items remaining) Downloading picture [microsoft.com<...]The URL and the content/page that appears is kernel.org.
Its not a bug!
Then what is it? Is it a feature in *all* browsers, especially made for Spamming?
I do agree, this does work in every browser (I tried it in Opera, Netscape, Mozlla and IE). Lets just wait for MS to release a patch, but wait, this bug is getting applied in every browser! Who should we trust?Sid
[kernel.org...]
As expected. I get it in the address bar and I get kernel.org's content. I'm using IE6 SP1, the most commonly used version of IE. I haven't downloaded a patch or update in at least a month.