What does Wi-Fi Enhanced Open (OWE) change for customers of an open café guest network, and what does it leave unprotected?
answer
- privacy from bystanders, not identity
- no passphrase, still encrypted
- each client gets its own keys
- unauthenticated Diffie-Hellman at association
basics
~20 sWi-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 sOn 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
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.
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.
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.
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.