On Tue, Jun 28, 2011 at 12:21 AM, V G wrote: > On Mon, Jun 27, 2011 at 7:18 PM, Bob Blick wrote: > >> On Mon, 27 Jun 2011 18:37 -0400, "V G" wrote: >> > I didn't really look into this before, but it seems interesting: >> >> Dangerous work. One could say that code protection only keeps honest >> people honest. >> > > What do you mean? I presume his point is that you can't hide your code from the unscrupulous (and that only the unscrupulous would resort to such activities). The thing is, this is only new in so far as the details are now out on the net for any punter to try (if they have the facilities to decapsulate the chip). I'm sure this sort of thing has been going on in the commercial world (where it's worth them bothering) for ages. The trick then is setting up the separate teams to analyse the existing code and write a complete spec, and to rewrite the code to the spec, thus circumventing any copyright issues. Chris --=20 http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .