Posts: 15
Threads: 7
Joined: May 2010
(05-29-2010, 06:38 AM)atom Wrote: it reads 40 chars of the line to be the hash, yes, regardless of the position of the seperator. the reason therefore is the problematic hash
alt format. it is possible that the seperator char itself is part of the salt. so i could add -p option but this would not solve the main problem. a better solution would be the user manually setting a fixed length of the salt. this is possible but would require a new option. if user uses this option all salts of all hashes must have exactly that length. this is problematic if you have a hashlist with multiple salts. so i think this is a bit to confusing. you see, the only real solution would be to change the format to maybe xml or something like that. but telling users to put their hashes into xml format would be a overkill.
i see. thank you very much. atom.
but i think add a option to define the salt length is necessary in your next version.because usually the salt in some web applications is fixed length....xml is not a good idea , in my thought
but however , hashcat and oclHashcat are very excellent .
