skip to content

WPA3

WPA3 and what it fixes: SAE (Dragonfly) replacing the PSK handshake, forward secrecy per session, resistance to offline dictionary attacks, and OWE for open networks. The current standard.

on this pageshow

explore

questions

15

What does Wi-Fi Enhanced Open (OWE) change for customers of an open café guest network, and what does it leave unprotected?

level: juniorimportance: must knowfreq 32%

answer

  1. privacy from bystanders, not identity
  2. no passphrase, still encrypted
  3. each client gets its own keys
  4. unauthenticated Diffie-Hellman at association

basics

~20 s

Wi-Fi Enhanced Open (OWE, RFC 8110) gives every client its own encryption keys through an unauthenticated Diffie-Hellman exchange, so other customers cannot read its traffic off the air. It authenticates nobody and protects only the wireless hop.

solid answer

~40 s

On a plain open network every frame crosses the air unencrypted, so anyone nearby can read it. With **Wi-Fi Enhanced Open** (the Wi-Fi Alliance name for OWE, RFC 8110) the client and the access point run a Diffie-Hellman exchange while the client associates, and each client ends up with its own keys. Joining still needs no passphrase and no user action. What OWE does **not** do: it authenticates neither side, so the client cannot tell the café's access point from an impostor; it protects only the wireless hop, not the path past the access point; and it is no access control, because anyone in range can still join. That is why RFC 8110 asks clients not to show a lock icon for an OWE network.

go deeper

for a junior

Remember the two-part answer: OWE gives each client its own encryption on an open network with no passphrase, but it authenticates nobody and stops at the access point.

for a middle

Be ready to explain why a publicly posted WPA2 passphrase does not keep customers' traffic private from each other, and why OWE's per-client keys do.

for a senior

Show you can state OWE's residual risks to a venue owner precisely: no protection against an impostor access point, none past the access point, and no access control.

for a principal

Frame OWE as a cheap privacy floor for guest networks, and be clear about what it must not be sold as: authentication, consent capture or a replacement for end-to-end security.

