sandbox
Size: 5435
Comment:
|
Size: 6801
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 3: | Line 3: |
#title Full System Encryption with Manual Control | #title Full System Encryption with Extras |
Line 25: | Line 25: |
As LVM is used, you can also use snapshots. This advanced topic is not covered here, but it is mentioned in the partitioning section. | The following advanced features are available, but are not covered in this process. * Snapshot: Take a snapshot of your system, e.g. before doing a risky upgrade, and easily roll back if required. * Boot from external USB: Put the two small unencrypted parts of the boot system (the bootloader and the ESP) onto a USB stick, so the computer cannot be started without the USB stick. Nothing unencrypted is left on the computer, except for what comes built in with the hardware and any existing system such as Windows. |
Line 31: | Line 35: |
It is important for you to know the possible limitations (described in the [[/Background|Background]]) and the potential problems. | There are quite a few notes below, but as it is important for you to know the possible potential problems, please read them all. (Further limitations are described in the [[/Background|Background]].) |
Line 56: | Line 60: |
* This process has been tested for a modern computer with EFI (aka UEFI). If your computer is too old to have EFI, the process would probably work if you omit any step that refers to it, but be aware that this type of encryption might slow down your old computer. | * This process has been tested for a modern computer with EFI. See [[/Basics#EFI|Basics → EFI]] for further information. |
Line 58: | Line 62: |
* Encrypting everything is more CPU-intensive. Modern computers tend to have fast multiple CPUs and dedicated AES (encryption) chips, so on a modern computer, this pose no problem at all. You would be likely to find slower responses only on old computers. | * Encrypting everything is more CPU-intensive. Modern computers tend to have fast multiple CPUs and dedicated AES (encryption) chips, so on a modern computer, this poses no problem at all. You would be likely to notice slower responses only on very old computers. * This process has been test on Ubuntu 16.04 (Xenial Xerus) and partially on Ubuntu 16.10 (Yakkety Yak). It is unlikely to work on previous versions. It will probably will work on later versions, at least for a few years. * These instructions are designed only for Windows and Linux-based computers, and do not cover any other system including Apple devices. If you wish to adapt these instructions to Apple or other devices, they probably will work, but I cannot promise this. * Hardware can be quite different, and sometimes an OEM will not adhere to the proper standards. This means that the installation cannot be guaranteed to work on your specific system, sorry. = Distributions other than Ubuntu = This process has not been tested on other Linux versions, but all Ubuntu-based distributions (, e.g. [[http://lubuntu.net/|Lubuntu]] and [[https://linuxmint.com/|Mint]]) are likely to work with this process. |
Line 72: | Line 88: |
* Partitioning | * EFI (aka UEFI) * Partitioning… * … including naming of partitions and file systems |
Line 75: | Line 93: |
* Editing files from root If you are new to Linux, or you don't know much about some or all of these features, this section is for you. You can safely skip the Basics if you are already familiar with all of these concepts. |
* Text files, including how to edit them If you are new to Linux, or you don't know much about some or all of these features, this section is for you. You can safely skip the Basics if you are already familiar with all of these concepts.<<BR>> |
Line 80: | Line 99: |
1. [[/Process|Detailed process]]<<BR>>Exactly how to prepare your system and install Ubuntu with encryption. Checkpoints are given along the way. It takes into account dual-booting and, optionally, paranoid mode. | 1. [[/DetailedProcess|Detailed process]]<<BR>>Exactly how to prepare your system and install Ubuntu with encryption. Checkpoints are given along the way. It takes into account dual-booting and, optionally, paranoid mode. |
1. Purpose
This document is for you if you wish to use full system encryption with all of these features:
- LUKS
- LVM
- encrypted Boot
- manual partitioning
and optionally any of these features:
- encrypted hibernation
- hybrid suspend
- dual-booting
- multi-disk installation
The following advanced features are available, but are not covered in this process.
- Snapshot: Take a snapshot of your system, e.g. before doing a risky upgrade, and easily roll back if required.
- Boot from external USB: Put the two small unencrypted parts of the boot system (the bootloader and the ESP) onto a USB stick, so the computer cannot be started without the USB stick. Nothing unencrypted is left on the computer, except for what comes built in with the hardware and any existing system such as Windows.
2. Caveats
There are quite a few notes below, but as it is important for you to know the possible potential problems, please read them all. (Further limitations are described in the Background.)
Always, when you install a system, there is a chance of data loss. No matter how careful you are, sometimes a person makes a silly mistake. For example, you accidentally delete the Windows partition. Or, something else can go wrong (I've had an installation cause data loss because a previously-unused part of the hard drive was faulty and caused it to crash). Therefore:
Take a full backup of all of your data before you start the process.
If you know how to use CloneZilla, you would be well advised to back up your entire disk beforehand.
The process optionally enables hibernation. While this should work well, some people have reported hardware that doesn't support it. So, you will need to test this on your machine after installation.
A consequence of full system encryption is that you need to type in your passphrase each time you power on your computer, including after hibernation.
- An unfortunate and inconvenient quirk is that if you mistype the passphrase, you have to reboot your computer to try again. I do not know a way around this.
If you share your computer with anyone else, they need to know the passphrase, even if they only use Windows.
You need a strong passphrase to prevent a hacker with physical access to your machine from breaking the encryption. You can look up "strong passphrase" for yourself; here's a pretty good method for paranoid mode.
Having a strong passphrase does not obviate the need for a good account password. Without a password, or with only a weak password:
- You cannot lock the computer when it is unattended and powered on.
- Anyone with physical access, or a hacker with Internet access, will find it easy to access your account and steal data or install malware such as a keylogger.
Remember that the passphrase for your computer and the password for your account are not the same. One lets you access your computer in the first place, whereas the other lets you log in after you have accessed your computer.1
This process has been tested for a modern computer with EFI. See Basics → EFI for further information.
- Encrypting everything is more CPU-intensive. Modern computers tend to have fast multiple CPUs and dedicated AES (encryption) chips, so on a modern computer, this poses no problem at all. You would be likely to notice slower responses only on very old computers.
- This process has been test on Ubuntu 16.04 (Xenial Xerus) and partially on Ubuntu 16.10 (Yakkety Yak). It is unlikely to work on previous versions. It will probably will work on later versions, at least for a few years.
- These instructions are designed only for Windows and Linux-based computers, and do not cover any other system including Apple devices. If you wish to adapt these instructions to Apple or other devices, they probably will work, but I cannot promise this.
- Hardware can be quite different, and sometimes an OEM will not adhere to the proper standards. This means that the installation cannot be guaranteed to work on your specific system, sorry.
3. Distributions other than Ubuntu
This process has not been tested on other Linux versions, but all Ubuntu-based distributions (, e.g. Lubuntu and Mint) are likely to work with this process.
4. Document Structure
Because the default Ubuntu Installer supports only the first two of the above-mentioned features (i.e. LUKS and LVM), and even then only for full-disk encryption, this installation process is rather more complicated than you might prefer. Thus, this document is organised into several sections. They are intended to be read in the order given here.
Background
A summary of the options; features; benefits and downsides; and purpose and limitations.
It contains important notes and further caveats, so please read the Background before proceeding.- Hybrid suspend
- Command line interface (CLI), aka the terminal
- EFI (aka UEFI)
- Partitioning…
- … including naming of partitions and file systems
- LUKS
- LVM
- Text files, including how to edit them
If you are new to Linux, or you don't know much about some or all of these features, this section is for you. You can safely skip the Basics if you are already familiar with all of these concepts.
High-level overview
What this process will achieve, and what you need to do to prepare. It includes freeing space on your hard drive if your current system has taken it all.Detailed process
Exactly how to prepare your system and install Ubuntu with encryption. Checkpoints are given along the way. It takes into account dual-booting and, optionally, paranoid mode.Troubleshooting
Sometimes something goes wrong and you struggle to figure out what. Errors and their messages can seem bewildering. Here are some pointers.
In this context, the terms "passphrase" and "password" are interchangeable, but in this document, I use "passphrase" for your computer decryption, and "password" for your account login. (1)
paddy-landau/sandbox (last edited 2017-04-04 18:58:46 by paddy-landau)