Add missing formats to pass_gen.pl and the TS.

[jfoug]

This issue should stay perpetually open. When new formats are added to pass_gen.pl (or we have some other technique to generate them), they should be added here.

Also, when new formats are added to JtR, but are not in the TS, we should also add them, and then move them to the 'in pass_gen' table when we code it there, then remove it when it gets added to the TS.

I added code to the -showtypes function in the jtrts.pl file, and now I think we have a pretty comprehensive list of data that we have in pass_gen.pl but not in the TS yet, AND a list of items not even added to pass_gen.pl yet. This is some decent 'todo' work, lol.

These are not in pass_gen.pl or in the TS yet.

• krb5pa-sha1
• krb5pa-sha1-opencl
• 7z
• 7z-opencl
• afs
• cq
• crypt
• dmg
• dmg-opencl
• dominosec
• encfs
• encfs-opencl
• fde
• gpg
• gpg-opencl
• haval-128-4
• haval-256-3
• ike
• keepass
• krb4
• kwallet
• lotus85
• luks
• oldoffice
• oldoffice-opencl
• openbsd-softraid
• openssl-enc
• openvms
• panama
• pdf
• pfx
• pkzip
• putty
• racf
• rar5
• rar5-opencl
• skein-256
• skein-512
• ssh-ng
• sybase-prop
• tripcode
• whirlpool0
• krb5
• rawsha3-224 (in pass_gen only)
• rawsha3-256 (in pass_gen only)
• rawsha3-384 (in pass_gen only)

---These have been added to pass_gen.pl and also placed into TS ---

• keystore
• efs
• keyring
• keyring-opencl
• palshop
• iwork
• mdc2
• has-160
• mongodb-scram
• zipmonster
• eigrp
• snefru-128
• snefru-256
• whirlpool1 (had to hand edit whirlpool.c in perl code to get right vectors)
• mhac-sha224 with variable length salts (bug found in long salt code)
• mhac-sha384 with variable length salts (bug found in long salt code)
• mhac-sha512 with variable length salts (bug found in long salt code)
• mhac-md5 with variable length salts (bug found in long salt code)
• mhac-sha256 with variable length salts (bug found in long salt code)
• cloudkeychain
• vtp
• vnc
• sxc
• sxc-opencl
• dynamic 310-308, 370-428
• blockchain (only v1 hashes)
• blockchain-opencl (only v1 hashes, 64 byte plaintext vs 125 byte built input file.)
• rawsha3-512
• AzureAD
• vdi_256 (full test)
• vdi_128 (full test)
• qnx_md5
• qnx_sha256
• qnx_sha512
• agilekeychain
• agilekeychain-opencl
• bitcoin
• siemens-s7
• strip
• strip-opencl
• clipperz (serious bugs fixed. 2 types input files, flush and 0-LPad)
• citrix_ns10
• blackberry-es10
• chap
• dynamic_1010
• asa-md5
• known_hosts
• hsrp
• sha1crypt
• sha1crypt-opencl
• keychain
• keychain-opencl
• sunmd5
• wpapsk
• wpapsk-opencl
• dummy
• tiger
• whirlpool
• wowsrp (serious bugs fixed. 2 types input files, flush and 0-LPad)
• skey (all 4 types)
• osc
• ripemd-128
• ripemd-160
• raw-sha256-ng
• raw-sha512-ng
• bcrypt-opencl (just needed jtrts.dat lines added)
• aix-smd5

[jfoug]

Ok, most of the low hanging fruit has now been converted, and is now part of the TS. I am sure there are others in our still to do list that we can get, but I think many of these will require a bit more work, but we should be able to get half of the ones left (or more).

Right now, I note there are now 54 formats we do not have in the TS. That is out of ALL formats (385 or so, including the hidden dynamic hashes).

[jfoug]

Question for @magnumripper

Should I add the larger hash dynamic (fixed numbers), or should we just build a script, allowing the user to build them him/her self, and then put .gitignore lines for any of the possible generated data items? There are a lot of them (several hundred).

NOTE, there were not that many missing, so I just added them. Most of the non-standard hashes are not in pass_gen.pl since there is no 'common' perl module for the hash algo.

[magnumripper]

I still think we should generate them on the fly and delete them afterwards.