SHA1 speed difference - Printable Version +- hashcat Forum (https://hashcat.net/forum) +-- Forum: Support (https://hashcat.net/forum/forum-3.html) +--- Forum: hashcat (https://hashcat.net/forum/forum-45.html) +--- Thread: SHA1 speed difference (/thread-10269.html) |
SHA1 speed difference - rste - 08-14-2021 Hi all, I have the following issue. Trying this on GeForce GTX 1080 whit CUDA API (CUDA 11.2). Hashcat is v6.2.3. Code: hashcat.exe -m 100 -w 3 -O -a 3 b89eaac7e61417341b710b727768294d0e6a277b I get speed of 8408.5 MH/s. Which looks OK. Code: b89eaac7e61417341b710b727768294d0e6a277b:hashcat Applying a mask like this Code: hashcat.exe -m 100 -w 3 -O -a 3 b89eaac7e61417341b710b727768294d0e6a277b --hex-charset ?b?b?b?b?b?b Code: Speed.#1.........: 8550.0 MH/s (77.38ms) @ Accel:32 Loops:1024 Thr:1024 Vec:1 Prepending up to two fixed bytes to the mask the speed remains Code: hashcat.exe -m 100 -w 3 -O -a 3 b89eaac7e61417341b710b727768294d0e6a277b --hex-charset 0102?b?b?b?b?b?b Prepending 3 fixed bytes to the mask the spped drops to 5000 MH7s,. Which is also fine. Code: hashcat.exe -m 100 -w 3 -O -a 3 b89eaac7e61417341b710b727768294d0e6a277b --hex-charset 010203?b?b?b?b?b?b Now the problem. Prepending 4 or more fixed bytes the speed drops to 50 MH/s. Code: hashcat.exe -m 100 -w 3 -O -a 3 b89eaac7e61417341b710b727768294d0e6a277b --hex-charset 01020304?b?b?b?b?b?b Funny. If the fixed bytes are in the middle or at the end like this. The speed ramps up again to 5 to 8 GH/s Code: hashcat.exe -m 100 -w 3 -O -a 3 b89eaac7e61417341b710b727768294d0e6a277b --hex-charset ?b01020304?b?b?b?b?b The question. What am I doing wrong? Thanks for your help. Regards rste RE: SHA1 speed difference - atom - 08-14-2021 Nothing, that's exactly the expected behavior. The first 4 byte are used as amplifiers. If you really need to brute force the first 4 byte you can use hybrid rules in -a 0 mode for almost full speed. RE: SHA1 speed difference - rste - 08-15-2021 (08-14-2021, 07:10 PM)atom Wrote: Nothing, that's exactly the expected behavior. The first 4 byte are used as amplifiers. If you really need to brute force the first 4 byte you can use hybrid rules in -a 0 mode for almost full speed. Thank you. I couldn't make it with rules in -a 0, because I found no way to append in byte mode when used with --hex-charset. What worked was generating a dictionary Code: $PSDefaultParameterValues['Out-File:Encoding'] = 'utf8' and using -a 6 Code: .\hashcat.exe -m 100 -w 3 -O -a 6 b89eaac7e61417341b710b727768294d0e6a277b --hex-charset prependmask.txt ?b?b?b The only problem is in -a 6 mode I get "Integer overflow detected in keyspace of mask" with only 4 ?b regardless of the dictionary size. In -a 3 mode overflow happens with 8 ?b. So to test for 6 bytes I have to add another loop to the dictionary generation. |