02-07-2011, 06:27 PM
Because oclHashcat currently does not support SSHA hashes, I thought the workaround would be to use -m 101 = sha1($pass.$salt)
But this does not work well, as the salt can actually contain characters such as 0x0A, 0x3A or even 0x00. Then of course, oclHashcat fails to understand the salt when such characters occur.
I think a good feature would be to require hex-encoded salts. This way, oclHashcat would support many other hashing variants out of the box. For instance the CMS ezpublish (http://ez.no/) use "$login\n" as a salt, with hash == md5($salt.$pass).
But this does not work well, as the salt can actually contain characters such as 0x0A, 0x3A or even 0x00. Then of course, oclHashcat fails to understand the salt when such characters occur.
I think a good feature would be to require hex-encoded salts. This way, oclHashcat would support many other hashing variants out of the box. For instance the CMS ezpublish (http://ez.no/) use "$login\n" as a salt, with hash == md5($salt.$pass).