Closed bruhgod69 closed 2 months ago
Version: 1.9.0-jumbo-1
Hi. Before we possibly spend more time on this, can you please re-try all of this with the latest code (both script and compiled) from this repo? Our previous release 1.9.0-jumbo-1 is 5 years old now (our/my fault, but nevertheless). A lot has changed since.
In particular, pfx2john.py
in 1.9.0-jumbo-1 is apparently not compatible with Python 3, which I guess is what you're using these days? This has been corrected since. And probably more.
Alternatively, if you insist on getting this to work with 1.9.0-jumbo-1, you can try python2 pfx2john.py
if your distro still has Python 2. This will likely work.
Oh sorry, I didn't realize the precompiled bins on the website are that old.
In particular, my pfx2john
didn't have the decode
methods called like the current. I just replaced it and it works now.
sys.stdout.write("%s:$pfxng$%s$%s$%s$%s$%s$%s$%s:::::%s\n" %
(os.path.basename(filename), mac_algo_numeric,
key_length, iterations, size, binascii.hexlify(salt).decode(),
binascii.hexlify(data).decode(),
binascii.hexlify(stored_hmac).decode(), filename))
(the password was abcd so I just wasted a whold lot of time)
Thanks for the help and sorry for my misunderstanding
I'm trying to find the 4-byte password to a private key in a
.pfx
file. I have tried every possible fix I could find which leads me to believe it may be some sort of a bug.Steps:
I used the provided
pfx2john
to convert the file:Which results in this file: (I put the ..... to truncate, only hex bytes are omitted, no special chars there)
I have tried both LF and CRLF line endings on this file and whether it ends with a newline or not. When I try to supply it to john, it does not seem to recognize the format either way:
I have tried without
--format
, or just./john key.txt
, and withpfx-opencl
but always same result: