Unsafe browser cannot login to captive portals since 1.2 RC
Originally created by @emmapeel on #8088 (Redmine)
Two users have reported with whisperBack that captive portals where they logged in with unsafe browser from Tails 1.1.2 cannot connect with Tails 1.2 rc.
One found a very interesting detail:
This location is one I can connect to the wireless with every tails version from 1.1.2 and backwards.
At this location I can ping the wifi access point, my IP and a redirection IP. Yes, this particular site is really spooky. I suspect but don’t know for sure but I would guess this site grabs all sorts of customer data. Why? Because it can. Tails is really handy here. But the new 1.2 rc unsafe browser will not play with it.
Below is the failed tor log that I saved. It looks to me like the Unsafe is really trying to connect as a typical tor connection.
10/12/2014 16:46:58.932 [NOTICE] New control connection opened from 127.0.0.1.
10/12/2014 16:46:59.924 [NOTICE] New control connection opened from 127.0.0.1.
10/12/2014 16:47:00.938 [NOTICE] New control connection opened from 127.0.0.1.
10/12/2014 16:47:01.951 [NOTICE] New control connection opened from 127.0.0.1.
10/12/2014 16:47:02.965 [NOTICE] New control connection opened from 127.0.0.1.
10/12/2014 16:47:03.979 [NOTICE] New control connection opened from 127.0.0.1.
10/12/2014 16:47:04.991 [NOTICE] New control connection opened from 127.0.0.1.
10/12/2014 16:47:06.500 [NOTICE] New control connection opened from 127.0.0.1.
10/12/2014 16:47:07.190 [NOTICE] New control connection opened from 127.0.0.1.
10/12/2014 16:47:08.330 [NOTICE] New control connection opened from 127.0.0.1.
10/12/2014 16:47:08.940 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
10/12/2014 16:47:08.940 [NOTICE] Caching new entry debian-tor for debian-tor
10/12/2014 16:47:08.940 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
10/12/2014 16:47:08.940 [NOTICE] Caching new entry debian-tor for debian-tor
10/12/2014 16:47:08.940 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
10/12/2014 16:47:08.940 [NOTICE] Caching new entry debian-tor for debian-tor
10/12/2014 16:47:08.950 [NOTICE] Opening Socks listener on 127.0.0.1:9050
10/12/2014 16:47:08.950 [NOTICE] Opening Socks listener on 127.0.0.1:9061
10/12/2014 16:47:08.950 [NOTICE] Opening Socks listener on 127.0.0.1:9062
10/12/2014 16:47:08.950 [NOTICE] Opening Socks listener on 127.0.0.1:9150
10/12/2014 16:47:08.950 [NOTICE] Opening DNS listener on 127.0.0.1:5353
10/12/2014 16:47:08.950 [NOTICE] Opening Transparent pf/netfilter listener on 127.0.0.1:9040
10/12/2014 16:47:08.950 [NOTICE] Caching new entry debian-tor for debian-tor
10/12/2014 16:47:08.950 [NOTICE] Renaming old configuration file to "/etc/tor/torrc.orig.1"
10/12/2014 16:47:08.712 [NOTICE] Bootstrapped 5%: Connecting to directory server
10/12/2014 16:47:08.718 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server
10/12/2014 16:47:09.460 [NOTICE] New control connection opened from 127.0.0.1.
10/12/2014 16:47:15.940 [WARN] Tried connecting to router at [IP stripped by emmapeel]:443, but identity key was not as expected: wanted [hash stripped by emmapeel] but got [hash stripped by emmapeel].
10/12/2014 16:49:12.151 [WARN] Tried connecting to router at [IP stripped by emmapeel]:443, but identity key was not as expected: wanted [hash stripped by emmapeel] but got [hash stripped by emmapeel].
Below is the message I get when I close the unsafe browser down.
(( Unable to save Tor settings.
Please ensure that Tor is running.))
=
also another report, though user is not so tech savvy, is available. I can not test this right now, hopefully someone can reproduce it?