News for hackers. Stuff that matters.
Re:NeverSSL by saghm on Saturday November 02, 2019 @06:34PM (#21430579)
On some public wifi networks, you need to load a captive portal page and hit a button (usually to accept terms and conditions) before network to route you to any actual sites. The network often enforces this by redirecting you to that page whenever you try to visit something else. However, this doesn't occur properly when accessing a page with HTTPS. The easiest way to to directly to to the captive portal is to try to go to a non-HTTPS site, but fewer and fewer sites provide this (for obvious securityv reasons). The purpose of this site is to provide an easy-to-remember domain that the owner guarantees will never use HTTPS so that users of such networks can type it in as a way to load the captive portal. I've used it a number of times when using wifi on Amtrak trains.
Re:NeverSSL by wilg on Saturday November 02, 2019 @06:44PM (#21430641)
Apple devices try to go to http://captive.apple.com/ for this purpose.
Re:NeverSSL by _bxg1 on Saturday November 02, 2019 @07:29PM (#21430863)
Thanks for the explanation - I've definitely encountered that situation. Do you know why it works that way?
Re:NeverSSL by manigandham on Saturday November 02, 2019 @07:40PM (#21430893)
Captive portals require intercepting and redirecting your HTTP request. You can't do that with HTTPS because it's encrypted. Most sites now automatically redirect to HTTPS and are cached that way by browsers so it's hard to find a HTTP-only site that will get redirected on these networks.
Re:NeverSSL by MrStonedOne on Saturday November 02, 2019 @08:35PM (#21431172)
Websites can tell browsers to never connect to them via unsecured channels (hsts/hsts preload), in a secured channel the browser validates the server's encryption certificate is authorized to encrypt traffic for that domain, so the wifi network can not intercept it to serve up the captive porter.