Tails

#1 Updated by intrigeri 2014-09-16 10:16:13

> Is not fixed when restarting the Unsafe browser neither.

This is very surprising to me, and may indicate a more severe bug.
How exactly can you reproduce this?

> I think that this can be a very annoying usability issue.

Agreed… in corner cases.

> Let’s say that you are in an airport and want to try out several captive portals. You should restart Tails every time?

I think that having to restart the Unsafe Browser only would be acceptable. Having to restart Tails entirely is really problematic, indeed.

#3 Updated by emmapeel 2014-09-17 13:54:00

I left some people without Internet for a while, and could reproduce the bug.

Restarting the Unsafe Browser doesn’t help.

#4 Updated by intrigeri 2014-09-17 14:25:08

emmapeel wrote:
> Restarting the Unsafe Browser doesn’t help.

Again, how exactly can I reproduce this?

#5 Updated by emmapeel 2014-09-18 00:41:12

Well, if you have two different networks available with internal nameservers you can reproduce it with:

1. Connect to a network with a given resolver.
2. Start the Unsafe Browser.
3. Connect to a different network with another resolver.
4. Load a page in the Unsafe Browser. Not found
5. Restart Unsafe Browser
6. Load a page in the Unsafe Browser. Not found

#6 Updated by BitingBird 2014-09-18 03:00:25

The unsafe browser is not meant to surf the internet, only connect (Feature #7774). Is the safe browser able to connect ?

#7 Updated by Anonymous 2014-09-18 07:25:30

I could not reproduce this behaviour.

#8 Updated by intrigeri 2014-09-18 09:16:48

> The unsafe browser is not meant to surf the internet, only connect (Feature #7774).

Indeed. And the main use case described in this ticket is about connecting, e.g. trying out different Wi-Fi hotspots in a airport.

#9 Updated by sajolida 2014-09-18 14:20:28

I tried this. If visit something.com, then change network and visit somethingelse.com I get an error.

But if I restart the unsafe browser and visit again somethingelse.com it works.

So, from what I see, restarting the unsafe browser is enough to get a working DNS resolver.

If it is technically difficult to update the DNS resolver without restartin the unsafe browser, I would be find with adding a note about that in the documentation.

#10 Updated by intrigeri 2014-09-19 08:07:07

> If it is technically difficult to update the DNS resolver without restartin the
> unsafe browser, I would be find with adding a note about that in the documentation.

I think it might be quite easy to update resolv.conf in the unsafe
browser chroot. Things might get a bit more hairy when we migrate it
to a stronger sandbox, though.