You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
first simple workflow would be looking into your jwt.txt and deleting everything not needed by hashcat like comments and so on
when looking into the module 16500 you will see hashcat is supporting 3 kernels, JWT_HS256, JWT_HS384, JWT_HS512
token seperated by . max 2047, max 2047 . max68 in size, if jwt is now using lets say JWT_HS1024, you/hashcat will need a new kernel to support this
second, there were already in the past some modules changed due to things like increased iterations rounds where the old var or the size checkup failed
could you provide your jwt.txt? please alter different parts wit XXXXX, but let the overallcount intact, so delete 5 chars and add 5 X on the same spot, plz dont delete the .
Feature: Increase allowed JWT token size.
Current Behavior: Small tokens are allowed, but larger ones get rejected with the following:
Hashfile 'jwt.txt' on line 1 (token...): Token length exception
Additional notes:
Developers are adding lots of information into tokens that exceed the allowed 2kb size limit.
I'm working with a token that is ~4KB in size.
If I can get clear direction on what changes need to be made, I can make them.
Hashcat version (please complete the following information):
The text was updated successfully, but these errors were encountered: