On Comcast’s open wifi deployment we make our best attempt to upgrade security upon authentication on our captive portal page. After a successful login, we have unique flows for each operating system that deliver secure profiles to the client for installation. This is very hard to maintain and QA test as the operating systems’ sandbox gets more strict on each iteration. I do not know if its this is a problem we need to address immediately but it s something we need to think about as we transition into secure phy layers.
-- Alexander Roscoe Comcast - Wireless Engineer Phone 215.286.7283 Cell 215.609.2691 On 4/4/16, 5:42 PM, "Martin Thomson" <[email protected]> wrote: >On 4 April 2016 at 15:43, Michael Richardson <[email protected]> >wrote: >> So, a URL-scheme that could contain a pointer to the other SSID. > >You mean something I could put on my webpage that, if clicked, would >cause a device to connect to the identified SSID? That might be less >than good. I thought that Adam was talking about plain ol' text, but >maybe he can confirm. > >> > I¹m very happy to contribute towards an industry survey and will >>keep >> > following the discussion in the mailing list. >> >> I'm super-happy to have you on the list. > >Likewise. It's good to have this sort of perspective. > >_______________________________________________ >Captive-portals mailing list >[email protected] >https://www.ietf.org/mailman/listinfo/captive-portals _______________________________________________ Captive-portals mailing list [email protected] https://www.ietf.org/mailman/listinfo/captive-portals
