+- hashcat Forum (https://hashcat.net/forum)
+-- Forum: Deprecated; Ancient Versions (https://hashcat.net/forum/forum-46.html)
+--- Forum: Very old oclHashcat-plus Support (https://hashcat.net/forum/forum-23.html)
+--- Thread: Bad --hex-charset (/thread-1799.html)
Bad --hex-charset - M@LIK - 11-30-2012
--hex-charset affects interpreting the whole command-line instead of working on charsets only.
See below:
Code:
// md5-fu
3631313171ffbf23b394fa8ecd9e83e5:zer0
// hashcat-fu
-plus -a3 --force -1 30 --hex-charset 3631313171ffbf23b394fa8ecd9e83e5 zer?1
...
Status.......: Exhausted
Input.Mode...: Mask (zer?1)
// lol-fu
php -r "print bin2hex('zer0');"
7a657230
-plus -a3 --force --hex-charset 3631313171ffbf23b394fa8ecd9e83e5 7a657230
Status.......: Cracked
Input.Mode...: Mask (7a657230)
// however-fu
-plus -a3 --force -1 30 --hex-charset 3631313171ffbf23b394fa8ecd9e83e5 ?l?l?l?l?1
...
Status.......: Cracked
Input.Mode...: Mask (?l?l?l?1)I guess --hex-charset is actually more of a --hex-it-all!
RE: Bad --hex-charset - atom - 12-08-2012
Yeah thats right. It should have been called --hex-it-all. But since this is how it is implemented and how it is used by many ext. applications I cant change this back. Any idea of how to solve it?
maybe --no-hex-mask ?