News for hackers. Stuff that matters.
Re:Chrome 68 will mark all HTTP sites as “not secure” by chainsaw10 on Thursday February 08, 2018 @11:33PM (#16337907)
> log in with some criteria more than just a username/password

The problem there is that captive portals don't add any extra link-layer security. The network is open, so literally anyone can sniff packets.

It's uncommon, but a network using WPA2-Enterprise and user/pass uses different keys for each person (not sure if per device or per user), so you don't have to trust everyone in the room.

Re:Chrome 68 will mark all HTTP sites as “not secure” by fyfy18 on Friday February 09, 2018 @12:05AM (#16338021)
Most portals I use intercept your request to a HTTP site and redirect you to their logic form which is served over HTTPS.
Re:Chrome 68 will mark all HTTP sites as “not secure” by icebraining on Friday February 09, 2018 @01:25AM (#16338324)
Yes, but after authentication, all traffic can be sniffed - including unencrypted connections.
Re:Chrome 68 will mark all HTTP sites as “not secure” by ori_b on Friday February 09, 2018 @01:46AM (#16338411)
How is this different from the case without a captive portal, again?
Re:Chrome 68 will mark all HTTP sites as “not secure” by icebraining on Friday February 09, 2018 @02:00AM (#16338457)
Using WPA-Enterprise, each connection is encrypted separately, eliminating that hole.
Re:Chrome 68 will mark all HTTP sites as “not secure” by tinus_hn on Friday February 09, 2018 @07:13AM (#16339615)
Now you don’t have to trust the other customers, only the bar you’re at, their ISP and a million other parties between you and the site you’re visiting.
Re:Chrome 68 will mark all HTTP sites as “not secure” by icebraining on Friday February 09, 2018 @07:39AM (#16339730)
That's a reasonable point, but I'm speaking from the perspective of the bar owner - I feel I have a duty to provide better security even if the patrons have no reason to trust me.
Re:Chrome 68 will mark all HTTP sites as “not secure” by tinus_hn on Friday February 09, 2018 @08:05AM (#16339868)
Like a bar is going to run account administration.. at most they’re going to set a proper password with WPA2-PSK which provides protection against outsiders. But it can’t provide protection against an active attacker that has the password.
Re:Chrome 68 will mark all HTTP sites as “not secure” by fulafel on Friday February 09, 2018 @10:52AM (#16341074)
You could have a wifi access product that used a voucher system. The code could be on the bar receipt.
Re:Chrome 68 will mark all HTTP sites as “not secure” by icebraining on Friday February 09, 2018 @08:08AM (#16339882)
They're probably also not putting up a captive portal, so what's your point?
Re:Chrome 68 will mark all HTTP sites as “not secure” by ori_b on Friday February 09, 2018 @02:29AM (#16338549)
Using WPA-Enterprise, as I understand it, requires devices to be preconfigured to authenticate with the radius server, which makes it a non-starter for the kinds of networks that use a captive portal.
Re:Chrome 68 will mark all HTTP sites as “not secure” by icebraining on Friday February 09, 2018 @03:34AM (#16338769)
No, there's no preconfiguration needed, it's just a username/password account. You choose the network, then the OS asks you for your user/pass, then you're connected.

It's the router that connects to the RADIUS server, not the device directly. And some routers have one embedded, so you don't even need to configure that, it "just works".

Re:Chrome 68 will mark all HTTP sites as “not secure” by lorenzhs on Friday February 09, 2018 @11:45AM (#16341663)
Wouldn't it be nice if there was an encryption mode for Wifi that ensures integrity without requiring authentication? At CCC events, the workaround is to have a WPA2-Enterprise network that accepts every username/password combination, but that's going to be hard to explain to non-technical users.

I think WPA3 is going to support this use case.