--- npguy <[EMAIL PROTECTED]> wrote: > This comes when extracting module doesn't verify the > intgerity of headers. The > similar types of breaches were found in WinRAR. The > quick > approach to resolve is to verify the actual physical > size of the compressed > file against the headers info. WinRAR now takes > similar approach.
Yap, my winrar advisory dates back to, Sep 9 2003, http://www.securityfocus.com/bid/8572/discussion/ http://www.geocities.com/visitbipin It has been 9 months, still... the AV companies that call itself the worlds best [Macfee, symantec...etc] seem to have problem coding the program logics. Is it like, NAV isn't immune from this bug so BUGTRAQ guys are having hegitation posting this agvisory? ------------[snip]----------------- * Winxp default zip manager just report the 12Gb zip file to be 121 Mb!??? * Winrar [3.20] can show the size of .bz2 files and winrar just report bipin.zip is 128 Mb but it start filling up the hdd. to 12 Gb if you try to extract the file. *If we try to extract the 12 Gb [Standalone] file in Fat32 tries to extract the 12 Gb file and terminate extraction after 4Gb [fat32 limit] I wounder, why in the 1'st place would Winrar allow to extract a 4+ Gb [single] file in Fat 32. -------------[snip]----------------- bipin gautam __________________________________ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo.com/ _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.netsys.com/full-disclosure-charter.html
