<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
  <channel>
    <title>Creating a transparently encrypted root filesystem</title>
    <link>http://westhoffswelt.de/blog/creating_a_transparently_encrypted_root_filesystem.html</link>
    <description>This article provides all the neccessary explanations to create a fully transparent filesystem encryption for your system root. After you followed the steps of this tutorial all your data will be stored encrypted on your hard drive during your normal days work. This is especially interesting for laptops which might be stolen with important or even secret information on it.
</description>
    <language>en</language>
    <copyright>CC by-nc-sa</copyright>
    <managingEditor>Jakob Westhoff</managingEditor>
    <managingEditor>Jakob Westhoff &lt;jakob@westhoffswelt.de&gt;</managingEditor>
    <pubDate>Tue, 24 Jun 2008 14:34:12 +0000</pubDate>
    <lastBuildDate>Wed, 04 Feb 2009 22:44:26 +0000</lastBuildDate>
    <generator>eZ Components Feed dev (http://ezcomponents.org/docs/tutorials/Feed)</generator>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <item>
      <title>nmp0906 at Thu, 21 May 2009 08:45:12 +0200</title>
      <link>http://westhoffswelt.de/blog/creating_a_transparently_encrypted_root_filesystem.html#comment_7</link>
      <description>Excellent and thorough guide.  Thank you.&#13;
&#13;
A couple suggestions:&#13;
&#13;
1) I agree with Chris, you need to create /proc and /mnt/root in the initramfs directory before gzip'ng it up.&#13;
2) There is an aes-x86_64 module that needs to be loaded in order for the 64-bit AES cipher to be used.&#13;
3) Specify what your initramfs contains.  For example, noting that your keymap is different than say US, will save people time by just going ahead and rolling their own.  Also, it doesn't look like you included v86d in your initramfs.&#13;
&#13;
Overall, your guide is impressive.  Thanks to you, I didn't have to read/sort through the gentoo-wiki article that was chock full of suspend2 stuff.</description>
      <author>nmp0906</author>
      <pubDate>Thu, 21 May 2009 06:45:12 +0000</pubDate>
    </item>
    <item>
      <title>Chris at Fri, 08 May 2009 17:51:04 +0200</title>
      <link>http://westhoffswelt.de/blog/creating_a_transparently_encrypted_root_filesystem.html#comment_6</link>
      <description>Great guide, some comments though:&#13;
&#13;
- /proc and /mnt/root have to be created manually&#13;
- I also had to uncomment the / part in fstab in order to boot succesfully&#13;
&#13;
With this guide I succesfully created an encrypted gentoo root installation on a raid1 root disk setup. Thank you for writing this nice tutorial!</description>
      <author>Chris</author>
      <pubDate>Fri, 08 May 2009 15:51:04 +0000</pubDate>
    </item>
    <item>
      <title>rac at Tue, 02 Dec 2008 12:06:57 +0100</title>
      <link>http://westhoffswelt.de/blog/creating_a_transparently_encrypted_root_filesystem.html#comment_5</link>
      <description>good point, sounds logically...</description>
      <author>rac</author>
      <pubDate>Tue, 02 Dec 2008 11:06:57 +0000</pubDate>
    </item>
    <item>
      <title>Jakob at Fri, 21 Nov 2008 19:30:38 +0100</title>
      <link>http://westhoffswelt.de/blog/creating_a_transparently_encrypted_root_filesystem.html#comment_4</link>
      <description>That might be true. But as I stated above by writing zeros (0s) to the encryption container, the data written to the disk should be as good as random data in relation to the chances of data reconstruction.&#13;
&#13;
greetings&#13;
Jakob</description>
      <author>Jakob</author>
      <pubDate>Fri, 21 Nov 2008 18:30:38 +0000</pubDate>
    </item>
    <item>
      <title>rac at Fri, 14 Nov 2008 12:55:24 +0100</title>
      <link>http://westhoffswelt.de/blog/creating_a_transparently_encrypted_root_filesystem.html#comment_3</link>
      <description>Hy&#13;
A friend that worked in forensics told me once that if you just overwrite it with 0s it is possible to recover the data partially (maybe just in laboratory) but if you use 1s instead it will be harder and if you use random data its going to be very hard to recover and of course if you use multiple cycles with random data it should be nearly impossible...&#13;
&#13;
greetz rac</description>
      <author>rac</author>
      <pubDate>Fri, 14 Nov 2008 11:55:24 +0000</pubDate>
    </item>
    <item>
      <title>Jakob at Mon, 10 Nov 2008 19:25:02 +0100</title>
      <link>http://westhoffswelt.de/blog/creating_a_transparently_encrypted_root_filesystem.html#comment_2</link>
      <description>Hi,&#13;
&#13;
you are partially right concerning step 8. This step was not ment to ensure the overwritten data could not be reconstructed in any way. It was just introduced to render it virtually impossible to distinguish between encrypted data and free space. This may become relevant if you are using an empty disk for encryption or your previous filesystem has got some serious gaps inbetween the datablocks.&#13;
Nevertheless, it is still not completely clear what kind of overwrite is needed to make sure the data can not be recovered. The wikipedia article about data remanence ( http://en.wikipedia.org/wiki/Data_remanence#Overwriting ) has some details about this. If you are the paranoid type of person you may use a tool which uses the Gutmann method ( http://en.wikipedia.org/wiki/Gutmann_method ) for example to wipe the disk. This method uses a specially designed order of different patterns to destroy the data. Personally I don't think this is really neccessary, because the high density of todays magnetic storage systems in combination with one write cycle of pseudo random data should be enough make it nearly impossible to reconstruct the data using a realistic amount of time and effort.&#13;
&#13;
greetings&#13;
Jakob </description>
      <author>Jakob</author>
      <pubDate>Mon, 10 Nov 2008 18:25:02 +0000</pubDate>
    </item>
    <item>
      <title>rac at Mon, 10 Nov 2008 15:35:26 +0100</title>
      <link>http://westhoffswelt.de/blog/creating_a_transparently_encrypted_root_filesystem.html#comment_1</link>
      <description>Hy&#13;
I was just flying trough your post and it looks quite impressive, good work.&#13;
Question about Step 8:&#13;
You wrote that filling it with 0 makes no difference.&#13;
As I see this is the initial overwrite all phase where the data that was there should be overwritten and I thought that it would be recoverable, if it's just set on LOW (0),  with special equipment...&#13;
Of course the Data from the encrypted partition will fill up the disk with random look-a-like data but some old data would be left hiiden behind the LOW bit's for some time.&#13;
Or what do you think?&#13;
&#13;
PS: Hab deinen post in die related links genommen da er sehr informativ die Hintergründe erklärt.&#13;
Eigentlich hätte ich das ja auch so machen müssen, deswegen wurde es auch nur ein install log ;-)</description>
      <author>rac</author>
      <pubDate>Mon, 10 Nov 2008 14:35:26 +0000</pubDate>
    </item>
  </channel>
</rss>

