search

brannondorsey / naive-hashcat

Crack password hashes without the fuss :cat2:
MIT License
1.21k stars 161 forks source link

After each iteration (1-2 seconds) naive-hashcat stops and waits for user input #9

Closed yeralin closed 6 years ago

yeralin commented 6 years ago

Hello,

It might be a stupid question. But while I'm trying to run naive-hashcat, it stops after each iteration and prints: [s]tatus [p]ause [b]ypass [c]echpoint [q]uit => I'm trying to avoid this problem running yes b | ./naive-hashcat.sh

brannondorsey commented 6 years ago

Hi there,

Are you sure that the behavior you are observing is actually stopping each attack? If memory serves me correctly, that is the standard message printed by hashcat during a crack, and it indicates the crack is operating normally, but you as the user have several options to interrupt it or view in-progress information. For instance, pressing "s" during a crack should print information about the current crack. The reason you are seeing several of these messages in succession is that naive-hashcat attempts several separate cracks using different combinations of rules. One of these messages should be printed for each run of the hashcat binary.

yeralin commented 6 years ago

@brannondorsey is right. I thought that when this message is printed, attack stops which is not true.