Skip to content
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

A WPA 2 karma attack (saved network handshaker ) #22

Closed
minanagehsalalma opened this issue Jan 23, 2020 · 2 comments
Closed

A WPA 2 karma attack (saved network handshaker ) #22

minanagehsalalma opened this issue Jan 23, 2020 · 2 comments
Assignees
Labels
feature New feature invalid Invalid issue

Comments

@minanagehsalalma
Copy link

as karma attacks works on saved open networks only and not secured ones so we will need to have the password first to get it work although this seems a bit hard... the number of saved networks Guarantee that there is a one with a weak password... so will need to make the karma attack start two networks of the targeted prob one open and the second secured and the victim will auto connect to the one with the correct configuration with the saved obviously correct password and we save that handshake with the other handshakes captured form the same device to brute force and break the ones with the weak passwords.

@SkypLabs
Copy link
Owner

Hi @minanagehsalalma,

ProbeQuest is not meant to be used for capturing network handshakes. It only focuses on the collect and the exploitation of probe requests. However, it will be soon possible to know which saved networks are open by answering the received probe requests with fake probe responses (see #7).

I close this issue but feel free to comment or reopen it if you think I misunderstood your point.

@SkypLabs SkypLabs added the invalid Invalid issue label Oct 15, 2020
@minanagehsalalma
Copy link
Author

However, it will be soon possible to know which saved networks are open by answering the received probe requests with fake probe responses (see #7).

@SkypLabs thanks that would be great ....

ProbeQuest is not meant to be used for capturing network handshakes. It only focuses on the collect and the exploitation of probe requests

i know ... with the upcoming feature it would be really useful as a side tool in doing so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature invalid Invalid issue
Projects
None yet
Development

No branches or pull requests

2 participants