## What an open network gives away A traditional **open** Wi-Fi network uses Open System authentication and no encryption. After association, every data frame travels over the air in the clear. Anyone within radio range can receive those frames, so web requests sent without TLS, DNS lookups and other unprotected traffic are readable by other people in the same café. Many venues try to fix this by posting a **WPA2-Personal passphrase** on a sign or menu. RFC 8110 explains why that helps less than people think. The passphrase is the same for everyone, so it gives every customer the same starting secret. Someone who knows it and observes another customer joining can compute that customer's traffic keys. The RFC calls the belief that a public passphrase protects against passive sniffing "erroneous". ## What OWE adds **Opportunistic Wireless Encryption (OWE)**, defined in RFC 8110 and certified by the Wi-Fi Alliance as **Wi-Fi Enhanced Open**, replaces open authentication with something that still feels open to the user: - The access point advertises OWE in its beacons, and the client joins without any passphrase. - During association the client and the access point exchange Diffie-Hellman public keys. Each side combines its own private key with the other's public key, so both reach the same secret while a listener who saw only the public keys cannot. - That secret becomes a **Pairwise Master Key (PMK)** unique to this client. The normal key handshake then derives the traffic keys. - Every customer therefore gets different keys. A neighbour who records the air sees encrypted frames that no other customer can decrypt. The Wi-Fi Alliance describes the result as "unauthenticated data encryption", with no public passphrases to maintain, share or manage. ## What OWE does not do OWE fixes one problem, passive listening, and is deliberately honest about the rest: 1. **It authenticates nobody.** The client has no proof of which access point it is talking to, and the access point knows nothing about the client. RFC 8110 notes that a station impersonating the access point could place itself between the client and the real network. The defence against that is real authentication, which OWE does not provide. 2. **It protects only the wireless hop.** Encryption ends where the 802.11 link ends. Traffic beyond the access point is exactly as exposed as it was before, so TLS, a VPN or other end-to-end protection is still needed. 3. **It is not access control.** Anyone in range can still join. Terms of use, time limits or a sign-in page remain the job of whatever the venue runs after association, such as a captive portal. 4. **It does not isolate clients from each other on the network.** Stopping one guest reaching another guest's device is a separate setting. ## How it looks to the user RFC 8110 recommends that clients present an OWE network like an open one, **without a lock icon**, because to the user it is still an open network that simply "provides more security behind the scenes". A lock would suggest an assurance about who runs the network that OWE cannot give. Two practical consequences follow for the operator: - A device without OWE support cannot join an OWE-only network at all. A venue whose guests still carry such devices can run **OWE transition mode**, which keeps an open network beside the OWE one and steers capable devices to the encrypted side. - For the customer, joining stays as simple as on an open network; for the operator there is no code at the counter, no password to rotate when staff leave and no sign to reprint. The Wi-Fi Alliance presents exactly this as the operator's benefit, alongside working with networks that still use a captive portal. ## Where it sits among the guest-network options | Option | Encrypted on the air | Can one customer read another's traffic? | Who is authenticated | |---|---|---|---| | Open | No | Yes, trivially | Nobody | | Open with a captive portal | No | Yes, trivially | Nobody (the portal records consent only) | | WPA2-Personal, passphrase posted publicly | Yes | Yes, for anyone who knows the passphrase and observes the join | Only "knows the passphrase", which everyone does | | OWE (Wi-Fi Enhanced Open) | Yes | No, each client has its own keys | Nobody | For a café or a conference venue, OWE removes the cheapest kind of snooping at no cost to the customer. It is a privacy improvement, not a trust or access-control mechanism, and the venue should describe it that way.

  • Why does RFC 8110 recommend that clients show an OWE network without a lock icon?
    Because OWE authenticates neither the client nor the access point. A lock suggests the user can trust who runs the network, and OWE gives no such assurance. RFC 8110 says that to a user an OWE network is the same as an open one; it only adds encryption behind the scenes, so it should be presented like an open network.
  • Once a guest network uses OWE, do guests still need HTTPS or a VPN?
    Yes. OWE protects only the wireless hop between the client and the access point. Beyond the access point, across the venue's network and the internet, traffic is as exposed as before. RFC 8110 itself says users should still use application-level security for end-to-end protection.

  • OWE proves to the customer that the access point really belongs to the café.
  • OWE encrypts traffic all the way to the website, so HTTPS no longer matters.
  • All customers on an OWE network share one key, like a posted passphrase.
  • A WPA2 passphrase printed on the wall already stops customers reading each other's traffic.
  • OWE requires customers to type a code from the counter before they can join.
open as a page

In WPA3-Personal, what does the SAE handshake do differently from WPA2-Personal's pre-shared key, and why does it matter?

level: juniorimportance: must knowfreq 46%

basics

~20 s

SAE is a password-authenticated key exchange: both sides prove they know the passphrase without sending anything a recording can test guesses against, and every run yields a fresh PMK. WPA2-Personal uses one fixed passphrase-derived PMK.

open as a page

What is WPA3-Personal transition mode, and why would a network run it while migrating a mixed fleet off WPA2-Personal?

level: juniorimportance: must knowfreq 42%

basics

~20 s

WPA3-Personal transition mode is one SSID advertising both the WPA2 PSK and the WPA3 SAE key management with PMF optional, so SAE-capable clients use SAE with PMF while older clients keep the same passphrase over PSK.

open as a page

For a WPA3-Personal SAE exchange recorded in full by an eavesdropper, what can the recording still reveal, and what can it not?

level: middleimportance: must knowfreq 34%

basics

~20 s

A recorded SAE exchange reveals metadata — MAC addresses, the group, timing — but nothing that confirms or rules out a passphrase guess, and nothing that recovers the PMK even if the passphrase leaks later.

open as a page

What does 802.11w Protected Management Frames actually protect on a WPA2 or WPA3 network, and which management frames does it leave unprotected?

level: middleimportance: must knowfreq 34%

basics

~20 s

802.11w Protected Management Frames protects robust management frames: Deauthentication, Disassociation and most Action frames, unicast under the pairwise key and group-addressed under BIP with the IGTK. Beacons without beacon protection, probes, authentication and association frames stay unprotected.

