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
Right now, argon2-opencl is unnecessarily limited by its PLAINTEXT_LENGTH 100. We should probably bump this to our usual maximum of 125, unless there's any specific reason to keep it at 100, @alainesp?
The text was updated successfully, but these errors were encountered:
Patched to 125, still works (using a CMIYC 2024 hash on an ancient machine):
$ ./john -mask='Adity?l?s?d?d?d?d' pw-argon2id
Device 1: GeForce GTX 570
Using default input encoding: UTF-8
Loaded 1 password hash (argon2-opencl [Blake2 OpenCL])
Cost 1 (t) is 1 for all loaded hashes
Cost 2 (m) is 65536 for all loaded hashes
Cost 3 (p) is 4 for all loaded hashes
Cost 4 (type [0:Argon2d 1:Argon2i 2:Argon2id]) is 2 for all loaded hashes
Trying to compute 18 hashes at a time using 1152 of 1279 MiB device memory
LWS=32 GWS=2304 (72 blocks) => Mode: LOCAL_MEMORY
Press 'q' or Ctrl-C to abort, 'h' for help, almost any other key for status
Aditya@2011 (?)
1g 0:00:00:39 DONE (2024-08-13 17:30) 0.02520g/s 263.5p/s 263.5c/s 263.5C/s Dev#1:68C Adityu 2011..Adityr@2011
Right now, argon2-opencl is unnecessarily limited by its PLAINTEXT_LENGTH 100. We should probably bump this to our usual maximum of 125, unless there's any specific reason to keep it at 100, @alainesp?
There shouldn't be any problem, but I can't provide a guarantee. I can recheck the code this weekend if you need assurance.
Thanks @alainesp. I just wanted to know you don't recall any special reason for choosing 100. I don't see any limitations in the code. Ideally, we'd actually test with a length 125 password (generate such Argon2 hash on CPU).
Right now, argon2-opencl is unnecessarily limited by its
PLAINTEXT_LENGTH 100
. We should probably bump this to our usual maximum of 125, unless there's any specific reason to keep it at 100, @alainesp?The text was updated successfully, but these errors were encountered: