kernel.panic.0x11 · field guide

How I'd hack your WiFi4 parts

You commented WIFI or HANDSHAKE on the series. Here is the whole chain in one place: how each step actually works, and the exact settings that shut every one of them down.

Part 1

Recon: I find you without connecting

I never touch your network to start. I put one adapter into monitor mode, which just listens to the radio. From across the street I can see every network nearby, including hidden ones, the channel each runs on, and every device already connected to them.

# passive listen, nothing sent BSSID PWR ENC ESSID CLIENTS AA:BB:..:11 -42 WPA HomeNet_2G 3 CC:DD:..:22 -55 WPA2 <hidden> 1 # sorted by weakest encryption -> that one goes to the top

Then I sort by how easy each one is. Weak or old encryption goes to the top of the list, and that network never knew it was being profiled.

Why it matters

You cannot stop a stranger from seeing that your network exists; radio is broadcast. What you control is being the easy target at the top of the list. That comes down to your encryption and passphrase, which Parts 3 and 4 settle.

Part 2

The handshake: I grab your key exchange out of the air

When a device joins WiFi, it performs a four-way handshake, a short cryptographic exchange that proves it knows the password without ever sending the password. I want that exchange.

So I send a single deauth frame, a forged "disconnect" that looks like it came from your router. Every connected device drops for a fraction of a second and immediately reconnects. That reconnect replays the handshake, and my adapter captures the packets out of the air. You never notice.

# one forged frame, then just listen [deauth] -> client kicked for ~1ms [client] reconnecting... [EAPOL] 4-way handshake captured -> saved to disk # I now have the hash. I can leave. Range no longer matters.

Why it matters

The forged-deauth trick is the linchpin, and it is exactly what modern protections kill (see Defense). Once I have the captured handshake, the rest happens offline on my own machine, days later, nowhere near you.

Part 3

Cracking: I guess the password offline

The password itself was never sent over the air, so I cannot "read" it. I have to guess it. I load the captured handshake into a cracker like Hashcat and throw a GPU and a giant wordlist at it, thousands of parallel guesses per moment, until one produces the same hash.

hashcat -m 22000 capture.hc22000 wordlist.txt # common passphrase? seconds. # pet name + birth year? minutes. # 20 random characters? longer than the universe has left.

This is the whole game. A weak or common passphrase falls in seconds because it is already in the wordlist. A long random one is not in any wordlist, and brute force against strong WPA2 would take a modern machine on the order of thousands of years.

Why it matters

Everything before this only mattered because most passwords are guessable. Your passphrase is the single biggest lever you own. Length beats cleverness.

Bonus

The evil twin: I become the network you trust

On open public WiFi there is no handshake to steal, so I do something simpler. Your phone constantly shouts the names of networks it has joined before, looking to reconnect. I clone one, "Starbucks WiFi", say, and broadcast it. Your device sees a trusted name and just connects. Now every request runs through my laptop first.

Why it matters

This one is pure convenience-exploitation, and the fixes are small habit changes below.

Part 4 · the point of all this

How to shut every step down

You do not need to be un-hackable. You need to not be the easy one at the top of the list. Do these and the chain above breaks at multiple points.

Do the first three and you are no longer worth the time. That is the whole goal: raise the cost until the attacker moves on.

Part 4 (the deep defense walkthrough) drops next.

Drop your email and I'll send the next one when it's live. One message, no spam, and you can reply to it. Or just follow on Instagram.