[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bad binaries
- Subject: Re: Bad binaries
- From: taob@r-node.io.org (Brian Tao)
- Date: 17 Oct 1993 23:43:10 -0400
- In-reply-to: behrenss@Informatik.TU-Muenchen.DE (Soenke Behrens)
- Newsgroups: comp.sys.apple2
- Organization: Terran Exobiology Research Institute, 1-800-GO-ALIEN
- References: <behrenss.750706993@hphalle6>
- Reply-to: taob@io.org (Brian Tao)
In article <behrenss.750706993@hphalle6>, Soenke Behrens writes...
>
> nulib, just like GSHK, doesn't do much on "integrity check". To see if
> an archive is really OK, you have to unpack it (which is what all the
> other packers out there actually do if you ask them to check an
> archive).
Hmmm... I figured Nulib would do something similar to Yankit: unpack
the archive "to memory" and report any errors. What good is the CRC
integrity check if you can't compare it to the original values?
--
Brian Tao:: taob@io.org (Internex Online, 416-363-3783, 17 lines, v.32bis)
::::::::::: 90taobri@wave.scar.utoronto.ca (University of Toronto, 9T4)