01-15-2013, 02:43 PM
- Pot output cannot be customized.
- Outfile output can be customized, using --outfile-format=N.
- I believe hashcat reads dicts line by line, chops \n, and \r if found first, and then processes it.
- The only way to "input" these eol chars to hashcat is to use -a3 (brute-force), --hex-charset, SHex (--outfile-format=5) and user-defined charset with all eol chars needed, represented hex of course.
Something like:
There are other tricky ways, but they're just too dirty to do.
- Outfile output can be customized, using --outfile-format=N.
- I believe hashcat reads dicts line by line, chops \n, and \r if found first, and then processes it.
- The only way to "input" these eol chars to hashcat is to use -a3 (brute-force), --hex-charset, SHex (--outfile-format=5) and user-defined charset with all eol chars needed, represented hex of course.
Something like:
Code:
-plus -a3 -1 0d0a?d --hex-charset -o OUT --outfile-format=5 HASHFILE ?1?1?1?1?1There are other tricky ways, but they're just too dirty to do.