shipping python

[Chris Angelico]

On Thu, Oct 13, 2011 at 8:10 AM, Kristen J. Webb <kwebb at teradactyl.com> wrote:
> My main motivation to use .pyc is to keep end users from changing scripts,
> breaking things, and then calling us.  Tamper proofing may be an
> alternative approach if anyone has suggestions.
>

I wouldn't bother; if you're worried about that, try a tamper-evident
system rather than tamper-proof - for instance, MD5 checksums of
everything:

$ md5sum * >checksum.txt
$ md5sum checksum.txt
123412341234123412341234 md5sum

Save that meta-checksum and have an easy way to read it back - that
way, you can be sure they haven't just rebuilt the checksum file. If
that one checksum has changed, you know something else has; to find
out which:

$ md5sum -c --quiet checksum.txt

No need to restrict what you send out that way, and you can still get
a guarantee that they haven't fiddled with anything.

ChrisA