DeforaNetworks/hashcat
DeforaNetworks/hashcat
3
0
Fork 0
Code Releases Activity
hashcat/src/modules
History
jsteube 684256022e Small fix for -m 18900
2019-02-22 16:00:08 +01:00
..
module_00000.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_00010.c
Add generic_salt_encode so we have both function types
2019-02-14 10:52:24 +01:00
module_00011.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_00012.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_00020.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_00021.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_00022.c
Allocate always MAX_SALT * 2 bytes for temporary buffers going into generic_salt_encode()
2019-02-16 14:07:53 +01:00
module_00023.c
Allocate always MAX_SALT * 2 bytes for temporary buffers going into generic_salt_encode()
2019-02-16 14:07:53 +01:00
module_00030.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_00040.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_00050.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_00060.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_00100.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_00101.c
Fixed output length in -m 101
2019-02-13 10:10:08 +01:00
module_00110.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_00111.c
Respect base64 padding lenghts in input tokenizer
2019-02-21 09:17:30 +01:00
module_00112.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_00120.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_00121.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_00122.c
Allocate always MAX_SALT * 2 bytes for temporary buffers going into generic_salt_encode()
2019-02-16 14:07:53 +01:00
module_00124.c
Allocate always MAX_SALT * 2 bytes for temporary buffers going into generic_salt_encode()
2019-02-16 14:07:53 +01:00
module_00125.c
Allocate always MAX_SALT * 2 bytes for temporary buffers going into generic_salt_encode()
2019-02-16 14:07:53 +01:00
module_00130.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_00131.c
Allocate always MAX_SALT * 2 bytes for temporary buffers going into generic_salt_encode()
2019-02-16 14:07:53 +01:00
module_00132.c
Allocate always MAX_SALT * 2 bytes for temporary buffers going into generic_salt_encode()
2019-02-16 14:07:53 +01:00
module_00133.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_00140.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_00141.c
Respect base64 padding lenghts in input tokenizer
2019-02-21 09:17:30 +01:00
module_00150.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_00160.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_00200.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_00300.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_00400.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_00500.c
Allocate always MAX_SALT * 2 bytes for temporary buffers going into generic_salt_encode()
2019-02-16 14:07:53 +01:00
module_00501.c
Rename parse_and_store_generic_salt to generic_salt_decode
2019-02-14 09:53:29 +01:00
module_00600.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_00900.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_01000.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_01100.c
Add generic_salt_encode so we have both function types
2019-02-14 10:52:24 +01:00
module_01300.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_01400.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_01410.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_01411.c
Respect base64 padding lenghts in input tokenizer
2019-02-21 09:17:30 +01:00
module_01420.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_01421.c
Allocate always MAX_SALT * 2 bytes for temporary buffers going into generic_salt_encode()
2019-02-16 14:07:53 +01:00
module_01430.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_01440.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_01441.c
Respect base64 padding lenghts in input tokenizer
2019-02-21 09:17:30 +01:00
module_01450.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_01460.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_01500.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_01600.c
Allocate always MAX_SALT * 2 bytes for temporary buffers going into generic_salt_encode()
2019-02-16 14:07:53 +01:00
module_01700.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_01710.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_01711.c
Respect base64 padding lenghts in input tokenizer
2019-02-21 09:17:30 +01:00
module_01720.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_01722.c
Allocate always MAX_SALT * 2 bytes for temporary buffers going into generic_salt_encode()
2019-02-16 14:07:53 +01:00
module_01730.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_01731.c
Allocate always MAX_SALT * 2 bytes for temporary buffers going into generic_salt_encode()
2019-02-16 14:07:53 +01:00
module_01740.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_01750.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_01760.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_01800.c
Allocate always MAX_SALT * 2 bytes for temporary buffers going into generic_salt_encode()
2019-02-16 14:07:53 +01:00
module_02000.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_02100.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_02400.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_02410.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_02500.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_02501.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_02600.c
Rename parse_and_store_generic_salt to generic_salt_decode
2019-02-14 09:53:29 +01:00
module_02611.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_02612.c
Fixed salt_max in -m 2612
2019-02-17 07:36:28 +01:00
module_02711.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_02811.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_03000.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_03100.c
Fix a warning in -m 3100
2019-02-14 13:17:16 +01:00
module_03200.c
Add generic_salt_encode so we have both function types
2019-02-14 10:52:24 +01:00
module_03710.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_03711.c
Allocate always MAX_SALT * 2 bytes for temporary buffers going into generic_salt_encode()
2019-02-16 14:07:53 +01:00
module_03800.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_03910.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_04010.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_04110.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_04300.c
Rename parse_and_store_generic_salt to generic_salt_decode
2019-02-14 09:53:29 +01:00
module_04400.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_04500.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_04520.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_04521.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_04522.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_04700.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_04800.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_04900.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_05100.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_05200.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_05300.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_05400.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_05500.c
Rename parse_and_store_generic_salt to generic_salt_decode
2019-02-14 09:53:29 +01:00
module_05600.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_05700.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_05800.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_06000.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_06100.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_06211.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_06212.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_06213.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_06221.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_06222.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_06223.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_06231.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_06232.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_06233.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_06241.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_06242.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_06243.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_06300.c
Allocate always MAX_SALT * 2 bytes for temporary buffers going into generic_salt_encode()
2019-02-16 14:07:53 +01:00
module_06400.c
Allocate always MAX_SALT * 2 bytes for temporary buffers going into generic_salt_encode()
2019-02-16 14:07:53 +01:00
module_06500.c
Allocate always MAX_SALT * 2 bytes for temporary buffers going into generic_salt_encode()
2019-02-16 14:07:53 +01:00
module_06600.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_06700.c
Allocate always MAX_SALT * 2 bytes for temporary buffers going into generic_salt_encode()
2019-02-16 14:07:53 +01:00
module_06800.c
Allocate always MAX_SALT * 2 bytes for temporary buffers going into generic_salt_encode()
2019-02-16 14:07:53 +01:00
module_06900.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_07000.c
Fix some module hash output in -O mode
2019-02-13 22:08:19 +01:00
module_07100.c
Fixed length check for raw PBKDF2 modules
2019-02-13 10:03:07 +01:00
module_07200.c
Fixed length check for raw PBKDF2 modules
2019-02-13 10:03:07 +01:00
module_07300.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_07400.c
Allocate always MAX_SALT * 2 bytes for temporary buffers going into generic_salt_encode()
2019-02-16 14:07:53 +01:00
module_07500.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_07700.c
Allocate always MAX_SALT * 2 bytes for temporary buffers going into generic_salt_encode()
2019-02-16 14:07:53 +01:00
module_07701.c
Allocate always MAX_SALT * 2 bytes for temporary buffers going into generic_salt_encode()
2019-02-16 14:07:53 +01:00
module_07800.c
Allocate always MAX_SALT * 2 bytes for temporary buffers going into generic_salt_encode()
2019-02-16 14:07:53 +01:00
module_07801.c
Allocate always MAX_SALT * 2 bytes for temporary buffers going into generic_salt_encode()
2019-02-16 14:07:53 +01:00
module_07900.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_08000.c
Allocate always MAX_SALT * 2 bytes for temporary buffers going into generic_salt_encode()
2019-02-16 14:07:53 +01:00
module_08100.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_08200.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_08300.c
Allocate always MAX_SALT * 2 bytes for temporary buffers going into generic_salt_encode()
2019-02-16 14:07:53 +01:00
module_08400.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_08500.c
Allocate always MAX_SALT * 2 bytes for temporary buffers going into generic_salt_encode()
2019-02-16 14:07:53 +01:00
module_08600.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_08700.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_08800.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_08900.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_09000.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_09100.c
Add -m 9100 unit test
2019-02-18 09:48:39 +01:00
module_09200.c
Fixed length check for raw PBKDF2 modules
2019-02-13 10:03:07 +01:00
module_09300.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_09400.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_09500.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_09600.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_09700.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_09710.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_09720.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_09800.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_09810.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_09820.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_09900.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_10000.c
Fixed length check for raw PBKDF2 modules
2019-02-13 10:03:07 +01:00
module_10100.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_10200.c
Respect base64 padding lenghts in input tokenizer
2019-02-21 09:17:30 +01:00
module_10300.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_10400.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_10410.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_10420.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_10500.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_10600.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_10700.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_10800.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_10900.c
Respect base64 padding lenghts in input tokenizer
2019-02-21 09:17:30 +01:00
module_11000.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_11100.c
Rename parse_and_store_generic_salt to generic_salt_decode
2019-02-14 09:53:29 +01:00
module_11200.c
Allocate always MAX_SALT * 2 bytes for temporary buffers going into generic_salt_encode()
2019-02-16 14:07:53 +01:00
module_11300.c
Bitcoin Wallet: Be more user friendly by allowing a larger data range for ckey and public_key
2019-02-20 16:20:28 +01:00
module_11400.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_11500.c
Allocate always MAX_SALT * 2 bytes for temporary buffers going into generic_salt_encode()
2019-02-16 14:07:53 +01:00
module_11600.c
fixes 7-Zip parser limits for encrypted/decrypted data lengths
2019-02-15 18:49:16 +01:00
module_11700.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_11750.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_11760.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_11800.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_11850.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_11860.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_11900.c
Respect base64 padding lenghts in input tokenizer
2019-02-21 09:17:30 +01:00
module_12000.c
Respect base64 padding lenghts in input tokenizer
2019-02-21 09:17:30 +01:00
module_12001.c
Fixed length check for raw PBKDF2 modules
2019-02-13 10:03:07 +01:00
module_12100.c
Respect base64 padding lenghts in input tokenizer
2019-02-21 09:17:30 +01:00
module_12200.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_12300.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_12400.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_12500.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_12600.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_12700.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_12800.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_12900.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_13000.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_13100.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_13200.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_13300.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_13400.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_13500.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_13600.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_13711.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_13712.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_13713.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_13721.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_13722.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_13723.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_13731.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_13732.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_13733.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_13741.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_13742.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_13743.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_13751.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_13752.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_13753.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_13761.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_13762.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_13763.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_13771.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_13772.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_13773.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_13800.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_13900.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_14000.c
Add generic_salt_encode so we have both function types
2019-02-14 10:52:24 +01:00
module_14100.c
Add generic_salt_encode so we have both function types
2019-02-14 10:52:24 +01:00
module_14400.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_14600.c
Allow module_hash_encode() to be set to MODULE_DEFAULT if OPTS_TYPE_BINARY_HASHFILE is set. In that case return hashfile name
2019-02-22 07:00:34 +01:00
module_14700.c
Allocate always MAX_SALT * 2 bytes for temporary buffers going into generic_salt_encode()
2019-02-16 14:07:53 +01:00
module_14800.c
Allocate always MAX_SALT * 2 bytes for temporary buffers going into generic_salt_encode()
2019-02-16 14:07:53 +01:00
module_14900.c
Add generic_salt_encode so we have both function types
2019-02-14 10:52:24 +01:00
module_15000.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_15100.c
Allocate always MAX_SALT * 2 bytes for temporary buffers going into generic_salt_encode()
2019-02-16 14:07:53 +01:00
module_15200.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_15300.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_15400.c
Fix -m 15400 output
2019-02-13 14:16:30 +01:00
module_15500.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_15600.c
Where generic_salt_decode() is used, the generic_salt_encode() should be used, too
2019-02-14 13:05:14 +01:00
module_15700.c
Allocate always MAX_SALT * 2 bytes for temporary buffers going into generic_salt_encode()
2019-02-16 14:07:53 +01:00
module_15900.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_16000.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_16100.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_16200.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_16300.c
Allocate always MAX_SALT * 2 bytes for temporary buffers going into generic_salt_encode()
2019-02-16 14:07:53 +01:00
module_16400.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_16500.c
Add some missing benchmark defaults for dynamic kern_type module in -m 16500
2019-02-12 21:11:47 +01:00
module_16600.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_16700.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_16800.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_16801.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_16900.c
Add missing -m 16900
2019-02-13 14:35:33 +01:00
module_17300.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_17400.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_17500.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_17600.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_17700.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_17800.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_17900.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_18000.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_18100.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_18200.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_18300.c
Fix -m 18300 module
2019-02-13 20:05:16 +01:00
module_18400.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_18500.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_18600.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00
module_18700.c
Rename -m 18700 to Java Object hashCode()
2019-02-22 09:30:56 +01:00
module_18900.c
Small fix for -m 18900
2019-02-22 16:00:08 +01:00
module_99999.c
Get rid of hash_type variable. This hopefully reduces some confusion for new hashcat kernel developers
2019-02-12 16:02:27 +01:00