Cant Output Cracked Password with Null Character
#6
(02-08-2013, 10:47 PM)cyphear Wrote: 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.

it's a trade-off between speed and flexibility. one of the ways oclHashcat-plus achieves such high speeds is that it does not use the full implementation of each algorithm. rather, the algorithms are reduced to the absolute minimum steps needed to calculate inputs of very specific lengths.

(02-08-2013, 10:47 PM)cyphear Wrote: The documentation says the CPU version does not support hex charsets.

the documentation is a bit outdated, the cpu version does indeed have support for hex charsets.


Messages In This Thread
RE: Cant Output Cracked Password with Null Character - by epixoip - 02-08-2013, 11:24 PM