Faulty entered bridges lead to broken prefs.js -> browser does show connect button
Summary
When entering multiple bridges in the "Provide a bridge" section and having a line-break inside a bridge line by error, the next time starting the Tor Browser won't show a connect button, due to erroneous prefs.js entries and in the current session Tor Browser connects without using bridges if possible.
Steps to reproduce:
- Enter details of 3 bridges in "Provide a bridge" section [about:preferences#tor]
- Add a line-break (hit enter) between
PORT
andFINGERPRINT
Bridge obfs4 <IP ADDRESS>:<PORT> <FINGERPRINT> cert=<CERTIFICATE> iat-mode=0
- Use the browser once (will work) and quit it
- Start the browser again.
- The browser won't show the connect button any more due to faulty entries in prefs.js user_pref("torbrowser.settings.bridges.bridge_strings
What is the current bug behavior?
When entering bridge details no error shows up, it's hard to notice, because of long bridge lines in a small box and the problem manifests when starting next time plus Tor connects without bridges if possible in current session
What is the expected behavior?
Format checking while entry (would prevent connection without bridges) and/or removal of faulty torbrowser.settings.bridges.bridge_strings from prefs.js at startup
user_pref("torbrowser.settings.bridges.bridge_strings. […]
Environment
Linux, Tor Browser 11.0.2 from torproject.org, No installation, just extract an run ./start-tor-browser from command-line.