Dustin Cook wrote:
> BugHunter uses a proprietary checksum algorithm that I developed over
> 14 years ago. In an effort to reduce scantime, BugHunter scans files
> ONLY if they have a known filelength; IE: Known to BugHunter as
> potentially being malicious. Once BugHunter takes a scan of the
> suspect file, it gets two 32bit numbers in a specific order. If the
> numbers match the record as well as the filelength in the correct
> order, BugHunter considers it a valid match and looks the information
> up to give it a more descriptive name, of course that depends on the
> record having a matching description in one of the buginfo files.
>
>
> I hope this will help with any questions you may have about what
> BugHunter is, and what it is not. If you have any questions, I will
> monitor this thread; you may respond here or in email.
>
> Thanks for reading!

No thanks required on account I'm not interested.