Re: [Full-Disclosure] FAT32 input > output = null?

2004-04-09 Thread Nico Golde
Hallo chris, * chris <[EMAIL PROTECTED]> [2004-04-09 13:38]: > >i don't understand your problem. > >i tried: > >[EMAIL PROTECTED]:~] $ ls -al test > >-rw-r--r--1 nico users 6 2004-04-08 11:46 test > >[EMAIL PROTECTED]:~] $ test>test > >[EMAIL PROTECTED]:~] $ ls -al test > >-rw-r-

Re: [Full-Disclosure] FAT32 input > output = null?

2004-04-08 Thread Harlan Carvey
Somehow I get the feeling that this would be a much better world if the "touch morning_wood" command were executed more often... Geez, this has really gotten into the gutter... --- morning_wood <[EMAIL PROTECTED]> wrote: > >executing this at the dos promt would create a > zero byte m.wood file >

Re: [Full-Disclosure] FAT32 input > output = null?

2004-04-08 Thread morning_wood
>executing this at the dos promt would create a zero byte m.wood file >> m.wood >looks like a feature equivalent to touch m.wood or touch filename LMFAO m.wood Delivered using the Free Personal Edition of Mailtraq (www

RE: [Full-Disclosure] FAT32 input > output = null?

2004-04-08 Thread Aditya, ALD [Aditya Lalit Deshmukh]
executing this at the dos promt would create a zero byte m.wood file > m.wood looks like a feature equivalent to touch m.wood or touch filename -aditya Delivered using the Free Personal Edition of Mailtraq (www.mai

Re: [Full-Disclosure] FAT32 input > output = null?

2004-04-08 Thread madsaxon
At 10:56 AM 4/8/2004 -0500, jamie wrote: Big, long, slow moving line.. and this Certain Ethnic woman was on her cell phone.. talking at the top of her vocal volume, like she was on a tin can and string about 100 miles long, really annoying everyone in line. This lady in front of me finally pipe

Re: [Full-Disclosure] FAT32 input > output = null?

2004-04-08 Thread jamie
I read m.wood's post, and had to go read the OP. This is a serious vulnerability. The type as referenced Microsoft #id-10T et al, Pebkac edition. The other day, I was at the post office.. My postal person left a notice for me to pick up a package. Big, long, slow moving line.. and this Certain

Re: [Full-Disclosure] FAT32 input > output = null?

2004-04-08 Thread chris
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nico Golde wrote: >Hallo chris, > >i don't understand your problem. >i tried: >[EMAIL PROTECTED]:~] $ ls -al test >-rw-r--r--1 nico users 6 2004-04-08 11:46 test >[EMAIL PROTECTED]:~] $ test>test >[EMAIL PROTECTED]:~] $ ls -al test

Re: [Full-Disclosure] FAT32 input > output = null?

2004-04-08 Thread Nico Golde
Hallo chris, * chris <[EMAIL PROTECTED]> [2004-04-08 11:20]: > This also works with the 2.4.24 Linux kernel (Slackware 9.1): > > [EMAIL PROTECTED]:~$ more testfile.txt > Let's try this in Linux > [EMAIL PROTECTED]:~$ ls -al testfile.txt > - -rw-r--r--1 chrisusers 24 Apr 7 12:43

Re: [Full-Disclosure] FAT32 input > output = null?

2004-04-08 Thread harry
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 comma

Re: [Full-Disclosure] FAT32 input > output = null?

2004-04-08 Thread Frederic Pasteleurs
> C:>del.exe >del.exe Under Dos/Windoze, there is no file named del.exe: this command is built into the command interpreter (command.com/cmd.exe) All this line will do is creating an empty file named del.exe. Furthermore, in order to invoke this particular file, you will have to type it's full nam

Re: [Full-Disclosure] FAT32 input > output = null?

2004-04-07 Thread J.A. Terranson
On Wed, 7 Apr 2004, morning_wood wrote: > 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, execu

Re: [Full-Disclosure] FAT32 input > output = null?

2004-04-07 Thread morning_wood
> 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 fro

Re: [Full-Disclosure] FAT32 input > output = null?

2004-04-07 Thread morning_wood
> [EMAIL PROTECTED]:~$ more testfile.txt > Let's try this in Linux > [EMAIL PROTECTED]:~$ ls -al testfile.txt > - -rw-r--r--1 chrisusers 24 Apr 7 12:43 testfile.txt > [EMAIL PROTECTED]:~$ testfile.txt>testfile.txt > - -bash: ./testfile.txt: Permission denied > [EMAIL PROTECTED]:~$

Re: [Full-Disclosure] FAT32 input > output = null?

2004-04-07 Thread Chris Palmer
chris writes: > This also works with the 2.4.24 Linux kernel (Slackware 9.1): It's the shell, not the kernel. When you say "./foo > ./foo", the shell interprets "> ./foo" FIRST and does something like open("foo", O_TRUNC | O_CREAT). Take a look at any Unix shell document and the open(2) man pag

Re: [Full-Disclosure] FAT32 input > output = null?

2004-04-07 Thread Hugh Mann
This also works with the 2.4.24 Linux kernel (Slackware 9.1): 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 and it deleted the file. I can't believe my eyes. _

Re: [Full-Disclosure] FAT32 input > output = null?

2004-04-07 Thread chris
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This also works with the 2.4.24 Linux kernel (Slackware 9.1): [EMAIL PROTECTED]:~$ more testfile.txt Let's try this in Linux [EMAIL PROTECTED]:~$ ls -al testfile.txt - -rw-r--r--1 chrisusers 24 Apr 7 12:43 testfile.txt [EMAIL PROTECT

Re: [Full-Disclosure] FAT32 input > output = null?

2004-04-07 Thread bipin gautam
YAP, works for ntfs too... -- --- morning_wood <[EMAIL PROTECTED]> wrote: > Fat32 file output redirect overwrites self. > === > > odd behavior... >? > > 1.) console application output redirected to itself > ( file.ext > file.ext ) > C:\

[Full-Disclosure] FAT32 input > output = null?

2004-04-06 Thread morning_wood
Fat32 file output redirect overwrites self. === odd behavior... >? 1.) console application output redirected to itself ( file.ext > file.ext ) C:\test>program.exe >program.exe program.exe The process cannot access the file because it is being used by another process. ok