Yesterday, 06:44 PM
Totally reasonable suggestion, but no luck.
Previously the wordlist was gzipped and stored on a zfs hdd, but I get the same segfault when it is decompressed to .txt (and seems fine when I open it) and placed on the nvme next to the zip file.
Also segfault when I use `john.txt` as the wordlist.
Could it have anything to do with using the wrong mode? I am using 17220 based on the below gist, matching on the first part of my `zip2john` output:
https://gist.github.com/dwallraff/6a50b5...560c176401
my zip2john output starts with:
I wasn't aware of `hashcat --identify`, trying it now.
Previously the wordlist was gzipped and stored on a zfs hdd, but I get the same segfault when it is decompressed to .txt (and seems fine when I open it) and placed on the nvme next to the zip file.
Also segfault when I use `john.txt` as the wordlist.
Could it have anything to do with using the wrong mode? I am using 17220 based on the below gist, matching on the first part of my `zip2john` output:
https://gist.github.com/dwallraff/6a50b5...560c176401
my zip2john output starts with:
Code:
my_log.zip:$pkzip2$3*1*1*0*8*24I wasn't aware of `hashcat --identify`, trying it now.