[QUESTION] John Do Not Parse the PFX Key

which is the cause of failure of the file, john or PFX file? I have a question about legacyy_dev_auth.pfx in Timelapse. legacyy_dev_auth.pfx was hashed with pfx2john.py and tried to crack the password using john but john could not do it I used crackpkcs12 to escape this problem.

I solved the exercises, but I have a question about john’s strange behavior.

┌─[MKV@virtualbox]─[/mnt/10.10.11.152]
└──╼ $python3 /usr/share/john/pfx2john.py legacyy_dev_auth.pfx > pfx.john
┌─[MKV@virtualbox]─[/mnt/10.10.11.152]
└──╼ $john pfx.john -wordlist:/usr/share/wordlists/rockyou.txt
Using default input encoding: UTF-8
No password hashes loaded (see FAQ)
┌─[MKV@virtualbox]─[/mnt/10.10.11.152]
└──╼ $
1 Like

I also traped with this problem , please tell me how you fixed it

Fixed this when running python 3 with the following fix: pfx2john: use decode() for python3 compatibility · openwall/john@708ea34 · GitHub also noted at PFX P12 will not crack password if exported from mozilla · Issue #4752 · openwall/john · GitHub . If your hash output has ticks “`” in it, you need to update the pfx2john.py script in the john installation.