个人工具

“UbuntuHelp:EncryptedFilesystemHowto3”的版本间的差异

来自Ubuntu中文

跳转至: 导航, 搜索
 
(未显示同一用户的7个中间版本)
第1行: 第1行:
 
{{From|https://help.ubuntu.com/community/EncryptedFilesystemHowto3}}
 
{{From|https://help.ubuntu.com/community/EncryptedFilesystemHowto3}}
 
{{Languages|UbuntuHelp:EncryptedFilesystemHowto3}}
 
{{Languages|UbuntuHelp:EncryptedFilesystemHowto3}}
== Encrypted Swap and Home with LUKS (on Ubuntu 6.06 and 5.10) ==
+
<<Include(Tag/ContentCleanup)>>
by Stefano Spinucci virgo977virgo at <googlemail> dot com
+
== Encrypted Swap and Home with LUKS on Ubuntu 6.06 and 5.10 ==
=== introduction ===
+
{|border="1" cellspacing="0"
==== notes ====
+
| {i} Please refer to [[UbuntuHelp:EncryptedFilesystems|EncryptedFilesystems]] for further documentation.
'''NOTE#1''' in this tutorial we assume that:
+
|}
* old (unencrypted) and the new (encrypted) swap is in the partition '/dev/hda2'
+
By Stefano Spinucci: virgo977virgo at <googlemail> dot com
* new home (encrypted) is in the partition '/dev/hda3'
+
=== Introduction ===
replace '/dev/hda2' with your real swap partition and '/dev/hda3' with an
+
==== Notes ====
 +
* Newer Ubuntu versions can do hard disk encryption during installation time. You need to install from alternative install CD. [http://users.piuha.net/martti/comp/ubuntu/en/cryptolvm.html Here are instructions for install time encryption].
 +
* In this tutorial we assume that:
 +
* Old (unencrypted) and the new (encrypted) swap is in the partition '/dev/hda2'
 +
* New home (encrypted) is in the partition '/dev/hda3'
 +
Replace '/dev/hda2' with your real swap partition and '/dev/hda3' with an
 
empty partition that will become your new encrypted home partition.
 
empty partition that will become your new encrypted home partition.
'''NOTE#2''' DM-Crypt works by transparently translating (in the kernel)
+
* DM-Crypt works by transparently translating (in the kernel) between a physical on-disk partition (which is encrypted) and a logical partition which you can then mount and use as normal; then, for example, to operate on your home partition you must do so by using /dev/mapper/home instead of /dev/hda3.
between a physical on-disk partition (which is encrypted) and a logical
+
* If you are using Windows and you need to encrypt it also, it can be done [http://blog.redinnovation.com/2008/07/15/perfect-dual-boot-crypted-hard-disk-setup-with-truecrypt-and-luks/ with free open source tools in Linux friendly manner].
partition which you can then mount and use as normal; then, for example,
+
==== Warnings ====
to operate on your home partition you must do so by using /dev/mapper/home
+
Encrypting a partition is a destructive operation; then, your new home
instead of /dev/hda3.
+
==== warnings ====
+
encrypting a partition is a destructive operation; then, your new home
+
 
partition (/dev/hda3) must be empty, because all data on it will be erased.
 
partition (/dev/hda3) must be empty, because all data on it will be erased.
unencrypted data on the old home directory won’t be deleted and will be
+
Unencrypted data on the old home directory won’t be deleted and will be
 
accessible, for example, with a live CD; then, you shouldn't put any
 
accessible, for example, with a live CD; then, you shouldn't put any
 
sensitive data on home before encrypting.
 
sensitive data on home before encrypting.
otherwise, if you have sensitive data to delete securely from the old
+
Otherwise, if you have sensitive data to delete securely from the old
 
unencrypted home, you should <code><nowiki>shred</nowiki></code> the old home directory.
 
unencrypted home, you should <code><nowiki>shred</nowiki></code> the old home directory.
if the partition containing the old home directory is formatted with a
+
If the partition containing the old home directory is formatted with a
 
journaled file system (JFS, ReiserFS, XFS, Ext3, etc.), you must boot with
 
journaled file system (JFS, ReiserFS, XFS, Ext3, etc.), you must boot with
 
a live CD and <code><nowiki>shred</nowiki></code> the entire partition containing the old home
 
a live CD and <code><nowiki>shred</nowiki></code> the entire partition containing the old home
 
directory.
 
directory.
if the shredded partition is the partition containing the OS, reinstall
+
If the shredded partition is the partition containing the OS, reinstall
 
ubuntu, and finally mount the previously created encrypted home.
 
ubuntu, and finally mount the previously created encrypted home.
references for secure deletion:
+
References for secure deletion:
 
* [http://man.linuxquestions.org/index.php?query=shred&type=2&section=1 shred man page]
 
* [http://man.linuxquestions.org/index.php?query=shred&type=2&section=1 shred man page]
 
* [http://www.cs.auckland.ac.nz/~pgut001/pubs/secure_del.html Secure Deletion of Data - by Peter Gutmann]
 
* [http://www.cs.auckland.ac.nz/~pgut001/pubs/secure_del.html Secure Deletion of Data - by Peter Gutmann]
==== strong passwords ====
+
==== Strong Passwords ====
remember that ''a chain is only as strong as its weakest link'', and in
+
Remember that ''a chain is only as strong as its weakest link'', and in
 
the encryption chain the password is always the weakest link.
 
the encryption chain the password is always the weakest link.
then, choose a strong password, or your data won't be more secure than
+
Then, choose a strong password, or your data won't be more secure than
 
without encryption.
 
without encryption.
references for strong passwords:
+
References for strong passwords:
* [https://wiki.ubuntu.com/StrongPasswords Strong Passwords (Ubuntu wiki)]
+
* [[UbuntuWiki:StrongPasswords|Strong|Passwords (Ubuntu wiki)]]
 
* [http://diceware.com The Diceware Passphrase Home Page]
 
* [http://diceware.com The Diceware Passphrase Home Page]
 
* [http://en.wikipedia.org/wiki/Password_strength Password strength (Wikipedia)]
 
* [http://en.wikipedia.org/wiki/Password_strength Password strength (Wikipedia)]
 
* [http://en.wikipedia.org/wiki/Password_cracking Password cracking (Wikipedia)]
 
* [http://en.wikipedia.org/wiki/Password_cracking Password cracking (Wikipedia)]
 
* [http://en.wikipedia.org/wiki/Key_size Key size (Wikipedia)]
 
* [http://en.wikipedia.org/wiki/Key_size Key size (Wikipedia)]
=== install cryptsetup ===
+
=== Install cryptsetup ===
enable 'community maintained' (universe) repository from the Synaptic
+
Enable 'community maintained' (universe) repository from the Synaptic
package manager or modifying the file /etc/apt/sources.list (apt sources
+
package manager or modifying the file /etc/apt/sources.list (APT sources
 
list).
 
list).
install cryptsetup:
+
Install cryptsetup:
 
<pre><nowiki>
 
<pre><nowiki>
# apt-get install cryptsetup
+
$ sudo apt-get install cryptsetup
 
</nowiki></pre>
 
</nowiki></pre>
=== encrypted home ===
+
=== Encrypted Home ===
unmount (if mounted) /dev/hda3
+
Unmount (if mounted) /dev/hda3
 
<pre><nowiki>
 
<pre><nowiki>
sudo umount /dev/hda3
+
$ sudo umount /dev/hda3
 
</nowiki></pre>
 
</nowiki></pre>
check the partition for errors (and wait several minutes...):
+
Check the partition for errors (and wait several minutes...):
 
<pre><nowiki>
 
<pre><nowiki>
# sudo /sbin/badblocks -c 10240 -s -w -t random -v /dev/hda3
+
$ sudo /sbin/badblocks -c 10240 -s -w -t random -v /dev/hda3
 
</nowiki></pre>
 
</nowiki></pre>
fill the disk with random data (and wait many more minutes...);
+
Fill the disk with random data (and wait many more minutes...);
 
/dev/urandom won't be as random as /dev/random, but it is the best
 
/dev/urandom won't be as random as /dev/random, but it is the best
 
practical solution available:
 
practical solution available:
 
<pre><nowiki>
 
<pre><nowiki>
# sudo dd if=/dev/urandom of=/dev/hda3
+
$ sudo dd if=/dev/urandom of=/dev/hda3
 
</nowiki></pre>
 
</nowiki></pre>
create a LUKS partition:
+
Create a LUKS partition:
 
<pre><nowiki>
 
<pre><nowiki>
# sudo cryptsetup --verify-passphrase --verbose --hash=sha256 --cipher=aes-cbc-essiv:sha256 --key-size=256 luksFormat /dev/hda3
+
$ sudo cryptsetup --verify-passphrase --verbose --hash=sha256 --cipher=aes-cbc-essiv:sha256 --key-size=256 luksFormat /dev/hda3
 
</nowiki></pre>
 
</nowiki></pre>
'''NOTE''': if you get errors that the kernel may not use dm-crypt, try the command <code><nowiki>modprobe dm-crypt</nowiki></code> and retry to create the LUKS partition; if that helps, you may also want to add the module <code><nowiki>dm-crypt</nowiki></code> to the file <code><nowiki>/etc/modules</nowiki></code>.
+
'''NOTE''': If you get errors that the kernel may not use dm-crypt, try the command <code><nowiki>modprobe dm-crypt</nowiki></code> and retry to create the LUKS partition; if that helps, you may also want to add the module <code><nowiki>dm-crypt</nowiki></code> to the file <code><nowiki>/etc/modules</nowiki></code>.
set up the device mapper:
+
Set up the device mapper:
 
<pre><nowiki>
 
<pre><nowiki>
# sudo cryptsetup luksOpen /dev/hda3 home
+
$ sudo cryptsetup luksOpen /dev/hda3 home
 
</nowiki></pre>
 
</nowiki></pre>
confirm it worked:
+
Confirm it worked:
 
<pre><nowiki>
 
<pre><nowiki>
# sudo cryptsetup status home
+
$ sudo cryptsetup status home
 
/dev/mapper/home is active:
 
/dev/mapper/home is active:
cipher:  aes-cbc-essiv:sha256
+
  cipher:  aes-cbc-essiv:sha256
keysize: 256 bits
+
  keysize: 256 bits
device:  /dev/.static/dev/hda3
+
  device:  /dev/.static/dev/hda3
offset:  2056 sectors
+
  offset:  2056 sectors
size:    20962706 sectors
+
  size:    20962706 sectors
mode:    read/write
+
  mode:    read/write
 
</nowiki></pre>
 
</nowiki></pre>
create the filesystem (e.g. ext3):
+
Create the filesystem (e.g. ext3):
 
<pre><nowiki>
 
<pre><nowiki>
# sudo mke2fs -j -O dir_index,filetype,sparse_super /dev/mapper/home
+
$ sudo mke2fs -j -O dir_index,filetype,sparse_super /dev/mapper/home
 
</nowiki></pre>
 
</nowiki></pre>
temporary mount, to copy data from old home:
+
Temporary mount, to copy data from old home:
 
<pre><nowiki>
 
<pre><nowiki>
# sudo mount -t ext3 /dev/mapper/home /mnt
+
$ sudo mount -t ext3 /dev/mapper/home /mnt
 
</nowiki></pre>
 
</nowiki></pre>
copy data from old home:
+
Copy data from old home:
 
<pre><nowiki>
 
<pre><nowiki>
# sudo cp -axv /home/* /mnt/
+
$ sudo cp -axv /home/* /mnt/
 
</nowiki></pre>
 
</nowiki></pre>
unmount the temporary mount:
+
Unmount the temporary mount:
 
<pre><nowiki>
 
<pre><nowiki>
# sudo umount /mnt
+
$ sudo umount /mnt
 
</nowiki></pre>
 
</nowiki></pre>
==== permanent mounting ====
+
==== Permanent Mounting ====
 
===== Ubuntu 6.06 =====
 
===== Ubuntu 6.06 =====
insert in /etc/fstab :
+
Insert in /etc/fstab :
 
<pre><nowiki>
 
<pre><nowiki>
 
# <file system>    <mount point>  <type>  <options>  <dump>  <pass>
 
# <file system>    <mount point>  <type>  <options>  <dump>  <pass>
 
/dev/mapper/home  /home          ext3    defaults    1      2
 
/dev/mapper/home  /home          ext3    defaults    1      2
 
</nowiki></pre>
 
</nowiki></pre>
after that, add an entry in /etc/crypttab:
+
After that, add an entry in /etc/crypttab:
 
<pre><nowiki>
 
<pre><nowiki>
 
# <target device>  <source device>  <key file>  <options>
 
# <target device>  <source device>  <key file>  <options>
 
home                /dev/hda3        none        luks
 
home                /dev/hda3        none        luks
 
</nowiki></pre>
 
</nowiki></pre>
reboot, and the encrypted home is done.
+
Reboot, and the encrypted home is done.
 
===== Ubuntu 5.10 =====
 
===== Ubuntu 5.10 =====
because 'crypttab' in Ubuntu 5.10 doesn't support LUKS encrypted
+
Because 'crypttab' in Ubuntu 5.10 doesn't support LUKS encrypted
 
partitions, automatic mounting of home with Ubuntu 5.10 is a bit more
 
partitions, automatic mounting of home with Ubuntu 5.10 is a bit more
 
difficult.
 
difficult.
create a file named 'cryptinit' in /etc/init.d/ with the following content:
+
Create a file named 'cryptinit' in /etc/init.d/ with the following content:
 
<pre><nowiki>
 
<pre><nowiki>
 
#! /bin/sh
 
#! /bin/sh
第126行: 第128行:
 
# opening it
 
# opening it
 
if [ -b /dev/mapper/home ]; then
 
if [ -b /dev/mapper/home ]; then
/sbin/cryptsetup luksClose home
+
    /sbin/cryptsetup luksClose home
 
else
 
else
i=3
+
    i=3
while [ $i -gt 0 ]; do
+
    while [ $i -gt 0 ]; do
let "i -= 1"
+
        let "i -= 1"
/sbin/cryptsetup luksOpen /dev/hda3 home && i=0
+
        /sbin/cryptsetup luksOpen /dev/hda3 home && i=0
done
+
    done
 
fi
 
fi
 
</nowiki></pre>
 
</nowiki></pre>
make 'cryptinit' executable
+
Make 'cryptinit' executable
 
<pre><nowiki>
 
<pre><nowiki>
sudo chmod 755 /etc/init.d/cryptinit
+
$ sudo chmod 755 /etc/init.d/cryptinit
 
</nowiki></pre>
 
</nowiki></pre>
then, create a symlink to 'cryptinit' in /etc/rcS.d
+
Then, create a symlink to 'cryptinit' in /etc/rcS.d
 
<pre><nowiki>
 
<pre><nowiki>
# cd /etc/rcS.d
+
$ cd /etc/rcS.d
# sudo ln -s ../init.d/cryptinit S28cryptinit
+
$ sudo ln -s ../init.d/cryptinit S28cryptinit
 
</nowiki></pre>
 
</nowiki></pre>
insert in /etc/fstab :
+
Insert in /etc/fstab :
 
<pre><nowiki>
 
<pre><nowiki>
 
# <file system>    <mount point>  <type>  <options>  <dump>  <pass>
 
# <file system>    <mount point>  <type>  <options>  <dump>  <pass>
 
/dev/mapper/home  /home          ext3    defaults    1        2
 
/dev/mapper/home  /home          ext3    defaults    1        2
 
</nowiki></pre>
 
</nowiki></pre>
reboot, and the encrypted home is done.
+
Reboot, and the encrypted home is done.
===== notes =====
+
===== Notes =====
with the instructions above about encrypting home you can also encrypt
+
With the instructions above about encrypting home you can also encrypt
 
generic data partitions (other than home), and you can permanently mount
 
generic data partitions (other than home), and you can permanently mount
 
them in two ways.
 
them in two ways.
the first technique is shown above for mounting home, and requests the
+
The first technique is shown above for mounting home, and requests the
 
password during the loading of the kernel.
 
password during the loading of the kernel.
the second technique we explain here asks you for the password right at
+
The second technique we explain here asks you for the password right at
 
the end of the booting process, at the gnome login:
 
the end of the booting process, at the gnome login:
* do not make any modifications to /etc/fstab or /etc/crypttab
+
* Do not make any modifications to /etc/fstab or /etc/crypttab
* add the encrypted partition to /etc/pmount.allow (ie. <code><nowiki>/dev/hda3</nowiki></code>)
+
* Add the encrypted partition to /etc/pmount.allow (ie. <code><nowiki>/dev/hda3</nowiki></code>)
this will give you the convenience of entering the password at the end of
+
This will give you the convenience of entering the password at the end of
 
the boot process rather than in the middle. however, a
 
the boot process rather than in the middle. however, a
 
[https://launchpad.net/distros/ubuntu/+ticket/985 bug] means that your
 
[https://launchpad.net/distros/ubuntu/+ticket/985 bug] means that your
 
encrypted partition will always be called 'usbdisk' whether it is a usbdisk
 
encrypted partition will always be called 'usbdisk' whether it is a usbdisk
 
or not.
 
or not.
==== manual mounting and unmounting ====
+
==== Manual Mounting and Unmounting ====
if you have encrypted other partitions than home and you don't want to
+
If you have encrypted other partitions than home and you don't want to
 
unlock those partitions on boot, then you need to manually mount and
 
unlock those partitions on boot, then you need to manually mount and
 
unmount them.
 
unmount them.
===== mounting =====
+
===== Mounting =====
set up the device mapper:
+
Set up the device mapper:
 
<pre><nowiki>
 
<pre><nowiki>
# cryptsetup luksOpen /dev/hda4 data
+
$ cryptsetup luksOpen /dev/hda4 data
 
</nowiki></pre>
 
</nowiki></pre>
mounting:
+
Mounting:
 
<pre><nowiki>
 
<pre><nowiki>
# mount /dev/mapper/data /media/data
+
$ mount /dev/mapper/data /media/data
 
</nowiki></pre>
 
</nowiki></pre>
===== unmounting =====
+
===== Unmounting =====
umounting:
+
Umounting:
 
<pre><nowiki>
 
<pre><nowiki>
# umount /media/data
+
$ umount /media/data
 
</nowiki></pre>
 
</nowiki></pre>
delete the device mapper:
+
Delete the device mapper:
 
<pre><nowiki>
 
<pre><nowiki>
# cryptsetup luksClose data
+
$ cryptsetup luksClose data
 
</nowiki></pre>
 
</nowiki></pre>
=== encrypted swap ===
+
=== Encrypted Swap ===
before setting the encrypted swap, the file /etc/fstab should have a swap
+
Before setting the encrypted swap, the file /etc/fstab should have a swap
 
entry like this:
 
entry like this:
 
<pre><nowiki>
 
<pre><nowiki>
第194行: 第196行:
 
/dev/hda2        none            swap    sw          0      0
 
/dev/hda2        none            swap    sw          0      0
 
</nowiki></pre>
 
</nowiki></pre>
now just replace in /etc/fstab /dev/hda2 with the new device name
+
Now just replace in /etc/fstab /dev/hda2 with the new device name
 
/dev/mapper/cswap:
 
/dev/mapper/cswap:
 
<pre><nowiki>
 
<pre><nowiki>
第200行: 第202行:
 
/dev/mapper/cswap  none            swap    sw          0      0
 
/dev/mapper/cswap  none            swap    sw          0      0
 
</nowiki></pre>
 
</nowiki></pre>
after that, add an entry in /etc/crypttab:
+
After that, add an entry in /etc/crypttab:
 
<pre><nowiki>
 
<pre><nowiki>
 
# <target device>  <source device>  <key file>    <options>
 
# <target device>  <source device>  <key file>    <options>
 
cswap              /dev/hda2        /dev/random  swap
 
cswap              /dev/hda2        /dev/random  swap
 
</nowiki></pre>
 
</nowiki></pre>
reboot, and that's it! the encrypted swap device is done; confirm it worked:
+
Reboot, and that's it! The encrypted swap device is done; confirm it worked:
 
<pre><nowiki>
 
<pre><nowiki>
# cat /proc/swaps
+
$ cat /proc/swaps
 
Filename                                Type            Size    Used    Priority
 
Filename                                Type            Size    Used    Priority
 
/dev/mapper/cswap                      partition      3148700 0      -1
 
/dev/mapper/cswap                      partition      3148700 0      -1
# sudo cryptsetup status cswap
+
 
 +
$ sudo cryptsetup status cswap
 
/dev/mapper/cswap is active:
 
/dev/mapper/cswap is active:
cipher:  aes-cbc-plain
+
  cipher:  aes-cbc-plain
keysize: 256 bits
+
  keysize: 256 bits
device:  /dev/.static/dev/hda2
+
  device:  /dev/.static/dev/hda2
offset:  0 sectors
+
  offset:  0 sectors
size:    6297417 sectors
+
  size:    6297417 sectors
mode:    read/write
+
  mode:    read/write
 
</nowiki></pre>
 
</nowiki></pre>
read the crypttab(5) manpage for more information
+
Read the crypttab(5) manpage for more information.
=== encrypting with keyfiles ===
+
=== Encrypting with Keyfiles ===
with LUKS you can encrypt/decrypt with keyfiles instead of passphrases.
+
With LUKS you can encrypt/decrypt with keyfiles instead of passphrases.
you can add a keyfile with the command luksFormat or with the command
+
You can add a keyfile with the command luksFormat or with the command
 
luksAddKey.
 
luksAddKey.
for example, you can add with luksFormat a passphrase on slot 0 and with
+
For example, you can add with luksFormat a passphrase on slot 0 and with
 
luksAddKey a keyfile on slot 1; then, you can open your encrypted device
 
luksAddKey a keyfile on slot 1; then, you can open your encrypted device
 
with the keyfile and, if you lose the keyfile, you can always use the
 
with the keyfile and, if you lose the keyfile, you can always use the
 
passphrase.
 
passphrase.
for better security you can store your keyfiles on a USB stick, maybe
+
For better security you can store your keyfiles on a USB stick, maybe
 
encrypting the USB stick with a passphrase.
 
encrypting the USB stick with a passphrase.
you can use every file you like as keyfile; for example, to generate a
+
You can use every file you like as keyfile; for example, to generate a
 
2048bit random key:
 
2048bit random key:
 
<pre><nowiki>
 
<pre><nowiki>
# dd if=/dev/random of=keyfile bs=1 count=256
+
$ dd if=/dev/random of=keyfile bs=1 count=256
 
</nowiki></pre>
 
</nowiki></pre>
then, to add the generated keyfile to an existing encrypted partition:
+
Then, to add the generated keyfile to an existing encrypted partition:
 
<pre><nowiki>
 
<pre><nowiki>
the following command will require you to enter two times the passphrase
+
The following command will require you to enter two times the passphrase
 
stored on slot 0...
 
stored on slot 0...
# sudo cryptsetup luksAddKey /dev/hda4 keyfile
+
$ sudo cryptsetup luksAddKey /dev/hda4 keyfile
 
</nowiki></pre>
 
</nowiki></pre>
finally, to open the encrypted partition with the keyfile:
+
Finally, to open the encrypted partition with the keyfile:
 
<pre><nowiki>
 
<pre><nowiki>
# sudo cryptsetup luksOpen /dev/hda4 data --key-file keyfile
+
$ sudo cryptsetup luksOpen /dev/hda4 data --key-file keyfile
 
</nowiki></pre>
 
</nowiki></pre>
if you like to disable (delete) the keyfile on slot 1:
+
If you like to disable (delete) the keyfile on slot 1:
 
<pre><nowiki>
 
<pre><nowiki>
# sudo cryptsetup luksDelKey /dev/hda4 1
+
$ sudo cryptsetup luksDelKey /dev/hda4 1
 
</nowiki></pre>
 
</nowiki></pre>
=== tools ===
+
=== Tools ===
 
* [http://sourceforge.net/projects/cryptmount/ cryptmount]
 
* [http://sourceforge.net/projects/cryptmount/ cryptmount]
=== references ===
+
=== References ===
 
* [http://luks.endorphin.org/dm-crypt LUKS on dm-crypt]
 
* [http://luks.endorphin.org/dm-crypt LUKS on dm-crypt]
 
* [http://www.saout.de/misc/dm-crypt/ dm-crypt]
 
* [http://www.saout.de/misc/dm-crypt/ dm-crypt]
第257行: 第260行:
 
* [http://news.gmane.org/gmane.linux.kernel.device-mapper.dm-crypt dm-crypt mailing list]
 
* [http://news.gmane.org/gmane.linux.kernel.device-mapper.dm-crypt dm-crypt mailing list]
 
* [http://www.saout.de/tikiwiki/tiki-index.php?page=EncryptedDeviceUsingLUKS Encrypted Device Using LUKS]
 
* [http://www.saout.de/tikiwiki/tiki-index.php?page=EncryptedDeviceUsingLUKS Encrypted Device Using LUKS]
* <code><nowiki>/usr/share/doc/cryptsetup/CryptoSwap.[[UbuntuHelp:HowTo|HowTo]]</nowiki></code> How to configure an encrypted swap partition on Debian systems
+
* <code><nowiki>/usr/share/doc/cryptsetup/CryptoSwap.HowTo</nowiki></code> How to configure an encrypted swap partition on Debian systems
* [https://wiki.ubuntu.com/EncryptedFilesystemHowto Encrypted filesystem howto (Ubuntu)]
+
* [[UbuntuWiki:EncryptedFilesystemHowto|Encrypted|filesystem howto (Ubuntu)]]
* [https://wiki.ubuntu.com/EncryptedFilesystemHowto2 Encrypted filesystem howto 2 (Ubuntu)]
+
* [[UbuntuWiki:EncryptedFilesystemHowto2|Encrypted|filesystem howto 2 (Ubuntu)]]
 
* [http://deb.riseup.net/storage/encryption/dmcrypt/ dmcrypt (Debian)]
 
* [http://deb.riseup.net/storage/encryption/dmcrypt/ dmcrypt (Debian)]
 
* [http://www.raoul.shacknet.nu/2005/11/10/encrypt-devices-using-dm-crypt-and-luks/ Encrypt devices using dm-crypt and LUKS (Fedora Core)]
 
* [http://www.raoul.shacknet.nu/2005/11/10/encrypt-devices-using-dm-crypt-and-luks/ Encrypt devices using dm-crypt and LUKS (Fedora Core)]
第266行: 第269行:
 
* [http://gentoo-wiki.com/SECURITY_Encrypting_Root_Filesystem_with_DM-Crypt SECURITY Encrypting Root Filesystem with DM-Crypt (Gentoo)]
 
* [http://gentoo-wiki.com/SECURITY_Encrypting_Root_Filesystem_with_DM-Crypt SECURITY Encrypting Root Filesystem with DM-Crypt (Gentoo)]
 
----
 
----
[[category:CategoryCleanup]] [[category:CategorySecurity]]
+
[[category:CategorySecurity]]
  
 
[[category:UbuntuHelp]]
 
[[category:UbuntuHelp]]

2009年11月17日 (二) 19:02的最新版本

<<Include(Tag/ContentCleanup)>>

Encrypted Swap and Home with LUKS on Ubuntu 6.06 and 5.10

{i} Please refer to EncryptedFilesystems for further documentation.

By Stefano Spinucci: virgo977virgo at <googlemail> dot com

Introduction

Notes

  • Newer Ubuntu versions can do hard disk encryption during installation time. You need to install from alternative install CD. Here are instructions for install time encryption.
  • In this tutorial we assume that:
  • Old (unencrypted) and the new (encrypted) swap is in the partition '/dev/hda2'
  • New home (encrypted) is in the partition '/dev/hda3'

Replace '/dev/hda2' with your real swap partition and '/dev/hda3' with an empty partition that will become your new encrypted home partition.

  • DM-Crypt works by transparently translating (in the kernel) between a physical on-disk partition (which is encrypted) and a logical partition which you can then mount and use as normal; then, for example, to operate on your home partition you must do so by using /dev/mapper/home instead of /dev/hda3.
  • If you are using Windows and you need to encrypt it also, it can be done with free open source tools in Linux friendly manner.

Warnings

Encrypting a partition is a destructive operation; then, your new home partition (/dev/hda3) must be empty, because all data on it will be erased. Unencrypted data on the old home directory won’t be deleted and will be accessible, for example, with a live CD; then, you shouldn't put any sensitive data on home before encrypting. Otherwise, if you have sensitive data to delete securely from the old unencrypted home, you should shred the old home directory. If the partition containing the old home directory is formatted with a journaled file system (JFS, ReiserFS, XFS, Ext3, etc.), you must boot with a live CD and shred the entire partition containing the old home directory. If the shredded partition is the partition containing the OS, reinstall ubuntu, and finally mount the previously created encrypted home. References for secure deletion:

Strong Passwords

Remember that a chain is only as strong as its weakest link, and in the encryption chain the password is always the weakest link. Then, choose a strong password, or your data won't be more secure than without encryption. References for strong passwords:

Install cryptsetup

Enable 'community maintained' (universe) repository from the Synaptic package manager or modifying the file /etc/apt/sources.list (APT sources list). Install cryptsetup:

$ sudo apt-get install cryptsetup

Encrypted Home

Unmount (if mounted) /dev/hda3

$ sudo umount /dev/hda3

Check the partition for errors (and wait several minutes...):

$ sudo /sbin/badblocks -c 10240 -s -w -t random -v /dev/hda3

Fill the disk with random data (and wait many more minutes...); /dev/urandom won't be as random as /dev/random, but it is the best practical solution available:

$ sudo dd if=/dev/urandom of=/dev/hda3

Create a LUKS partition:

$ sudo cryptsetup --verify-passphrase --verbose --hash=sha256 --cipher=aes-cbc-essiv:sha256 --key-size=256 luksFormat /dev/hda3

NOTE: If you get errors that the kernel may not use dm-crypt, try the command modprobe dm-crypt and retry to create the LUKS partition; if that helps, you may also want to add the module dm-crypt to the file /etc/modules. Set up the device mapper:

$ sudo cryptsetup luksOpen /dev/hda3 home

Confirm it worked:

$ sudo cryptsetup status home
/dev/mapper/home is active:
  cipher:  aes-cbc-essiv:sha256
  keysize: 256 bits
  device:  /dev/.static/dev/hda3
  offset:  2056 sectors
  size:    20962706 sectors
  mode:    read/write

Create the filesystem (e.g. ext3):

$ sudo mke2fs -j -O dir_index,filetype,sparse_super /dev/mapper/home

Temporary mount, to copy data from old home:

$ sudo mount -t ext3 /dev/mapper/home /mnt

Copy data from old home:

$ sudo cp -axv /home/* /mnt/

Unmount the temporary mount:

$ sudo umount /mnt

Permanent Mounting

Ubuntu 6.06

Insert in /etc/fstab :

# <file system>    <mount point>   <type>   <options>   <dump>  <pass>
/dev/mapper/home   /home           ext3     defaults    1       2

After that, add an entry in /etc/crypttab:

# <target device>   <source device>   <key file>   <options>
home                /dev/hda3         none         luks

Reboot, and the encrypted home is done.

Ubuntu 5.10

Because 'crypttab' in Ubuntu 5.10 doesn't support LUKS encrypted partitions, automatic mounting of home with Ubuntu 5.10 is a bit more difficult. Create a file named 'cryptinit' in /etc/init.d/ with the following content:

#! /bin/sh
# if this script is executed when home is opened, tries to close it;
# otherwise, tries to open it, for three times, then continue without
# opening it
if [ -b /dev/mapper/home ]; then
    /sbin/cryptsetup luksClose home
else
    i=3
    while [ $i -gt 0 ]; do
        let "i -= 1"
        /sbin/cryptsetup luksOpen /dev/hda3 home && i=0
    done
fi

Make 'cryptinit' executable

$ sudo chmod 755 /etc/init.d/cryptinit

Then, create a symlink to 'cryptinit' in /etc/rcS.d

$ cd /etc/rcS.d
$ sudo ln -s ../init.d/cryptinit S28cryptinit

Insert in /etc/fstab :

# <file system>    <mount point>   <type>   <options>   <dump>   <pass>
/dev/mapper/home   /home           ext3     defaults    1        2

Reboot, and the encrypted home is done.

Notes

With the instructions above about encrypting home you can also encrypt generic data partitions (other than home), and you can permanently mount them in two ways. The first technique is shown above for mounting home, and requests the password during the loading of the kernel. The second technique we explain here asks you for the password right at the end of the booting process, at the gnome login:

  • Do not make any modifications to /etc/fstab or /etc/crypttab
  • Add the encrypted partition to /etc/pmount.allow (ie. /dev/hda3)

This will give you the convenience of entering the password at the end of the boot process rather than in the middle. however, a bug means that your encrypted partition will always be called 'usbdisk' whether it is a usbdisk or not.

Manual Mounting and Unmounting

If you have encrypted other partitions than home and you don't want to unlock those partitions on boot, then you need to manually mount and unmount them.

Mounting

Set up the device mapper:

$ cryptsetup luksOpen /dev/hda4 data

Mounting:

$ mount /dev/mapper/data /media/data
Unmounting

Umounting:

$ umount /media/data

Delete the device mapper:

$ cryptsetup luksClose data

Encrypted Swap

Before setting the encrypted swap, the file /etc/fstab should have a swap entry like this:

# <file system>   <mount point>   <type>   <options>   <dump>  <pass>
/dev/hda2         none            swap     sw          0       0

Now just replace in /etc/fstab /dev/hda2 with the new device name /dev/mapper/cswap:

# <file system>     <mount point>   <type>   <options>   <dump>  <pass>
/dev/mapper/cswap   none            swap     sw          0       0

After that, add an entry in /etc/crypttab:

# <target device>   <source device>   <key file>    <options>
cswap               /dev/hda2         /dev/random   swap

Reboot, and that's it! The encrypted swap device is done; confirm it worked:

$ cat /proc/swaps
Filename                                Type            Size    Used    Priority
/dev/mapper/cswap                       partition       3148700 0       -1

$ sudo cryptsetup status cswap
/dev/mapper/cswap is active:
  cipher:  aes-cbc-plain
  keysize: 256 bits
  device:  /dev/.static/dev/hda2
  offset:  0 sectors
  size:    6297417 sectors
  mode:    read/write

Read the crypttab(5) manpage for more information.

Encrypting with Keyfiles

With LUKS you can encrypt/decrypt with keyfiles instead of passphrases. You can add a keyfile with the command luksFormat or with the command luksAddKey. For example, you can add with luksFormat a passphrase on slot 0 and with luksAddKey a keyfile on slot 1; then, you can open your encrypted device with the keyfile and, if you lose the keyfile, you can always use the passphrase. For better security you can store your keyfiles on a USB stick, maybe encrypting the USB stick with a passphrase. You can use every file you like as keyfile; for example, to generate a 2048bit random key:

$ dd if=/dev/random of=keyfile bs=1 count=256

Then, to add the generated keyfile to an existing encrypted partition:

The following command will require you to enter two times the passphrase
stored on slot 0...
$ sudo cryptsetup luksAddKey /dev/hda4 keyfile

Finally, to open the encrypted partition with the keyfile:

$ sudo cryptsetup luksOpen /dev/hda4 data --key-file keyfile

If you like to disable (delete) the keyfile on slot 1:

$ sudo cryptsetup luksDelKey /dev/hda4 1

Tools

References