- https://tor.stackexchange.com/questions/698/tracking-user-location-using-entry-guards (http://www.webcitation.org/6RTwwSWvw)
- https://tor.stackexchange.com/questions/636/is-it-dangerous-to-use-tails-without-persistent-entry-guards (http://www.webcitation.org/6RTwx8bil)
- Support more stable guards for live CDs: https://trac.torproject.org/projects/tor/ticket/2653
Number of entry guards was reduced to 1 since then. (As per changelog.)
- https://blog.torproject.org/blog/tor-weekly-news-%E2%80%94-june-17th-2015#A_persistent_Tor_state_for_Tails section A persistent Tor state for Tails?
- Under the new situation of reduced number of default entry guards, ask the above questions again to see if situation has changed.
Documentation could explain how to stop the Tor service; wipe Tor's data dir; start Tor service; connect.
Editing /etc/tor/torrc by adding the following could do the trick.
After every reboot, Tor would use new entry guards. Maybe extra AppArmor rules would be required.