Tuesday, February 8, 2011

Encrypting Source Code

I work on relatively sensitive code that we wouldn't want falling into the wrong hands. Up until now, all the code has been keep in house so it hasn't been an issue. I am moving to working from home a day or two a week and we want to secure the code on my laptop.

We have looked at a few alternatives, but Windows EFS and Bitlocker seem to be the most obvious. The laptop doesn't have TPM hardware, and I won't have access to Active Directory from home, so EFS looks to be the option.

Basically, does anyone else have any alternatives, or issues with using EFS to encrypt source code?

  • The last time I did this was a few years ago, but we used PGPdisk. It did a good job.

    From nsayer
  • Truecrypt

    hangy : Agreed. An encrypted TrueCrypt partition should also be fast enough not to slow down compilation process etc..
    Sunny : Just be sure to place the page file also on that partition.
    Martin Beckett : You can also set windows to clear the pagefile on shutdown instead.
  • You should look into TrueCrypt. It's free, open source and supported on a number of platforms.

    From QAZ
  • You should consider using truecrypt. It would accomplish the same thing, and be a bit less invasive to your system.

  • I would also recommend Truecrypt

    From PostMan
  • TrueCrypt, there's no excuse to use anything different. It's secure and it's free...what more could you want.

  • +1 for TrueCrypt. We use it at work, it's great.

    Tip: it seems that if you have a big codebase and you work with multiple working copies checked out simultaneously, you get much better performance if each working copy is on its own encrypted partition.

0 comments:

Post a Comment