[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Full-Disclosure] FAT32 input > output = null?
- To: full-disclosure@xxxxxxxxxxxxxxxx
- Subject: Re: [Full-Disclosure] FAT32 input > output = null?
- From: harry <Rik.Bobbaers@xxxxxxxxxxxxxxxxx>
- Date: Thu, 08 Apr 2004 12:56:29 +0200
morning_wood wrote:
You can also delete files by using the "del" command. I tested this with the
5.1 ntos kernel (Slackware XP):
C:\>del testfile.exe
if you were trying to be sarcastic in saying this is
"normal, any dummy knows that" then you failed
horrendously, sir.
where did the delete command came from ????
this has nothing to do with any system command
it was simply an odd behavior where by ">" piping
output of a file into itself, causes a 0 byte or corrupted file
C:>del.exe >del.exe
in particular, executeable files.
he is right... del does delete the file...
and > is redirect, not pipe (|)
what you are doing is: (IF del.exe should exist off course)
execute del.exe and redirect the output to a file: del.exe
==> del.exe is loaded in memory, and then the output of del.exe
(nothing) is written into del.exe ==> del.exe is 0 bytes, and not the
executable anymore. it's content is overwritten...
i don't see anything weird??? do you???
--
harry
aka Rik Bobbaers
K.U.Leuven - LUDIT -=- Tel: +32 485 52 71 50
Rik.Bobbaers@xxxxxxxxxxxxxxxxx -=- http://harry.ulyssis.org
-- Air conditioned environment - do not open windows!
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html