Open the Unsafe Browser from Tor Connection
Blocked by #18020 (closed)
TCA has a shortcut to open the unsafe browser when the connection is failing.
Right now, it just calls the unsafe-browser
executable, so if user hasn't selected enabling the Unsafe Browser at the greeter, this is not available.
Shall we make TCA an exception to open the unsafe browser? This has several security implications, but has clear UX advantages. So... let's discuss!
This would be useful to:
- Replace Moat by a link to bridges.torproject.org when autoconfig
- Log in through captive portals
User research findings
During #18762 (closed),
- 3 participants out of 4 failed to sign in to the network. I think that opening the Unsafe Browser from Tor Connection more easily would have helped them all a lot.
- P1 and P4 restarted Tails but didn't understand that they had to enable it in the Welcome Screen.

