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

Responder settings mismatch #192

Closed
ecapson opened this issue Feb 8, 2022 · 2 comments · Fixed by #206
Closed

Responder settings mismatch #192

ecapson opened this issue Feb 8, 2022 · 2 comments · Fixed by #206

Comments

@ecapson
Copy link

ecapson commented Feb 8, 2022

Describe the bug
Current Responder settings have mismatch with the latest Responder. Unsupported starting options and missing entries in the config file.

To Reproduce

Steps to reproduce the behavior:

  1. Start evil twin with hostile portal

Expected behavior

Responder part of the evil twin won't start

Screenshots

image

Command string(s) used

eaphammer -i wlan0 -c 1 -e test --hostile-portal

EAPHammer verbose output (using the --debug flag)

Unrelated to bug

EAPHammer Version (./eaphammer --version)

Latest on master.
--version no longer exist?

OS (the OS from which you are running EAPHammer)

Kali Arm 5.4.83-Re4son-v8l+
@ecapson
Copy link
Author

ecapson commented Feb 8, 2022

Working on fix

@ecapson ecapson mentioned this issue Feb 8, 2022
Closed
@s0lst1c3 s0lst1c3 mentioned this issue Oct 7, 2023
Merged
@s0lst1c3
Copy link
Owner

s0lst1c3 commented Oct 7, 2023

Resolved 1.14.0

@s0lst1c3 s0lst1c3 closed this as completed Oct 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Devel 1.14.0 s0lst1c3/eaphammer
responder fix ecapson/eaphammer
2 participants
@s0lst1c3 @ecapson