Hi all, I'm attempting to run hashcat (6.2.6+ds2-1+b1) in Attack Mode 22000 (WPA-PBKDF2-PMKID+EAPOL) on a OnePlus 7T Pro 5G mobile device, via The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali) NetHunter.
I consistently run into an error when running the following command:
"hashcat -a 0 -m 22000 (hashfile) (wordlist)"
The program appears to load as normal until during the backend runtime intialization, where the console is interrupted by a message reading "zsh: segmentation fault". After some digging online, I found that this error is generally related to insufficient memory, however top reports only 3469 MiB mem used out of 11583 MiB total.
In the process of elimination, I determined the following:
1: The error appears to only occur in attack mode 22000 (mode 0 and 22001 worked fine)
2: The error occurs regardless of hashfile and wordlist used, even occuring in benchmark mode (hashcat -a 22000 -b).
3: The error appears to have originated in one of the more recent versions, as I was able to avoid it when running "hashcat -a 22000 -b" in hashcat version 6.0.0, assembled from the official github repo source code.
4: Uninstalling (using apt purge) and reinstalling hashcat, along with all of its dependent and recommended packages, does not resolve the error.
For my purposes, I can settle for the workaround of using version 6.0.0, yet I must admit that I am curious as to the cause of this issue. Would anyone be willing to instruct me as to how to gather the relevant information to determine the source of error?
I consistently run into an error when running the following command:
"hashcat -a 0 -m 22000 (hashfile) (wordlist)"
The program appears to load as normal until during the backend runtime intialization, where the console is interrupted by a message reading "zsh: segmentation fault". After some digging online, I found that this error is generally related to insufficient memory, however top reports only 3469 MiB mem used out of 11583 MiB total.
In the process of elimination, I determined the following:
1: The error appears to only occur in attack mode 22000 (mode 0 and 22001 worked fine)
2: The error occurs regardless of hashfile and wordlist used, even occuring in benchmark mode (hashcat -a 22000 -b).
3: The error appears to have originated in one of the more recent versions, as I was able to avoid it when running "hashcat -a 22000 -b" in hashcat version 6.0.0, assembled from the official github repo source code.
4: Uninstalling (using apt purge) and reinstalling hashcat, along with all of its dependent and recommended packages, does not resolve the error.
For my purposes, I can settle for the workaround of using version 6.0.0, yet I must admit that I am curious as to the cause of this issue. Would anyone be willing to instruct me as to how to gather the relevant information to determine the source of error?
