Exetools  

Go Back   Exetools > General > General Discussion

Notices

 
 
Thread Tools Display Modes
Prev Previous Post   Next Post Next
  #9  
Old 08-23-2019, 03:21
chants chants is offline
VIP
 
Join Date: Jul 2016
Posts: 826
Rept. Given: 47
Rept. Rcvd 50 Times in 31 Posts
Thanks Given: 737
Thanks Rcvd at 1,140 Times in 529 Posts
chants Reputation: 51
The module has the failing check of PARSER_SALT_LENGTH ("Salt-length exception"):
Code:
  const bool parse_rc = generic_salt_decode (hashconfig, salt_pos, salt_len, (u8 *) salt->salt_buf, (int *) &salt->salt_len);

  if (parse_rc == false) return (PARSER_SALT_LENGTH);
I found the extra change you mention elsewhere:
Quote:
https://github.com/hashcat/hashcat/blob/master/src/shared.c
Code:
  u32 tmp_u32[(64 * 2) + 1] = { 0 };
  u8 *tmp_u8 = (u8 *) tmp_u32;
  if (in_len > 512) return false; // 512 = 2 * 256 -- (2 * because of hex), 256 because of maximum salt length in salt_t
So yes 2048 and 16384 should do the trick there. I see no problem with why you would get any further errors.

I also agree that PW_MAX and SALT_MAX should be the same value.

It looks like you have an old version of the source or did not change shared.c where it really needs to be changed as your error indicates this change you presume to have made was not yet made.
Reply With Quote
 

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



All times are GMT +8. The time now is 00:14.


Always Your Best Friend: Aaron, JMI, ahmadmansoor, ZeNiX, chessgod101
( Since 1998 )