Re: [Full-Disclosure] FAT32 input > output = null?
From: Nico Golde (nion_at_gmx.net)
Date: 04/09/04
- Previous message: Bugtraq Security Systems: "[Full-Disclosure] ron1n phone home, episode 6"
- In reply to: chris: "Re: [Full-Disclosure] FAT32 input > output = null?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
To: full-disclosure@lists.netsys.com Date: Fri, 9 Apr 2004 14:12:18 +0200
Hallo chris,
* chris <chris@defcon.org> [2004-04-09 13:38]:
> >i don't understand your problem.
> >i tried:
> >[nico@golde:~] $ ls -al test
> >-rw-r--r-- 1 nico users 6 2004-04-08 11:46 test
> >[nico@golde:~] $ test>test
> >[nico@golde:~] $ ls -al test
> >-rw-r--r-- 1 nico users 0 2004-04-08 11:47 test
> >
> >but it is not wondering because you put the output of the first command
> >in the file after the >. because you have not a real command and you
> >have no real output you overwrite the file with an empty output stream
> >and the file is 0 byte after it.
> >haven't i understand your problem correctly?
> >regards nico
>
> I don't really have a problem. The original poster tried this on a FAT32
> system and asked if it was normal behavior. Another poster confirmed that
> this was the case with NTFS and I was merely doing the same for ext3.
ok sorry, i misunderstood.
regards nico
-- Nico Golde | nico@ngolde.de | 310777820@ICQ | nion@gmx.net http://www.ngolde.de | GnuPG Key: http://www.ngolde.de/gpg/nico_golde.gpg Fingerprint | FF46 E565 5CC1 E2E5 3F69 C739 1D87 E549 7364 7CFF vim -c ":%s/^/WhfgTNabgureRIvzSUnpxreT-Tavba/|:%s/[R-T]/ /Ig|:normal ggVGg?"
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html
- application/pgp-signature attachment: stored
- Previous message: Bugtraq Security Systems: "[Full-Disclosure] ron1n phone home, episode 6"
- In reply to: chris: "Re: [Full-Disclosure] FAT32 input > output = null?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]