![](https://seccdn.libravatar.org/avatar/f71dc8e161926779170632048a753c69.jpg?s=120&d=mm&r=g)
On Friday 16 June 2006 08:41, Roger Oberholtzer wrote:
One could encrypt the file system. This seems a bit much. Encrypting the files themselves is not feasible. There are a gazillion of them. (I counted.) Can you encrypt an existing file system? I suspect not.
As others have mentioned, I would created an encrypted partition large enough to hold the source code you want to protect. I've never used an encrypted partition in a production system, but I have toyed around with them a bit. Keep in mind that an encrypted filesystem is designed to limit access to the data it holds, and this can come back to bite you when you upgrade OS's, move the encrypted filesystem to another partition, or another location on the same filesystem, lose the password, something gets corrupted, etc. Keep recent backups. I would also keep a unencrypted diff between the master subversion repo and my checkout on the laptop. That small set of changes won't be a huge help to an attacker, but it will protect your changes if something should happen to the encrypted filesystem. I also suggest you check out TrueCrypt. It is a Windows encryption program that is quite respected, and has recently been ported to Linux. I intend to try it out myself at my next opportunity. Regards, Mark -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com