I don't understand the problem here:
Your example:
- algo: -m 10 = md5($pass.$salt)
- string to hash: "11puma11" (without quotes)
if pass is "11puma" and salt is "11" then we end up with a string for $pass.$salt of "11puma11"
and indeed if you generate the md5 hash for "11puma11" (without quotes) the hash is correct:
echo -n 11puma11 | md5sum
f49cf95028de0f6ec389a1a3df65ee44
So everything is as expected. i.e. there are 2 "11" involved (one from password, the other - in this particular case - is also within the salt).
I don't see any problem of oclHashcat here. You just need to understand what is involved here (i.e. the 2 "11" that come from 2 different ingredients).
Btw: if this is the case for every hash/pass pair then you maybe should look at a total different algo, i.e. -m 3800 = md5($salt.$pass.$salt): if $salt = "11" and $pass is "puma", we now end up with "11puma11" again (note: $pass did change from "11puma" to only "puma" now)
Your example:
- algo: -m 10 = md5($pass.$salt)
- string to hash: "11puma11" (without quotes)
if pass is "11puma" and salt is "11" then we end up with a string for $pass.$salt of "11puma11"
and indeed if you generate the md5 hash for "11puma11" (without quotes) the hash is correct:
echo -n 11puma11 | md5sum
f49cf95028de0f6ec389a1a3df65ee44
So everything is as expected. i.e. there are 2 "11" involved (one from password, the other - in this particular case - is also within the salt).
I don't see any problem of oclHashcat here. You just need to understand what is involved here (i.e. the 2 "11" that come from 2 different ingredients).
Btw: if this is the case for every hash/pass pair then you maybe should look at a total different algo, i.e. -m 3800 = md5($salt.$pass.$salt): if $salt = "11" and $pass is "puma", we now end up with "11puma11" again (note: $pass did change from "11puma" to only "puma" now)