It didn't help. I edited the program (Open Source is awesome!) to count the
\r's and the \n's, there were 10679 missing bytes. I counted 10755 newline
characters. I replaced the first 10679 newlines with \r\n, but it still
couldn't find the directory... "start of central directory not found"
If the error took place during FTP, then it should be correctable, right?
Any ideas on what other characters are affected by ASCII FTP transfer?
Thanks,
Eric
On Mon, Aug 30, 2010 at 7:19 PM, Jason Holtzapple <
ml@bitflip.net> wrote:
> On 08/30/2010 06:51 PM, Eric Cope wrote:
> > I transferred a zip file off of an infected Windows machine via FTP.
> > That file was determined to be corrupt (after I wiped the drive of
> > course). I suspect the corruption took place because I transferred the
> > file using ASCII mode, not binary mode. Is there anyway to "repair" a
> > zip file, like search and replacing the "\n" with a "\r\n" or some other
> > tool, Linux based or otherwise?
>
> The fixgz program does exactly that.
>
>
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
(text/plain)
