Path: news.mathworks.com!newsfeed-00.mathworks.com!newsfeed2.dallas1.level3.net!news.level3.com!postnews.google.com!b25g2000prb.googlegroups.com!not-for-mail
From: Nathan <ngreco32@gmail.com>
Newsgroups: comp.soft-sys.matlab
Subject: Re: protecting MatLab code from being pirated?
Date: Wed, 16 Sep 2009 12:44:34 -0700 (PDT)
Organization: http://groups.google.com
Lines: 29
Message-ID: <44ef6f34-36a2-42bf-bc46-f0b7353e479b@b25g2000prb.googlegroups.com>
References: <0925d8cc-0669-4057-9ce0-04ccf1b627a4@d21g2000vbm.googlegroups.com>
NNTP-Posting-Host: 198.206.219.34
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Trace: posting.google.com 1253130274 2005 127.0.0.1 (16 Sep 2009 19:44:34 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Wed, 16 Sep 2009 19:44:34 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: b25g2000prb.googlegroups.com; posting-host=198.206.219.34; 
	posting-account=_KeVcAoAAAB7j3xn35ujaQ0BoQhuzwJP
User-Agent: G2/1.0
X-HTTP-Via: 1.1 wwwproxy-son-ca-02.ca.sandia.gov:80 (squid/2.5.STABLE14)
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.3) 
	Gecko/20090824 Firefox/3.5.3,gzip(gfe),gzip(gfe)
Xref: news.mathworks.com comp.soft-sys.matlab:570896


On Sep 16, 12:40 pm, stpatryck <stpatr...@gmail.com> wrote:
> Hello All,
>
> I'm supposed to write a portfolio optimization Monte Carlo simulation
> for some foreign mutual fund company on an advisory basis.  They have
> MatLab and want me to ship my code to them so they can run it over
> there.  I'm wondering how I can code some kind of protection for my
> MatLab programs so they don't just take it and cut me out of the
> picture.
>
> Is there a way to make the code unusable if they try to modify it?  Or
> some way I can put in some code so they can only run my progams until
> a certain expiration date?
>
> Any suggestions would be appreciated.

You can send them p code. That way, they can only use your code
without being able to see its contents.
doc pcode

Note: Create a backup of your file(s), because there is no going back
once you convert it to pcode.

This way, if they want to modify the code, they will have to contact
you and have you modify it for them.

Will this work for you?

-Nathan