10-16-2019, 10:51 PM
Thx for answering that question. Of course, I have another (Give a mouse a cookie).
I'll try to explain.
(While using the brain feature)
If I run an attack on a file that has already been processed, the attacks quits within seconds, which is good.
If I make a copy of that file and run the attack on the file, again it quits within seconds.
If I take just a single hash from the file and copy to a new file and run the attack, it takes the full time to process.
Does it not look at each hash and know if an attack has been run on it before? Or is that what client feature 3 does?
Thank You for your time and knowledge.
I'll try to explain.
(While using the brain feature)
If I run an attack on a file that has already been processed, the attacks quits within seconds, which is good.
If I make a copy of that file and run the attack on the file, again it quits within seconds.
If I take just a single hash from the file and copy to a new file and run the attack, it takes the full time to process.
Does it not look at each hash and know if an attack has been run on it before? Or is that what client feature 3 does?
Thank You for your time and knowledge.