02-08-2013, 10:47 PM
(02-08-2013, 10:39 PM)epixoip Wrote: trac may not still be up after the db crashed the other day, i am not sure its status.
unfortunately there's no way to bypass this, the padding cannot be ignored. the 16 character limitation (which is actually a 15 character limitation, by the way) is better interpreted as a 15 byte limitation. unicode characters count as multiple characters toward the 15-char limit as well.
Bummer, but I appreciate the help. Seems like extending this limit would be good. I dont see this actually happening, but admins could use unicode encoding and require 8 char passwords to prevent hashcat from cracking anything.
(02-08-2013, 10:39 PM)epixoip Wrote: you could use the cpu version of hashcat for these hashes though.
The documentation says the CPU version does not support hex charsets.
http://hashcat.net/wiki/doku.php?id=mask...ets_in_hex