Skip to content

Persistent Bridges, iteration 2: use settings from tca.conf on first start

intrigeri requested to merge 5461-persistent-tor-bridges-iteration-2+force-all-tests into devel

Based on the first iteration: !533 (merged).

Here as well, changes are happening under the hood: our doc and UI won't put a user into the situation where tca.conf is non-empty when they start Tor Connection for the first time.

To test this code in the (simulated) situation where it's relevant:

  1. Start Tails with an admin password

  2. Configure some bridges

  3. Wait for Tor Connection to report success

  4. Close Tor Connection

  5. As root, pretend we just started Tails: rm -rf /run/tca/ && systemctl stop tor@default && find /var/lib/tor/ -mindepth 1 -delete && echo DisableNetwork 1 >> /etc/tor/torrc && systemctl start tor@default

  6. Start Tor Connection from the Overview or Applications menu

    Expected behavior:

    • At the consent step, if you choose "automatically connect", then the "use bridges" checkbox is enabled.
    • At the bridges config step, the bridges you previously used are pre-configured.
    • torrc has those bridges configured

The automated test suite validates behavior in some other cases in a more lower level way, by checking the contents of tca.conf. !539 (merged) will add tests that validate the whole journey with a reboot and all.

refs #5461 (closed)

Edited by intrigeri

Merge request reports