| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <40752FDD.4000101@cc.kuleuven.ac.be> From: Rik.Bobbaers at cc.kuleuven.ac.be (harry) Subject: FAT32 input > output = null? 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@...kuleuven.ac.be -=- http://harry.ulyssis.org -- Air conditioned environment - do not open windows!
Powered by blists - more mailing lists