UI needs more instructions for the user. about fluxion

[SwiftPredator]

[gudangboys]

Please correct me if wrong - path specified in Kali from root
/root/Desktop/fluxhandshake/handshake01.cap
Still returns "Hash file does not exist"
Sorry for the silly questions and thanks

[MPX4132]

Let's make sure it's doing what I think it's doing. In the screen shot you showed, it looks like you chose the passive mode, correct? If you chose an aggressive mode (forcing deauthentication), and only airodump-ng came up, there's a problem. If you did in fact chose just a passive attack:

• Did the attack stop when a handshake was captured? Stopping, in this sense, is literal. Meaning, airodump-ng halted completely, but the handshake captor window should not close. This can be verified by looking at the elapsed field in airodump-ng for a few seconds. If the field stopped updating the attack succeeded and you caught a valid handshake.
• If you choose any option in fluxion, while the snooper attack is in progress, does the handshake captor close? It should, if it does not, it's a bug.
  I'm just verifying the behavior, and I understand you would like instructions or a clear sign the attack stopped.

[Geczy]

1. Yes, passive using pyrit.
2. The captor screen did appear to freeze, elapsed time stopped counting up. But nothing happened in the fluxion terminal.
3. Choosing another option while handshake captor is in progress does not close the captor screen.

Need to give instructions on this screen as well. "please wait..." will just leave the user sitting forever

[SwiftPredator]

Got the same bug on all methods.

[MPX4132]

Did the deauthenticator window close? If it did, and the "Handshake Captor" window froze, it means the attack succeeded. You can verify by checking if the handshake captor window (airodump-ng) says "Handshake Captured" on the top right. You can also check by going into "fluxion/attacks/Handshake Snooper/handshakes/" if you see handshakes there, it succeeded and that's a valid handshake.
edit: Sorry, posted this in the wrong thread.

[SwiftPredator]

Its frozen and it don't say "Handshake Captured" on the top right. But there is a .cap file in "fluxion/attacks/Handshake Snooper/handshakes/" after launching the deauthenticator attack.

[MPX4132]

Then yeah, it succeeded, the attack was successful. If the attack failed, there would be no capture file. Does it, by any chance, say "fixed channel -1" or something like that?

[SwiftPredator]

Not in the Handshake Captor or in the fluxion window.

[SwiftPredator]

This is the whole outcome after the window froze. I think the same like @Geczy have it.

[MPX4132]

Oh, I'm sorry. I gave you wrong information. It's actually working perfectly fine from what it looks like in that picture. The handshake captor window should say "WPA Handshake: XXXXXXXXXX" if it caught a handshake. Now you can run the Captive Portal attack by choosing option 1. The captive portal attack will ask you for a handshake and should auto detect that you've already captured one and ask you if you want to use it. It'll then verify it and you can start the attack.

[SwiftPredator]

Ok, did that.Is it normal that it stucks in the output "Starting Captive Portal access point service..."?

[SwiftPredator]

Thanks for your fast help by the way 💯

[MPX4132]

Actually, I'm hanging around here to see if the latest update causes issues. It should not get stuck on starting the access point service. If you still have it open and it's still stuck, open another terminal and run:

# iwconfig

And post the results here. It seems like the access point interface dropped or crashed.

[SwiftPredator]

I just loaded the new version you uploaded and know even the authentication doesn't want to work.
Cant text the Captive Portal now. The Handshake Captor window opens, but the deauthentification doesn't go on. The handsomer view isn't freezing. It worked in the unready version you uploaded before.

[SwiftPredator]

Sry, this auto corrector really doesn't do what i want :( Hope you could analyze the problem anyways.

[MPX4132]

Confirmed, fixing it now.

[MPX4132]

Fixed by commit, thanks for the report.

[SwiftPredator]

ifconfig after # iwconfig

[SwiftPredator]

Ah and thanks for bringing the deauth to work again !

[MPX4132]

Your interfaced dropped out of monitor mode, "wlan0" should be in "Mode:Monitor" like "wlan0FLXap" is.
Try running fluxion with the drop flag, so do:

export FLUXIONDropNet=1; ./fluxion.sh

It could be that the wireless manager is interfering, but I doubt it. It's probably related to the driver.

[Geczy]

Don't see why this was closed? The UI was never updated right? User still has no clue how the handshake attack is progressing @deltaxflux

[deltaxflux]

Because I thought that the problem is fixed after:

Ah and thanks for bringing the deauth to work again !

I think a good idea is that we print a . if the handshake is not found and + if it is found

Sample output
.............+

[Geczy]

You can also check by going into "fluxion/attacks/Handshake Snooper/handshakes/" if you see handshakes there, it succeeded and that's a valid handshake.
edit: Sorry, posted this in the wrong thread.

Left this up for several minutes on my own WiFi, it never seems to capture a handshake

It was deauthenticating everyone, but the deauth appears to have stopped and the window closed. Now it's just this one window

EDIT: I checked my handshakes folder and there does appear to be a handshake capture. So it seems it succeeded? Very confusing UI to the user

[deltaxflux]

If the mdk3 or aireplay window stops the handshake successfully captured

[Geczy]

Yes i know. But ui needs to update too hence the issue being open

[LOLLYTHECAT]

Why fluxion stuck on "[*] Starting Captive Portal access point service..." .. ?

[deltaxflux]

There is a button new issue hint hint

[gudangboys]

Hi I am new to fluxion, can you tell me what path do i specify for the capture file.
Any path I specify it returns a "Hash file does not exist"
Thanks.

[MPX4132]

@gudangboys make sure it’s the absolute path not a relative path.

[MPX4132]

Yeah, that's an absolute path alright. Well, all I can think of is human error somewhere. You sure the .cap file doesn't have a hyphen before the capture number, such as the one below:

/root/Desktop/fluxhandshake/handshake-01.cap

I highly doubt it's fluxion, I haven't had any issues with the path input. That could just be bias from my part, though. Just double check or triple check everything and report back.

[gudangboys]

Thanks for your prompt response.
Would you help me here again please:

1. Am I directing it to an already existing cap file?
2. If so I haven't a cap file, I assume it would write to the file I specify.
3. If not, how do I then create a .cap file to specify the path?
   Thanks in advance for your patience

[anashexor]

I have same problem with gudangboys.. i dont have that .cap file .. how to create it?

[MPX4132]

Sorry for the super late response @gudangboys I'm not sure what happened with the notification. You just have to run the Handshake Snooper attack. The attack will run and once a valid capture file is retrieved, the Handshake Captor window will stop, but it will not close. You can verify it stopped by checking the "Elapsed" field. Ignore the "Handshake Captured" notification on the top right of the Handshake Captor window, it's usually wrong. You can close the Handshake Captor window after if you want. Once you have the file, you can go to the main fluxion window and select another attack, the Captive Portal attack. Since you used the built-in captor, the script will automatically detect any previously retrieved handshake files and will load them itself.

[Geczy]

Gotta add this as instruction to the app :)

[deltaxflux]

I add a UI for the handshake. Try it and share results below.