Easy import/export of state file.
Users of tails that do not use persistence are at greater risk of correlation attacks due to fast node cycling. This could be prevented by creating a VERY simple mechanism that allows a user to import and subsequently export their state file. A little GUI that allows the user to browse for their state file and apply it to tor's data directory. When the user presses the power icon with the intent of shitting down or restarting, an option to export is displayed.
This is purely speculation but I believe at least half of tails users use it in an amnesic way as originally intended and supported by the acronyms' translation. Safeguarding these people is IMO reason enough to implement this.
#2 Updated by Tonda over 3 years ago
Fast node cycling = being assigned a new guard every time you boot up tails unless persistence is enabled.
State file = the file that holds the data about your selected guard node among other config info.
I propose that a simple import/export mechanism be created to allow users to keep their guard nodes for extended periods. For usb users, Tails could read the state file from the root of the usb drive and report to the user that it has been imported. Otherwise it could prompt/suggest to import the state file during the greeter or before Tor attempts to bootstrap.
Hope this helps! :)