I suggest that wrapping it in an executable should be considered a social measure. Its a clear sign that you don't want people to poke in there, although it won't stop them if they try.
In addition to appropriate contracts & licenses as above, you might also consider adding a watermark to the code to identify who leaked it when it inevitably gets out in a few years. Then bill the culprit for the extra copies floating around and/or damages incurred (write that part into the contract of course).
The only way to actually prevent the code from leaking is to keep it on trusted hardware being accessed only by trusted people ... even then, you can't be sure they're trustworthy or the only ones with access, but that is closer to a physical security issue. It also sounds like it isn't practical for your purpose.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
