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.

Sign up for GitHub

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

Jump to bottom

Reaver does not always provide PSK when WPS PIN is found #76

Closed
derv82 opened this issue Mar 24, 2018 · 2 comments
Closed

Reaver does not always provide PSK when WPS PIN is found #76

derv82 opened this issue Mar 24, 2018 · 2 comments
Labels
enhancement

Comments

@derv82
Copy link
Owner

derv82 commented Mar 24, 2018

Mentioned in #52

I think Bully can find the PSK when force-fed the correct PIN (via --bruteforce and -p?). There's also a method using wpa_supplicant if I'm wrong about Bully.
This was referenced Mar 24, 2018
Open
Closed
@derv82
Copy link
Owner Author

derv82 commented Mar 24, 2018

Apparently it can be done using bully as described above.

Boom shaka laka:

wifite-psk-from-bully

@derv82 derv82 closed this as completed in 19c38bd Mar 24, 2018
@derv82
Copy link
Owner Author

derv82 commented Mar 31, 2018

Note: Had to add --force switch to the bully command. 528741f

Not sure why it worked without --force last week.

cbrunnkvist pushed a commit to cbrunnkvist/wifite2 that referenced this issue Jun 4, 2023
@kimocoder
Merge pull request derv82#76 from danielfullmer/tshark-double-quote
c75e204 
Don't double quote tshark filter
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@derv82