CyberCertPrepMobile Security FundamentalsMobile ConnectivityEASYFree question
Scenario
An iPhone user at an international airport connects to a network named "Airport_Free_WiFi." A captive portal page appears asking them to log in with their Google or Facebook account to gain internet access. The URL bar shows an HTTP address.
A user connects their iPhone to free airport Wi-Fi. The captive portal page asks them to "log in with Google" to get access. The URL in the captive portal browser shows http://wifi-login.airport.com. What attack should the user be concerned about?
- A.This is ordinary captive portal behavior and the plain HTTP address is expected (the portal has to answer before the handset has any route to a certificate authority); social login is the standard identity method airports use for their guest networks. The user can proceed safely.
- B.This is likely a phishing captive portal designed to steal OAuth tokens or Google credentials; the HTTP (not HTTPS) URL means the page has no TLS protection and credentials entered are sent in plaintext over the network.
- C.