There is some good news here, the new hash type -m 11000 = PrestaShop made it to cpu hashcat already (beta!), oclHashcat support will follow.
But let me use this opportunity for a big Warning for forum user hashnoob (which according to the rules https://hashcat.net/forum/announcement-2.html should already be banned).
The example hash (which you should not have posted at all without explicit request from a moderator), is furthermore a fake/invalid hash. The proof:
$ echo -n salttest | md5sum
d653ea7ea31e77b41041e7e3d32e3e4a
So basically here the salt is "salt" and not k8k8yBEO7bXXjjRH9BoKTojYIA1dNmHDaKiC3sfGRp8eNORfW3joAA3c since md5 ("salttest") == d653ea7ea31e77b41041e7e3d32e3e4a
This is not really what devs (and mods) want to see here. Wrong/fake hash examples do not necessarily help the devs much in implementing the algorithm!
But let me use this opportunity for a big Warning for forum user hashnoob (which according to the rules https://hashcat.net/forum/announcement-2.html should already be banned).
The example hash (which you should not have posted at all without explicit request from a moderator), is furthermore a fake/invalid hash. The proof:
$ echo -n salttest | md5sum
d653ea7ea31e77b41041e7e3d32e3e4a
So basically here the salt is "salt" and not k8k8yBEO7bXXjjRH9BoKTojYIA1dNmHDaKiC3sfGRp8eNORfW3joAA3c since md5 ("salttest") == d653ea7ea31e77b41041e7e3d32e3e4a
This is not really what devs (and mods) want to see here. Wrong/fake hash examples do not necessarily help the devs much in implementing the algorithm!