02-05-2011, 08:23 AM
(02-04-2011, 10:57 AM)atom Wrote: what the problem using hashcat to do the --remove work?That would mean that you have to actually be physically there once every attack finish to remove them. When you run a batch file (several attacks one after the other), every attack after the first one gets "penalized". Let's say you have 100 hash and the first attack crack 20 of them. Since those hash are so slow to crack because of their high iterations, you really do not want to loose your gain of speed by trying to recrack those 20 in the second attack. If we continue and the second attack cracks 30 of them, without the --remove, the third attack will try to crack a 100 of them. With the --remove, it will run on 50 of them and should be twice faster.