03-29-2024, 11:48 AM
Alright, the beta works, but I now get:
I would assume the problem stems from how gpg2john.exe is creating the hash.
If I take the example hash, that is generated from, .\hashcat.exe -m17030 --example-hashes --mach, and break it out like this:
I can see that my hash that was created from gpg2john.exe is 3 lines shorter.
From the example, it looks like I am missing the values for:
I have also noticed that very long string value is much shorter for my hash, which might also be a problem?
Is there any documentation on what each section of the hash file is, that is each section separated by the asterisk?
Code:
Hashfile 'S:\scratch\hashcat-foobar-gpg-hash.txt' on line 1 ($gpg$*...18*8*9*65011712*4b9b39f440ed3ec5): Token length exception
* Token length exception: 1/1 hashes
This error happens if the wrong hash type is specified, if the hashes are
malformed, or if input is otherwise not as expected (for example, if the
--username option is used but no username is present)
I would assume the problem stems from how gpg2john.exe is creating the hash.
If I take the example hash, that is generated from, .\hashcat.exe -m17030 --example-hashes --mach, and break it out like this:
Code:
$gpg$
1
668
2048
e75985b4e7d0bce9e38925a5cf69494ae9a2ccfe2973f077d9423642fffec8bee0e327178a4a3431875ca1f377b9f89269e7c42b94150859d9e5bf5c4504d63076b270118183dda75d253492be8b680c0061e7f130010a00a09a0456710051f2483052ad209fcb9f194f78ecd04fd04953fa1cd6f7ce9babca8b2ee6432730de069648460b2822fe355ed19e0055c69251097681901d7183626019d938727399df47f5249f25b1c73e8654bf935014533845f278e6dd94b8c2964ad6a87c718967686f39a88b21a0e5a93321d4733c81d9310955db6990d8cd02bcf73159b1f48f5615def601aa3e12bf30384da41b558b1eef1111cfc85c8772c123a7b977e2ba399f65679c35b9a2abfde0230a5706fe99f5460c700b1498b1661353ec30eab25defb9af2e7e744fd050d2e7c87542d8bc49e728a7734accf2801dc5972192670858f2004308f3afdd94acd44e1161c44dd372296ca7fe40cbb541c21d640a10df34460c4f5c7cd1bf3b3282668d7edb53be4d843aef4b6f0357526d9c4432aa2a45e113a73e75bfec98cb4cc020ab6cca35336fd188140fd16183dbe288707421e698b6e4801508ae903de3e5d600bd613ea612af92780e53be37722897edb8a588193e7d28819c2f0cbb4e97c3e830113ce14ab05ddb82552fc5e82c386ec2fe9b2d86fc7ade39e341e3dd828502cc3dd038cb21cb0512e79dca9f5a9eae78b2e91aa0732ac77fbc3bc5575c210f519c178669ea99bef62eb6761dfa76407d0d501b07a696a0214dafde7b0bfb48e8ba445b6b42a859a63cb91c9d991ed030ef9e6c63f53b395e14821d7039e4455e0e3712f77f64b7abaa04467bd5b9be26c5e098430187676d0aa7206e2e4fa2e5b7bd486d18b0f3859e94319ccac587574a7bae6ccb3e9414cc769761cf6a0fa1b33cccd1a4b0b04c0d52cd
3
254
8
9
16
343d26cf2c10a8f8a161874fbb218c12
65536
666ae8d1c98404b0
I can see that my hash that was created from gpg2john.exe is 3 lines shorter.
From the example, it looks like I am missing the values for:
Code:
2048
16
65536
I have also noticed that very long string value is much shorter for my hash, which might also be a problem?
Is there any documentation on what each section of the hash file is, that is each section separated by the asterisk?