Re:Hotel WiFi JavaScript Injection (2012)
by bcye on Friday April 26, 2024 @01:41PM
(#40172117)
What's the downside of HTTPS that you'd want to remove the encryption feature?
[ Parent
| on HN ]
Re:Hotel WiFi JavaScript Injection (2012)
by droopybuns on Friday April 26, 2024 @03:55PM
(#40173478)
Captive portal detection is endlessly buggy.
That's explicitly why captive portal detection does not use HTTPS. If your OS of choice fails to detect captive portal (or doesn't implement detection), and you have the ability to visit a website, you can visit example.com to get into the captive portal.
The really annoying part is when a device (cough, Switch at launch) doesn't have portal detection nor a web browser, making it useless on hotel wifi.
Re:Hotel WiFi JavaScript Injection (2012)
by netsharc on Saturday April 27, 2024 @01:45PM
(#40181931)
I guess one could bring a laptop, spoof the Switch's WiFi MAC on the laptop and use it to login through that portal, and then disconnecting, and connect the "authorized" Switch. And make sure the Switch doesn't have "randomize MAC" like on Android/iOS.
But that's a huge workaround for many.