"Russg" <russgilb@MUNGEsbcglobal.net> wrote in
news:%DRsi.12542$eY.8974@newssvr13.news.prodigy.ne t:

>
> "Dustin Cook" <> wrote in message news:
>> 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!
>>
> Question comes to mind. Where do you get samples to get your ID CRC
> and length? Someone at one of the AV vendors?
>
>
>

Sorry russ old buddy, but you didn't know the difference between a
gopher and a groundhog; you do I'm sure, you were just being a wiseass
about it. Since your trolling then and now, I'm not going to tell you how
the samples arrive, except to say that I can acquire them just as easily
as anybody else; Surf to unsafe sites and allow programs to "install" in
a virtual environment. Various others arrive via different means, but
alas, it's no real big secret. I have access to the same material that I
always have. It's one of those ex-vxer benefits, you might say.

Now, if you have any real questions about the program, I'd be happy to
answer them.


--
Dustin Cook
Author of BugHunter - MalWare Removal Tool - v2.2c
email: bughunter.dustin@gmail.com.removethis
web..: http://bughunter.it-mate.co.uk
Pad..: http://bughunter.it-mate.co.uk/pad.xml