thaitang
January 9th, 2013, 03:26 AM
Is it possible to create encrypted containers within an already encrypted device/hd?
I used truecrypt to encrypt a 1TB hd because my wife needs to access the hd onp her winblowz PC at work. I also had to create what I consider a less than secure passphrase to make it usable for my wife. No probs I thought since I was intending to simply create additional encrypted containers withing the encrypted hd to keep other files I would like to store on there more secure from prying eyes, especially if the hd will be lying around on my wife's desk at work.
I have tried using truecrypt to make an encrypted container on the encrypted hd, however, after the process begins and gets as far as 1-2% of creating a 100GB container the process bails out complaining the disk is unavailable. Yet it is still listed with a df command and available to ls commands and general browsing using nautilus.
Iniitially I did try to make an ext2 container (using truecrypt), and then thought that maybe b/c I encrypted the drive using vfat that I had to settle for containers fobrmatted using vfat, but that process bails out in a similar fashion as earlier attempts specifying ext2.
I used truecrypt to encrypt a 1TB hd because my wife needs to access the hd onp her winblowz PC at work. I also had to create what I consider a less than secure passphrase to make it usable for my wife. No probs I thought since I was intending to simply create additional encrypted containers withing the encrypted hd to keep other files I would like to store on there more secure from prying eyes, especially if the hd will be lying around on my wife's desk at work.
I have tried using truecrypt to make an encrypted container on the encrypted hd, however, after the process begins and gets as far as 1-2% of creating a 100GB container the process bails out complaining the disk is unavailable. Yet it is still listed with a df command and available to ls commands and general browsing using nautilus.
Iniitially I did try to make an ext2 container (using truecrypt), and then thought that maybe b/c I encrypted the drive using vfat that I had to settle for containers fobrmatted using vfat, but that process bails out in a similar fashion as earlier attempts specifying ext2.