hashcat Forum

can i know what wrong??? 

Minimum password length supported by kernel: 64
Maximum password length supported by kernel: 64

Watchdog: Temperature abort trigger set to 90c

Integer overflow detected in keyspace of mask: ?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?
1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1

What the hell are you trying to crack? There is almost no way you will ever be able to run a mask that large unless your custom character is like, 1 character. And even then, there must be a better way. A 64 character mask is absolutely not ideal or feasible for basically anything I can think of.

(04-28-2019, 08:23 AM)Chick3nman Wrote: [ -> ]What the hell are you trying to crack? There is almost no way you will ever be able to run a mask that large unless your custom character is like, 1 character. And even then, there must be a better way. A 64 character mask is absolutely not ideal or feasible for basically anything I can think of.

-m 2501 -1 abcdef0123456789 ?1??1?.......................

Keyspace is stored as an unsigned 64-bit integer. 16^64 is much, much larger than 2^64 - 1.

You might want to do the math on how long it would take to crack 16^64.

2501 and 16801 hash modes are designed to verify (pre-)calculated PMKs. Latest hashcat use this modes to detect already recovered passwords, by testing the hash against the PMK (take a look at new hashcat potfile format: PMK : ESSID : PSK).

It doesn't make sense to try to recover a PMK by a mask.

BTW:
Captured WPA1/2 hashes (EAPOL and PMKID) are not static. They depend on AP and CLIENT values like MAC and NONCE. Some of them change from connect attempt to connect attempt (NONCE). While the PMK is unique for a WPA1/2 network (unless the PSK doesn't change) old md5_64 and PMKID aren't. This is the reason for the new potfile format!

Thankssssssssss
can i know any Exp??? PMK : ESSID : PSK
please how to do??

the answer hasn't changed since last year. https://hashcat.net/forum/thread-7749-po...l#pid41663