5 ms·
The problem I've run into with public key pinning is captive portals. Mobile operating systems or browsers need to provide a better user experience for captive
by cpeterso 12y ago
The problem I've run into with public key pinning is captive portals. Mobile operating systems or browsers need to provide a better user experience for captive portals.
- nandhp 12y agoMy solution to that is to open http://example.com/ http://example.com/ (instead of, e.g. Google) after connecting to Wi-Fi. It doesn't use SSL (so it works) and I have little use for it the rest of the time (so if the Firefox DNS cache gets messed up, it doesn't matter).
- kijin 12y agoDon't captive portals already have a problem with every HTTPS website? I don't see why PK pinning would cause any problem that doesn't already exist.
- illumen 12y agoYeah, many captive portals do have a problem with HTTPS. From my experience in 50+ hotels in the last years.
- kijin 12y agoWhich is not surprising at all, since the whole point of HTTPS is to prevent anyone other than Google from displaying a valid web page at https://www.google.com/ https://www.google.com/ If a captive portal is able to display a valid web page when you try to visit an HTTPS website, that would be a serious red flag.
- giovannibajo1 12y agoiOS have had good user experience for captive portals since a long time (iOS 3 I think), and also Mac OSX. They automatically detect when a captive portal is present by doing a background connection to some Apple-owned property and trying to download a small text file; if it fails for any reason, they bring up a modal panel showing the captive portal and letting the user login; then, they detect when the Internet access is active and close the panel (or, lately, let the user close the panel with a "Finish" button). What's more important is that the whole operating system / applications are not given the signal "network is on" until the whole process is finished, so you don't get one dozen of failures from applications that try to refresh in background and can't access their backend servers. This said, I really hate the fact that the WiFi alliance has left us in this very sad state. Like many similar committees, they move too slowly; captive portals arose from a real-world problem that wasn't solved by the WiFi standard, so people had to come up with weird DNS/HTTP interceptions that fail in so many regards it's not even funny. If there's somebody to blame, it's not operating systems for not adding weird heuristics like Apple did, but Wifi Alliance for not bringing to the market a good solution for handling hotspots soon enough.
- khc 12y agoI've never used iOS so I didn't know about it does this, but I've always wondered why Android didn't do the same thing.
- quentinp 12y agoIt does since 4.0 at least: http://android.stackexchange.com/questions/45629/what-android-versions-have-captive-wifi-detection http://android.stackexchange.com/questions/45629/what-androi...
- khc 12y agoit has a notification telling the user that they need to sign on, but it also tells other applications that a wifi connection is available, which causes all of them to try to sync.
- mrottenkolber 12y agoApple customers, where phoning home on every network connection is good UX. What is wrong with you people? I had this behaviour crash a captive portal daemon once, was fun tracking down the owner of the device in question in the building. "CapDaemon crashed, request came from around room A2.011!", "Let's get him before he's gone!", "Hey, Mr., do you own an Iphone or I pad? Yes? Please come with us. We need to have a debug session with you."
- giovannibajo1 12y agoIt is good UX. For privacy concerns, it's already phoning home on every network connection for push notification registration (at the very least), so your objection is moot to me. To handle this less centrally, you would need a distributed list of URLs to be used for captive portal checks, with servers handled by different entities, and each device selecting one at random from the list. This wouldn't change the UX though. For your other remark, if the captive portal crashes for a standard HTTP GET to a normal URL, you can't really blame this on anybody else but the captive portal developers.
- AlyssaRowan 12y agoWrong way round. Captive portals need to provide a better user experience for browsers that doesn't involve an MITM! See 802.11u: no excuse for not using it.
- DCKing 12y agoExcuses for not using 802.11u it do exist: client support simply isn't there. iOS only supports it since 7, Android doesn't support it (and will not generally for many years even if Android L does include it), Windows doesn't support it generally, OS X doesn't appear to have support for it, the list probably goes on. It will take 5 years at minimum before hotspot owners will provide this functionality, as there needs to be major client adoption first. Just because your solution is problematic doesn't however mean that your point is not correct. The problem here is indeed with captive portals.