On Mon, Nov 26, 2012 at 3:39 PM, Ken Schaefer <[email protected]> wrote:
> Your answer assumes that the only reason the disk would go missing is > because someone specifically targeted the source code.**** > > ** > Well, xkcd is a comic strip, it just seems appropriate at times. > ** > > What if it was just an opportunistic theft? > Risk involved in trying to peddle the source to someone who a - could use it b - was unethical enough to. > Or if the disk stopped working, and you wanted to dispose of it?**** > > ** > Or the sectors were getting marked as bad (but still contained data) > ** > > Whilst FDE would have its risks (e.g. you forget the key), it’s a > relatively low cost way of mitigating a number of risks.**** > > ** > Doesn't FDE typically have an 'enterprise' key as well as a user key? A down side, as well, would be performance in doing encrypt/decrypt for every read/write to your disk. > ** > > Cheers**** > > Ken**** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *mike smith > *Sent:* Monday, 26 November 2012 3:27 PM > *To:* ozDotNet > *Subject:* Re: What type of Insurance covers using your own custom > developer machine at work place?**** > > ** ** > > On Mon, Nov 26, 2012 at 2:01 PM, James Chapman-Smith < > [email protected]> wrote:**** > > Hi Arjang,**** > > **** > > I can't answer your question on insurance, but I can't help to think that > you're potentially opening yourself up to legal issues. Even with checking > things in to an external machine you're still keeping source on your > personal machine – even deleting the files fastidiously would leave > temporary and/or "undeletable" files behind.**** > > **** > > I would suggest that you employ something like TrueCrypt to do whole drive > encryption (WDE) on your machine. I do that with mine and I know that it > really doesn't matter if my machine goes missing. The harddrive just > appears to be random garbage without my TrueCrypt password.**** > > **** > > If you do WDE you might find that you can happily leave the source on the > machine without any risk.**** > > ** ** > > ** ** > > You're transferring the risk.**** > > ** ** > > http://xkcd.com/538/**** > > ** ** > > I'd sooner leave it on the disk in clear.**** > > **** > > **** > > Just a thought.**** > > **** > > Cheers.**** > > **** > > James.**** > > **** > > **** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Arjang Assadi > *Sent:* Monday, 26 November 2012 11:51 > *To:* ozDotNet > *Subject:* What type of Insurance covers using your own custom developer > machine at work place?**** > > **** > > Anyone having to use their own (custom build) developer machines for work > know what type of insurance would be enough to cover the physical machine? > The machine is personal property, but the work carried on it is for work. > Checking out the code and checking it back in, never keeping anything that > belongs to work on it.**** > > **** > > There is a separate machine that belongs to work that keeps everything on > it.**** > > **** > > So at worst if the machine disappears it would be only the physical > property and nothing intellectual. **** > > **** > > **** > > Thanks for ideas and recommendation**** > > **** > > Regards**** > > **** > > Arjang**** > > ** ** > > ** ** > -- Meski http://courteous.ly/aAOZcv "Going to Starbucks for coffee is like going to prison for sex. Sure, you'll get it, but it's going to be rough" - Adam Hills
