News for hackers. Stuff that matters.

A comment on Chrome 68 will mark all HTTP sites as “not secure”. Parent comment

Re:Chrome 68 will mark all HTTP sites as “not secure” by fulafel on Friday February 09, 2018 @12:13AM (#16338050)
Wifi has supported that kind of login for ages (15 years?) at the protocol level, without fucking with the traffic in a MITM fashion. OS support was there already for XP and iOS 2.0.

https://en.m.wikipedia.org/wiki/IEEE_802.1X

[ Parent | on HN ]
Re:Chrome 68 will mark all HTTP sites as “not secure” by throwaway2048 on Friday February 09, 2018 @02:56AM (#16338647)
except there is no provisions for UI indications whatsoever, not even what login you should be using, or what you are logging into, or why.
[ Parent | on HN ]
Re:Chrome 68 will mark all HTTP sites as “not secure” by dingaling on Friday February 09, 2018 @06:23AM (#16339408)
Every hotel room in which I've stayed has a placard on the table with the BSSID name, userID and password for the portal login.

It would be identical with 802.1X. The only difference in the UI flow is that the authentication prompt is generated by the OS, not on some HTTP page that I only remember about when I wonder why my VPN isn't coming-up.

[ Parent | on HN ]
Re:Chrome 68 will mark all HTTP sites as “not secure” by endless1234 on Friday February 09, 2018 @03:57AM (#16338840)
So why don't captive portals at e.g. cafés use 802.1X? Are they just stupid and don't know it exists, or is it really user unfriendly in that setting?
[ Parent | on HN ]