-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SOLUTION: I cannot crack a password for gmail/hotmail/outlook365/... #613
Comments
how to fix this ? |
Maybe this could be fixed but I never will because that would be - except for very rare circumstances - an illegal usage of the tool. And for these rare circumstances the person hired to perform the authorized penetration would be highly skilled and can easily make the necessary changes. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
I had found out (and it was still true two years ago) that gmail can be tested with pop3s://smtp.gmail.com |
This comment was marked as off-topic.
This comment was marked as off-topic.
quiero recuperar la contraseña de mi gmail y de mi facebook pero no me acuerdo cual eran |
Que es tu correo electronico |
Hii guys I want to find password of instagram and I realy don't know how |
@vanhauser-thc Just curious, how is the password cracker indicated? Is there a standard header for this, or does it vary by platform? |
ALL email services have password cracking protection enable, either blocking offender's IP addresses, faking positive results for bad passwords or faking negative results for a correct password.
Also hydra is telling the mail server that it is a password cracking tool to prevent misuse.
So if you test your own gmail/hotmail/... user account hydra will very likely tell you that the password is wrong.
But it is not hydra that is wrong, it is the mail server detecting an attack attempt and giving a fake reply.
The text was updated successfully, but these errors were encountered: