It's interesting that you can do the same type of test with windows utilities as well as described in this Full Disclosure note.
Hi all,
Wanna do a quick test to see if the programmers that wrote your windows operating system have any clue as to what there doing ? Run these commands from cmd.exe in the system32 directory:
for %i in (*.exe) do start %i %n%n%n%n%n%n%n%n%n%n%n%n%n%n%n%n%n%n%n%n for %i in (*.exe) do start %i AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA.... (type as much "A"-s as cmd.exe allows on one line.)
Each command will execute every program in your system32 directory, most of them will either ignore the parameter or report an error because the parameter doesn't make sence... But on my win2k system I found 6 programs vulnerable to these very simple formatsting and BoF tests.... grpconv even gives EIP 0x00410041, can it be any easier?
These are not vulnerabilities in itself: you cannot gain access or elevate priviledges but I just wanted to let you know that these programmers did a sloppy job.
I also use suse 9.1 and managed to get gaim working from source on the first try. The only extra stuff that I had to install were the packages listed here: http://linux01.gwdg.de/~pbleser/rpm-navigation.php ?cat=Network%2Fgaim/ because of the lack of bundled ssl support when connecting to msn. Installed opencdk, gntls, libtasn1 with their devel rpms ,./configure && make && make install gaim again and worked like a charm.
Sure, I am simply able to find the relevant files faster. Not only is it faster (probably because it searches less files) but I'm able to quickly spot the file I want by looking at the text previews - something which Window's search tool does not have.
From the screenshots, I don't know but to me it looks like nothing special. The interface still is pretty ugly specially with that overdone brushed steel/plastic thing. Can't even read the options properly. I'll stick with Media Player Classic.
You got it exactly right. IE doesn't seem to get the box model correctly and does not count the padding/border as part of the element's width. Gecko does.
That is why sometimes you will see developers use silly ie work arounds like:
/*width for standard compliant agents*/ width: 100px !important;
/*IE workaround */ width: 90px;
..on the same style sheet
IE does not recognize the !important directive which tells the browser to ignore any styles for the same purpose and always use this one (in this case gecko ignores 90px and uses 100px. IE doesn't understand therefore uses 90px.
It's silly inconsistent things like this that make the existence of standards so important. Would make our developing and users' lives easier!
You got it exactly right. IE doesn't seem to get the box model correctly and does not count the padding/border as part of the element's width. Gecko does.
That is why sometimes you will see developers use silly ie work arounds like:
/*width for standard compliant agents*/ width: 100px !important;
/*IE workaround */ width: 90px;
..on the same style sheet
IE does not recognize the !important directive which tells the browser to ignore any styles for the same purpose and always use this one (in this case gecko ignores 90px and uses 100px. IE doesn't understand therefore uses 90px.
It's silly inconsistent things like this that make the existence of standards so important to make us developers and users life easier!
No it doesn't have any problems displaying open/close form tags. If IE is not displaying the extra new lines then it's actually doing it wrong. Form tags, as specified in the w3 standard are block-level elements.
Block-level elements are those elements of the document language that, by default, are formatted visually as blocks (e.g., paragraphs). Inline elements are those elements of the document language that do not cause paragraph breaks (e.g., pieces of text, inline images, etc.).
That is why you get the extra space around the element. This is the intended behavior of form elements. If you want to get rid of the space, as mentioned, use a style sheet of margin:0; or display: inline;
"The claims administrator will not issue checks for less than $1.00. Such amounts will instead be reallocated to those claimants who are entitled to receive distributions."
It doesn't really matter that they've raised the limit. I've always disliked yahoo, I'm not sure if it's its ads filled pages or what not but I just tried composing a test e-mail and got over 5 errors trying to get to the compose screen which I couldn't even get to. Error connecting to my.yahoo.com edit.yahoo.com f501.yahoo.com, etc etc etc . 100 mbs for all the hoops I have to jump through, is not worth it.
..I am afraid that this comparison might fall out to the advantage of Windows...and how do you know this exactly?
I'm sure there is a comparable (if not greater) amount of critical bugs in windows's kernel that because of its closed nature we don't ever get to see or MS sweeps under the carpet without the public ever knowing they exist until someday they're found.
Slashdot Mirror
Never mind, they already knew it was coming. The other portion will go towards the recovery efforts..
They will need another fund raising campaign to pay to resurrect their webserver and database from the ashes.
I also use suse 9.1 and managed to get gaim working from source on the first try. The only extra stuff that I had to install were the packages listed here: http://linux01.gwdg.de/~pbleser/rpm-navigation.php ?cat=Network%2Fgaim/ because of the lack of bundled ssl support when connecting to msn. Installed opencdk, gntls, libtasn1 with their devel rpms , ./configure && make && make install gaim again and worked like a charm.
Sure, I am simply able to find the relevant files faster. Not only is it faster (probably because it searches less files) but I'm able to quickly spot the file I want by looking at the text previews - something which Window's search tool does not have.
So far in my testing, it has performed better than MS's own indexing service which comes with Windows.
From the screenshots, I don't know but to me it looks like nothing special. The interface still is pretty ugly specially with that overdone brushed steel/plastic thing. Can't even read the options properly. I'll stick with Media Player Classic.
and will sue any /. posters that post mirrors to the source code.
Once again I read this article as I see a "Windows 2003 outperformed every Red Hat Linux configuration tested -- source: Veritest" ad. ..
Columbia University and MIT have decided to join organizations to now be known as UAC ......
What would really be interesting is if they find a soulcube!
.. then those aliens are obviously the Soviets ;)
That is why sometimes you will see developers use silly ie work arounds like:..on the same style sheet
IE does not recognize the !important directive which tells the browser to ignore any styles for the same purpose and always use this one (in this case gecko ignores 90px and uses 100px. IE doesn't understand therefore uses 90px.
It's silly inconsistent things like this that make the existence of standards so important. Would make our developing and users' lives easier!
That is why sometimes you will see developers use silly ie work arounds like:..on the same style sheet
IE does not recognize the !important directive which tells the browser to ignore any styles for the same purpose and always use this one (in this case gecko ignores 90px and uses 100px. IE doesn't understand therefore uses 90px.
It's silly inconsistent things like this that make the existence of standards so important to make us developers and users life easier!
No it doesn't have any problems displaying open/close form tags. If IE is not displaying the extra new lines then it's actually doing it wrong. Form tags, as specified in the w3 standard are block-level elements.
Block-level elements are those elements of the document language that, by default, are formatted visually as blocks (e.g., paragraphs). Inline elements are those elements of the document language that do not cause paragraph breaks (e.g., pieces of text, inline images, etc.).
That is why you get the extra space around the element. This is the intended behavior of form elements. If you want to get rid of the space, as mentioned, use a style sheet of margin:0; or display: inline;
This release along with the ssl certificate spoof reported here proof of concept here, does not make my favorite brower look good :(
Thats what I thought as well. But after testing the form and trying to enter a Canadian postal code (zip code), It says invalid Zip code.
We all know https/http needs a : and // after it! .. this is a scam i tell you!
"I'm so ready to receive my check for $0.35US"
..... ;)
Think again
"The claims administrator will not issue checks for less than $1.00. Such amounts will instead be reallocated to those claimants who are entitled to receive distributions."
It doesn't really matter that they've raised the limit. I've always disliked yahoo, I'm not sure if it's its ads filled pages or what not but I just tried composing a test e-mail and got over 5 errors trying to get to the compose screen which I couldn't even get to. Error connecting to my.yahoo.com edit.yahoo.com f501.yahoo.com, etc etc etc . 100 mbs for all the hoops I have to jump through, is not worth it.
I submitted this this morning, got rejected .. life is not fair! ;)
anyways, here are the videos, it does look pretty cool:
Video 1
Video 2
Sad but true, so frustratrating too :(
..I am afraid that this comparison might fall out to the advantage of Windows ...and how do you know this exactly?
I'm sure there is a comparable (if not greater) amount of critical bugs in windows's kernel that because of its closed nature we don't ever get to see or MS sweeps under the carpet without the public ever knowing they exist until someday they're found.
And for all that cost, Visual Studio still hasn't got half the functionality of emacs...
.. I'm sure you meant vi right? ;)
Hey Mr. McKusick, RTFA