[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <021b01c48496$c3b730a0$a900a8c0@cybergeneration.com>
From: mducharme at cybergeneration.com (Maxime Ducharme)
Subject: cmd.exe bug in win2k sp4 in "for" loop ... erratum
Hi again
made a mistake in my explanation, part
" When you redirect a program's output, you may
specifiy which output you want (stdin or stderr)."
should read
" When you redirect a program's output, you may
specifiy which output you want (STDOUT or stderr)."
stdin is used for inputs, i.e. file reads & keyboard
strokes.
Have nice day
Maxime Ducharme
Programmeur / Sp?cialiste en s?curit? r?seau
----- Original Message -----
From: "Maxime Ducharme" <mducharme@...ergeneration.com>
To: <ald2003@...rs.sourceforge.net>; "Full-Disclosure@...ts. Netsys. Com"
<full-disclosure@...ts.netsys.com>
Sent: Tuesday, August 17, 2004 10:54 AM
Subject: Re: [Full-Disclosure] cmd.exe bug in win2k sp4 in "for" loop
>
> Hi Aditya,
> this is not a bug, but normal operation of
> msdos command interpreter.
>
> There is a concept of different outputs for
> normal output and errors.
>
> They are called "stdout" and "stderr".
>
> stdout = 1
> stderr = 2
>
> When you redirect a program's output, you may
> specifiy which output you want (stdin or stderr).
>
> By default stdout is used, so a "1" is added before
> the redirections ">" or ">>".
>
> If you want to catch errors, you need to specify
> stderr output like this :
>
> echo "ello" 2>>stderr.log
>
> You may also catch each of them like this :
>
> echo "ello" 1>>stdout.log 2>>stderr.log
>
> You may find more details here :
> www.microsoft.com/windowsxp/home/using/productdoc/en/redirection.asp
>
> This is XP details, but I think it is the same behavior on NT, 2K and
2003.
>
> Have a nice day
>
> Maxime Ducharme
> Programmeur / Sp?cialiste en s?curit? r?seau
>
> ----- Original Message -----
> From: Aditya, ALD [Aditya Lalit Deshmukh]
> To: Full-Disclosure@...ts. Netsys. Com
> Sent: Tuesday, August 17, 2004 1:31 AM
> Subject: [Full-Disclosure] cmd.exe bug in win2k sp4 in "for" loop
>
>
> On windows 2000 SP4 the command processor cmd.exe has a small bug in the
for
> loop see the attached image, this is making all the bat file go crazy with
> the output see the selected potions....
>
> is this a known bug, with a patch ? can it be reproduced on other
NT/2k/XP/3
> versions of windows ?
>
> -aditya
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.netsys.com/full-disclosure-charter.html
>
Powered by blists - more mailing lists