You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If there are abnormal errors such as connection failure in password blasting, for example, when hydra exits with hydra_child_exit(1) and hydra_child_exit(2), it will reconnect and retry the username and password used this time. However, an error occurred in the function hydra_send_next_pair, which caused the username to be updated to the next username, but the password still used this time.
The reason is that after entering the function hydra_send_next_pair, the “hydra_heads[head_no]->redo” is judged, and “hydra_heads[head_no]->redo” and “snpdone” are reassigned, resulting in the following conditions not being met, the username and password of the group are recognized as complete, and the subsequent username and password acquisition also has an exception, which eventually leads to The username and password that were re-attempted to crack are inconsistent with those in the dictionary, resulting in false positives.
The hydra log is as follows, pay attention to the relevant log of child 7.
The relevant username-password pairs in the dictionary are as follows:
leimingyong:1234
admin:leimingyong
sa:myPassword
Administrator:root@123
The logic in the above figure will cause the judgment in the figure below to fail, so that the process enters the complete logic of else.
At present, the first judgment logic is blocked, and the username and password guessed are normal. I am not sure whether this method is completely correct.
This issue will cause the correct username-password pair "admin:1234" for the following situations to be reported twice.
test:1234
admin:1234
English is not very good, please understand.Thanks!
The text was updated successfully, but these errors were encountered:
As shown in the figure below, at the beginning of the function hydra_send_next_pair, redo, snp_is_redo and snpdone are not assigned values, and the function logic is normal after shielding.
The text was updated successfully, but these errors were encountered: