Feature #7046
Design scenario and features for a Tails Installer package in Debian
0%
Description
It might simplify the installation workflow to have a Tails Installer package in Debian (eventually also Ubuntu) for downloading, verifying, and installing the ISO.
This could be a use scenario:
1. The user installs the tails-installer package.
2. The user starts Tails Installer.
3. Tails Installer downloads the latest ISO image.
4. Tails Installer verifies the ISO first with the signing key from the package.
5. Tails Installer also tries to verify the ISO using the user’s keyring.
6. Tails Installer compares both results and warn the user if they differ.
7. Tails Installer installs the ISO image onto a USB stick.
8. The user restarts on a fully operational Tails and is happy.
The user might, either before, either after using the Installer, do
stronger verification on the signing key in her own keyring. For example
you might have a personal trust path or a local signature in your
personal keyring. But we shouldn’t import automatically new keys in the user’s keyring. On the other hand, it might always be a good thing to verify the ISO with a key included in the package, probably using a dedicated keyring.
Subtasks
Related issues
|
Blocks Tails - |
Resolved | 2015-05-12 |
History
#1 Updated by BitingBird 2014-04-09 19:31:48
- Description updated
#2 Updated by intrigeri 2014-07-12 10:34:35
- related to
Feature #7544: Have a multiplatform Installer added
#3 Updated by BitingBird 2015-01-03 05:14:33
The scenario looks good to me. What is the research left to be done ?
#4 Updated by intrigeri 2015-01-03 10:43:07
> The scenario looks good to me. What is the research left to be done ?
E.g. upgrades are not dealt with by the single scenario above.
Also, I’m not convinced by “Tails Installer compares both results and warn the user if they differ”.
#5 Updated by sajolida 2015-01-03 18:44:52
I’ll keep this ticket in mind for our UX sprint in February. That should be considered in the broad picture of “getting started with Tails” (depending on your originating OS, prefered media, etc.)
#6 Updated by BitingBird 2015-01-04 19:03:21
- Affected tool set to Installer
#7 Updated by intrigeri 2015-01-06 13:49:42
- related to deleted (
Feature #7544: Have a multiplatform Installer
#8 Updated by intrigeri 2015-01-06 13:49:55
- Parent task set to
Feature #8549
#9 Updated by intrigeri 2015-01-06 13:59:45
- blocks
Feature #8556: Make Tails Installer work fine outside of Tails added
#10 Updated by intrigeri 2015-01-06 14:48:27
- blocks #8538 added
#11 Updated by bertagaz 2015-01-06 18:30:04
This might be solved by having step 7 diverge if the USB stick already contains a Tails install. The user would be prompted to know whether she wants to upgrade it.
Or if we keep the current interface, the user would choose between “clone and install” or “clone and upgrade”, depending on what she wants to do.
#12 Updated by intrigeri 2015-01-07 11:32:01
bertagaz wrote:
> Or if we keep the current interface, the user would choose between “clone and install” or “clone and upgrade”, depending on what she wants to do.
I don’t see why Tails Installer in Debian should display any option that’s about cloning.
#13 Updated by sajolida 2015-01-07 13:02:54
- Assignee set to tchou
#14 Updated by sajolida 2015-01-09 14:56:36
- Assignee changed from tchou to sajolida
#15 Updated by sajolida 2015-02-03 17:10:04
- Status changed from Confirmed to In Progress
#16 Updated by sajolida 2015-02-05 21:23:16
- Priority changed from Normal to Elevated
#17 Updated by sajolida 2015-02-20 19:23:03
- Status changed from In Progress to Resolved
- Assignee deleted (
sajolida) - Blueprint set to https://tails.boum.org/blueprint/bootstrapping/installer/
Objectives for 2015 were clarified and approved on https://mailman.boum.org/pipermail/tails-dev/2015-February/008059.html. See blueprint https://tails.boum.org/blueprint/bootstrapping/installer/.