Actually, I was told that Debarshi committed a fix for the TLS error in captive portal just last week and has pushed a fix for it. Christian ----- Original Message ----- > From: "Michael Catanzaro" <mcatanzaro@xxxxxxxxx> > To: "Development discussions related to Fedora" <devel@xxxxxxxxxxxxxxxxxxxxxxx> > Sent: Monday, December 5, 2016 1:16:08 PM > Subject: Re: Fedora captive portal page changed output :( > > On Mon, 2016-12-05 at 09:59 -0500, Paul Wouters wrote: > > Right now, the situation leads me to having to close the gnome window > > which only displays "TLS certificate invalid" or some text like that, > > and still use my firefox and a new tab/window to get through the > > captive portal. > > Good point. I guess ignoring TLS errors might mean better overall > safety here. :/ At least for the next couple of years. > > Ideally we would fix this bug before making any changes to that: > > https://bugzilla.gnome.org/show_bug.cgi?id=749197 > > It's assigned to me, which means I'll do it eventually for some value > of eventually; help always welcome.... > > > In which case we are exposing the full firefox with > > all my privacy settings and cookies to the captive portal, instead of > > (what I hope to be) some "private window" gnome web browser that has > > no access to any of my personal data. So I'd rather see the gnome > > window ignoring the TLS error and proceeding. > > Unfortunately you hoped too much, looks like it's using default WebKit > data directories. I think it probably can't read your cookies from > other apps as cookies work a bit differently, but it is getting > everything else from the default WebKit data dirs. It really should use > a private data dir, which is very easy to fix; then that would avoid > any concerns about caching as well. Modified bug report: > > https://bugzilla.gnome.org/show_bug.cgi?id=775639 > > BTW, full portal helper bug list: > > https://bugzilla.gnome.org/buglist.cgi?quicksearch=component:portal-helper%20product:"gnome-shell"%20&list_id=173288 > > Michael > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
