+- hashcat Forum (https://hashcat.net/forum)
+-- Forum: Support (https://hashcat.net/forum/forum-3.html)
+--- Forum: hashcat (https://hashcat.net/forum/forum-45.html)
+--- Thread: can hashcat be used only for hashing? (/thread-6801.html)
can hashcat be used only for hashing? - abdou99 - 08-19-2017
Hi
is it possible to use hashcat only for hashing?
example:
./hashcat64.bin -m0 wordlist.txt output.txt
wordlist.txt:
admin
user
testing
output.txt:
21232f297a57a5a743894a0e4a801fc3:admin
ee11cbb19052e40b07aac0ca060c23ee:user
ae2b1fca515949e5d54fb22b8ed95575:testing
thanks
RE: can hashcat be used only for hashing? - undeath - 08-19-2017
https://hashcat.net/forum/thread-6791.html
RE: can hashcat be used only for hashing? - abdou99 - 08-19-2017
not what im looking for..
i have already done such solutions, but i think a gpu task would be much faster
RE: can hashcat be used only for hashing? - philsmd - 08-20-2017
The main problem with your approach (e.g something like "I just want to use the GPU to generate a hash list faster") is that the main bottleneck there for sure is I/O.
Even if you use the fastest SSD or ramdisk, all operations involved with I/O (all those instructions, caching/buffering etc) will take way longer and will undo any speedup you achieve by using GPUs.
That's also why hashcat doesn't show/print every (password) candidate it is currently hashing.
So for short, you shouldn't forget that the slowest part in the chain (the so called bottleneck) will determine how fast the overall process is. It doesn't make sense to use the fastest hardware for hashing (or let's better say to convert passwords to hashes and write them somewhere) if you know that there are some other operations (like writing to a file/disk/RAM etc) that are much slower and will reduce the speed by a significant amount.