Security Guide
- About This Guide
- 1 Security and Confidentiality
- I Authentication
- II Local Security
- III Network Security
- IV Confining Privileges with AppArmor
- 19 Introducing AppArmor
- 20 Getting Started
- 21 Immunizing Programs
- 22 Profile Components and Syntax
- 23 AppArmor Profile Repositories
- 24 Building and Managing Profiles with YaST
- 25 Building Profiles from the Command Line
- 26 Profiling Your Web Applications Using ChangeHat
- 27 Confining Users with
pam_apparmor - 28 Managing Profiled Applications
- 29 Support
- 30 AppArmor Glossary
- V SELinux
- VI The Linux Audit Framework
- A GNU Licenses
12 Encrypting Partitions and Files Edit source
Encrypting files, partitions, and entire disks prevents unauthorized access to your data and protects your confidential files and documents.
You can choose between the following encryption options:
- Encrypting a Hard Disk Partition
It is possible to create an encrypted partition with YaST during installation or in an already installed system. For further info, see Section 12.1.1, “Creating an Encrypted Partition during Installation” and Section 12.1.2, “Creating an Encrypted Partition on a Running System”. This option can also be used for removable media, such as external hard disks, as described in Section 12.1.3, “Encrypting the Content of Removable Media”.
- Encrypting Single Files with GPG
To quickly encrypt one or more files, you can use the GPG tool. See Section 12.2, “Encrypting Files with GPG” for more information.
Warning: Encryption Offers Limited Protection
Encryption methods described in this chapter cannot protect your running system from being compromised. After the encrypted volume is successfully mounted, everybody with appropriate permissions can access it. However, encrypted media are useful in case of loss or theft of your computer, or to prevent unauthorized individuals from reading your confidential data.
12.1 Setting Up an Encrypted File System with YaST #Edit source
Use YaST to encrypt partitions or parts of your file system during installation or in an already installed system. However, encrypting a partition in an already-installed system is more difficult, because you need to resize and change existing partitions. In such cases, it may be more convenient to create an encrypted file of a defined size, in which to store other files or parts of your file system. To encrypt an entire partition, dedicate a partition for encryption in the partition layout. The standard partitioning proposal, as suggested by YaST, does not include an encrypted partition by default. Add an encrypted partition manually in the partitioning dialog.
12.1.1 Creating an Encrypted Partition during Installation #Edit source
Warning: Password Input
Make sure to memorize the password for your encrypted partitions well. Without that password, you cannot access or restore the encrypted data.
The YaST expert dialog for partitioning offers the options needed for creating an encrypted partition. To create a new encrypted partition proceed as follows:
Run the YaST Expert Partitioner with › .
Select a hard disk, click , and select a primary or an extended partition.
Select the partition size or the region to use on the disk.
Select the file system, and mount point of this partition.
Activate the check box.
Note: Additional Software Required
After checking , a pop-up window asking for installing additional software may appear. Confirm to install all the required packages to ensure that the encrypted partition works well.
If the encrypted file system needs to be mounted only when necessary, enable in the . otherwise enable and enter the mount point.
Click and enter a password which is used to encrypt this partition. This password is not displayed. To prevent typing errors, you need to enter the password twice.
Complete the process by clicking . The newly-encrypted partition is now created.
During the boot process, the operating system asks for the password
before mounting any encrypted partition which is set to be auto-mounted
in /etc/fstab. Such a partition is then available
to all users when it has been mounted.
To skip mounting the encrypted partition during start-up, press Enter when prompted for the password. Then decline the offer to enter the password again. In this case, the encrypted file system is not mounted and the operating system continues booting, blocking access to your data.
To mount an encrypted partition which is not mounted during the boot process, open a file manager and click the partition entry in the pane listing common places on your file system. You will be prompted for a password and the partition will be mounted.
When you are installing your system on a machine where partitions already exist, you can also decide to encrypt an existing partition during installation. In this case follow the description in Section 12.1.2, “Creating an Encrypted Partition on a Running System” and be aware that this action destroys all data on the existing partition.
12.1.2 Creating an Encrypted Partition on a Running System #Edit source
Warning: Activating Encryption on a Running System
It is also possible to create encrypted partitions on a running system. However, encrypting an existing partition destroys all data on it, and requires re-sizing and restructuring of existing partitions.
On a running system, select › in the YaST control center. Click to proceed. In the , select the partition to encrypt and click . The rest of the procedure is the same as described in Section 12.1.1, “Creating an Encrypted Partition during Installation”.
12.1.3 Encrypting the Content of Removable Media #Edit source
YaST treats removable media (like external hard disks or flash disks) the same as any other storage device. Virtual disks or partitions on external media can be encrypted as described above. However, you should disable mounting at boot time, because removable media is usually connected only when the system is up and running.
If you encrypted your removable device with YaST, the GNOME desktop
automatically recognizes the encrypted partition and prompts for the
password when the device is detected. If you plug in a FAT-formatted
removable device when running GNOME, the desktop user entering the
password automatically becomes the owner of the device.
For devices with a file system other than FAT, change the
ownership explicitly for users other than root to give them
read-write access to the device.
12.2 Encrypting Files with GPG #Edit source
The GPG encryption software can be used to encrypt individual files and documents.
To encrypt a file with GPG, you need to generate a key pair first. To do
this, run the gpg --gen-key and follow the on-screen
instructions. When generating the key pair, GPG creates a user ID (UID) to
identify the key based on your real name, comments, and email address. You
need this UID (or just a part of it like your first name or email address)
to specify the key you want to use to encrypt a file. To find the UID of an
existing key, use the gpg --list-keys command. To encrypt
a file use the following command:
tux > gpg -e -r UID
FILEReplace UID with part of the UID (for example, your first name) and FILE with the file you want to encrypt. For example:
tux > gpg -e -r Tux secret.txt
This command creates an encrypted version of the specified file
recognizable by the .gpg file extension (in
this example, it is secret.txt.gpg).
To decrypt an encrypted file, use the following command:
tux > gpg -d -o DECRYPTED_FILE
ENCRYPTED_FILEReplace DECRYPTED_FILE with the desired name for the decrypted file and ENCRYPTED_FILE with the encrypted file you want to decrypt.
Keep in mind that the encrypted file can be only decrypted using the same key that was used for encryption. If you want to share an encrypted file with another person, you have to use that person's public key to encrypt the file.