open as a page

How does OWE give each client its own keys on an open 802.11 network, and which frames carry its key exchange?

level: middleimportance: should knowfreq 20%

basics

~20 s

An OWE access point lists the OWE AKM in its RSN element. The client puts a Diffie-Hellman public key in its association request, the access point answers in the association response, and each side derives a per-client PMK for the four-way handshake.

open as a page

When a venue's guest SSID moves to OWE but keeps its captive portal for terms of use, what does each do, and in what order?

level: middleimportance: should knowfreq 16%

basics

~20 s

OWE runs first, inside 802.11 association, and encrypts the client's wireless link with its own keys. Only then does the client get an address and meet the captive portal, which records acceptance of the terms. OWE encrypts; the portal gates access.

open as a page

In SAE, what do the Commit and Confirm messages carry, in which 802.11 frames do they travel, and what still runs after them?

level: middleimportance: should knowfreq 24%

basics

~10 s

SAE Commit (group, scalar, element) and Confirm (send-confirm counter, confirm value) travel in 802.11 Authentication frames before association; they yield the PMK, and association plus the four-way handshake follow.

open as a page

On a WPA3-Personal network, how does SAE's hash-to-element differ from hunting-and-pecking, and why does 6 GHz operation insist on it?

level: seniorimportance: should knowfreq 14%

basics

~10 s

Hunting-and-pecking finds SAE's password element with a loop whose work depends on the password; hash-to-element maps the password directly with RFC 9380 hash-to-curve, without that loop. 6 GHz allows only hash-to-element.

open as a page

While a WPA3-Personal transition-mode SSID still offers PSK, what downgrade exposure remains for WPA3-capable clients, and what narrows it?

level: seniorimportance: should knowfreq 15%

basics

~20 s

A WPA3-capable client whose profile still allows PSK can end up on PSK, exposing the passphrase as WPA2 would. Transition Disable, SAE-only client profiles and a strong passphrase narrow it; for the whole SSID, only switching PSK off closes it.

open as a page

With 802.11w PMF in force, why does an unprotected Disassociation frame not end a live association, and how does the SA Query procedure resolve a real loss of state?

level: seniorimportance: should knowfreq 12%

basics

~20 s

Under PMF a station discards unprotected Deauthentication and Disassociation frames, because the real peer would protect them. SA Query then checks whether the peer still holds the keys: a protected answer keeps the association, a timeout ends it.

open as a page

Should a café chain's guest Wi-Fi move to OWE-only, run OWE transition mode, or stay open behind a captive portal, and what decides it?

level: principalimportance: should knowfreq 12%

basics

~20 s

The client fleet and the band plan decide. OWE-only encrypts everyone but strands clients without OWE support; transition mode protects capable clients and keeps the rest on an open BSS; staying open protects nobody. On 6 GHz, open is not an option.

open as a page

A security team asks when the corporate SSID can stop offering PSK and require PMF; how would you decide, and what evidence and sequence would you use?

level: principalimportance: should knowfreq 17%

basics

~20 s

Retire PSK when measured association data shows the PSK tail is small and has a home: replace, isolate or exempt those devices, harden SAE clients with Transition Disable, then set the SSID to SAE-only with PMF required.

open as a page

In OWE transition mode, how do the open BSS and the OWE BSS point at each other, and what does a client without OWE support experience?

level: seniorimportance: nice to knowfreq 10%

basics

~20 s

Each BSS advertises a Wi-Fi Alliance vendor-specific element naming the other's BSSID and SSID, and the OWE BSS is normally hidden. OWE-capable clients follow the pointer and join encrypted; clients without OWE support join the open BSS unencrypted, as before.

open as a page

Your team must set SAE defaults for a router firmware line after the 2019 Dragonblood findings — how do you choose the PWE mode, groups and patch policy?

level: principalimportance: nice to knowfreq 9%

basics

~20 s

Treat Dragonblood as an implementation lesson: ship patched, constant-time SAE code, enable hash-to-element (both methods on 2.4/5 GHz unless the fleet allows H2E-only, H2E on 6 GHz), keep group 19 as the default, and commit to security updates.

open as a page