3 ms·
I'm being hyper-pedantic here. Wouldn't the relevant kind of pwning happen to you rather than to the site? I'm thinking something like a MITM at your local coff
by sowbug 7y ago
I'm being hyper-pedantic here. Wouldn't the relevant kind of pwning happen to you rather than to the site? I'm thinking something like a MITM at your local coffee shop's wifi or an evil employee at your work. If someone took over the machine serving example.com, HTTPS wouldn't have stopped it or helped alert anyone to it.
- roywiggins 7y agoThe point is to generate a 302 redirect, so I guess it doesn't matter what example.com is actually serving if you never see it. But the captive portal may forward you along to it after you authenticate. This doesn't do anything to prevent a MITM at all, just that if neverssl.com starts serving crap you have a nonzero chance of loading it when trying to use it to generate a redirect. If there's a local MITM you're in trouble either way.
- sowbug 7y agoThat makes sense. My one change to the workflow is that I tend to visit example.com again, one last time, after jumping through the captive-portal hoops to make sure it's all really working. Thus I do see the content.