Add support for building TAILS images with persistent mode

[hellais]

It is a desired feature to have the image creation process output a TAILS image with persistence mode.

I believe the best approach of achieving this would be as follows:

Format the drive with 2 partitions. The first one should be a FAT32 formatted partition that contains all the TAILS related stuff. The second partition should be ext4 formatted. It must be full disk encrypted and it will contains all of the users home.

The TAILS part of the image should be custom built as per #5 and it shall include a small script that at startup symlinks the users home to a directory stored on the encrypted partition.

[cryptomule]

Upgradability:

Does this mean that the "TAILS-OSX" script will recognize the currently installed TAILS version (.2) on the USB key, so if the script is run after a complete setup for a second time, it will allow you to replace (.2) with (.21), while keeping your EXT4 partition intact? Just like how the script recognizes when the tails.iso is manually added to the /BOOT folder instead of going to the internet and fetching a copy...

Off topic but another quick question:

If this script was used and adapted for other less security conscious distributions, one's that required a lot of constant package updates, (ex. Kali Linux) could you create a persistent USB environment without having to create two partitions by...

• Would I simply need to change "Line 7" of grub.cfg to "persistent" instead of "nopersistent"?

[cryptomule]

Can you implement the suggestions of @qnrq in this post? http://grugq.tumblr.com/post/60464139008/alternative-truecrypt-implementations. cryptsetup + tomb

http://www.cyberciti.biz/hardware/howto-linux-hard-disk-encryption-with-luks-cryptsetup-command/

You want to dd if= either /dev/random or /dev/urandom instead of /dev/zero as the guide says though.