Feature #5412
Improve fingerprint of the Unsafe Browser
0%
Description
{{toc}}
Next steps
Avoid Tails-specific DNS requests
One can see e.g. with Wireshark that the Unsafe Browser sends DNS requests for amnesia
and tails.boum.org
on the network. This should clearly not happen.
Next thing to do: research why this happens.
Improve fingerprint of the request made to get the captive portal
For the WiFi hotspot and probably ISP, the recommended way of using the Unsafe browser only to login in the portal and then use only Tor is fingerprintable.
What clearnet request do people do to get the captive portal?
Next thing to do: research how we can improve the network fingerprint of that principal usecase.
Done
As a first step, we wanted to make the Unsafe Browser look like a default Debian Iceweasel ESR. This was done by removing all add-ons.
Subtasks
Related issues
Related to Tails - Feature #5555: Torbrowser patches vs. Unsafe browser | Confirmed | ||
Related to Tails - Feature #10491: Redesign the network configuration and startup | Confirmed | 2014-06-22 |
History
#1 Updated by BitingBird 2014-06-09 10:35:08
- Subject changed from improve fingerprint of the Unsafe Browser to Improve fingerprint of the Unsafe Browser
- Description updated
- Category set to 176
- Starter set to No
#2 Updated by BitingBird 2014-06-21 15:44:47
- related to Feature #5555: Torbrowser patches vs. Unsafe browser added
#3 Updated by intrigeri 2018-08-19 11:52:35
- Status changed from Confirmed to Rejected
I say let’s not spend time on this and instead focus on Feature #10491.
#4 Updated by intrigeri 2018-08-19 11:52:39
- related to Feature #10491: Redesign the network configuration and startup added