All right, so the good news is we have a valid handshake from the handshake snooper attack.
Now we can set up to perform a captive portal attack.
And that's also the good news.
All right, to go to totally open the terminal screen, change direct reflection.
So let's check if the handshake is saved inflexions database, we know it should be less folders and
files with a command unless change directory to attacks, handshake, snooper, handshakes folder.
List files.
All right, so you're looking at the captured handshake.
So go back to the fluxing folder again.
Run a file with pseudo.
Select captive portal attack.
Now select a channel of the access point that we want to create a fake access point for.
So if your target access point appears on the screen, just close the scanner with control, see, and
are the number of the target access point.
And I will select a wireless interface.
So here I'm revealing all my secrets, I've used this before for this attack, therefore the configuration
has been saved, so I'll just select reset attack.
So we'll select the same interface for the fake access point.
And this time, I would like to try the MDK for method for the authentic Haitian.
So now we need to select an access point service for the rogue access point.
OK, so I'll continue with a recommended option.
So I'll select Count Patty for password verification.
In a step, Flexion has detected the hash file previously captured by the Handshake Snooper Attack.
So just select use a hash found.
So, again, I'll select Count Patti for harsh verification.
All right, Ash, verification is successful.
Now, you must be aware that, as I say, LTL s is a method of encryption used to establish a secure
connection between two points.
In this case, the two points are the captive portals web server and the target client.
Now, if you don't have a personal certificate, you may select who automatically generate one.
So just select create an SSL certificate.
Now you can select whether the captive portal web server should attempt emulating an Internet connection.
This could be useful for people that don't want to make the captive portal obvious.
The clients will connect, but will be fooled into believing that Internet access is available and it
will cause all IOPS clients and some Android clients to not show the captive portal immediately upon
connecting to the rogue network.
However, the captive portal will still show up once the clients try to access any website that makes
it.
So that means our selected disconnected option.
Now, in this step, will select a captive portal interface for the rogue network.
I'll continue with the English generic portal.
OK, so the attack begins.
And this time there are six terminals on the screen.
So the terminals above from last fluxing DHP service to give an IP address to the connected client.
Flexion host APD, so it's a service to create a rogue access point.
And Flexion Access Point authenticator that displays the authenticated clients to the access point.
And the terminal is below, from the left are Flexion DNS service, and that provides access to the
Internet by forwarding clients DNS queries.
Election Web service, and that will listen to the Web traffic of the connected client and fluxing Jammer's
service for day authentication atax.
OK, so my phone authenticated to the access point now.
And DHP service offered an IP address.
It's disconnected and reconnected again.
Cool.
So finally, Web traffic appears on the Web service.
So I'm listening to the traffic and the man in the middle attack is completed successfully.
Good job.