11-20-2011, 07:00 PM
I do feel that free command line utilities literally always work better and faster then their commercial counterparts. I find that I can do anything I need to in terms of word-list manipulation (simple to complex) using existing tools such as the free hashcat utilities and other free & commercial tools as well.
The only thing *I* would wish for if I had the chance to (in the hashcat utilities suite), is the addition of a utility that could sort MULTI GIGABYTE wordlists with the same awesome speed & efficiency as the existing tools have in doing their tasks.
There really IS no Windows tool that can do that yet, anywhere. Not "slow", and especially NOT "fast". Don't be fooled by commercial tools that say they "do this", as the output from those tools is usually a ruined version of the input file.
So that's what I'd like to see. *proper* sorting/duplicate-removal of multi-gigabyte wordlists that usually exceed 20 gigabytes. Of course, this would also mean having the ability to parse those very same wordlits and remove dangerous characters that other programs could "trip" on while processing those files, such as NULL characters, etc..
Maybe the volatile characters to be removed could be selected on the command line by the user as an extra bonus? :p
The only thing *I* would wish for if I had the chance to (in the hashcat utilities suite), is the addition of a utility that could sort MULTI GIGABYTE wordlists with the same awesome speed & efficiency as the existing tools have in doing their tasks.
There really IS no Windows tool that can do that yet, anywhere. Not "slow", and especially NOT "fast". Don't be fooled by commercial tools that say they "do this", as the output from those tools is usually a ruined version of the input file.
So that's what I'd like to see. *proper* sorting/duplicate-removal of multi-gigabyte wordlists that usually exceed 20 gigabytes. Of course, this would also mean having the ability to parse those very same wordlits and remove dangerous characters that other programs could "trip" on while processing those files, such as NULL characters, etc..
Maybe the volatile characters to be removed could be selected on the command line by the user as an extra bonus? :p