Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #78452
| From | alister <alister.nospam.ware@ntlworld.com> |
|---|---|
| Subject | Re: Obscuring Python source from end users |
| Newsgroups | comp.lang.python |
| References | <89381545-5edc-4f85-a4b8-86eebfdf34ee@googlegroups.com> |
| Message-ID | <KX8Wv.342593$9I4.336453@fx35.am4> (permalink) |
| Organization | virginmedia.com |
| Date | 2014-09-29 08:42 +0000 |
On Mon, 29 Sep 2014 00:36:47 -0700, norman.ives wrote: > Hello list > > Python 3.4 applies. > > I have a project that involves distributing Python code to users in an > organisation. Users do not interact directly with the Python code; they > only know this project as an Excel add-in. > > Now, internal audit takes exception in some cases if users are able to > see the source code. > > So I'm wondering if anyone has clever suggestions in this regard... > > My current plan is to modify the bdist_wheel setuptools extension so > that it can produce distributions with only the .pyc files, laid out so > that they will be importable in the normal way. This will be sufficient > to satisfy internal audit, and will not negatively impact our users. > > However there are obvious downsides, including the overhead of > maintaining separate wheels for different architectures and (in the > future) Python versions. Not to mention that this plan seems to go > against the grain of how Python wants to use byte code files... > > Is there a better solution? For an internal app. I would suggest it is only necessary to protect user- names & passwords to back end services (databases etc.). storing these in a separate file in an encrypted format should be enough to discourage internal users from digging deeper. This will not stop a determined hacker but neither will any other forms of obfuscation. -- new, adj.: Different color from previous model.
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Obscuring Python source from end users norman.ives@gmail.com - 2014-09-29 00:36 -0700
Re: Obscuring Python source from end users Chris Angelico <rosuav@gmail.com> - 2014-09-29 17:52 +1000
Re: Obscuring Python source from end users norman.ives@gmail.com - 2014-09-29 01:41 -0700
Re: Obscuring Python source from end users Chris Angelico <rosuav@gmail.com> - 2014-09-29 18:55 +1000
Re: Obscuring Python source from end users Chris Angelico <rosuav@gmail.com> - 2014-09-29 20:14 +1000
Re: Obscuring Python source from end users alister <alister.nospam.ware@ntlworld.com> - 2014-09-29 08:42 +0000
Re: Obscuring Python source from end users Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-09-29 21:47 +1000
Re: Obscuring Python source from end users Sturla Molden <sturla.molden@gmail.com> - 2014-09-29 14:51 +0000
Re: Obscuring Python source from end users Dan Stromberg <drsalists@gmail.com> - 2014-10-01 15:06 -0700
Re: Obscuring Python source from end users Marko Rauhamaa <marko@pacujo.net> - 2014-10-02 08:17 +0300
Re: Obscuring Python source from end users Terry Reedy <tjreedy@udel.edu> - 2014-10-02 03:19 -0400
Re: Obscuring Python source from end users Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-10-02 17:22 +1000
Re: Obscuring Python source from end users Sturla Molden <sturla.molden@gmail.com> - 2014-09-29 14:53 +0000
Re: Obscuring Python source from end users Johannes Bauer <dfnsonfsduifb@gmx.de> - 2014-10-02 09:50 +0200
Re: Obscuring Python source from end users Chris Angelico <rosuav@gmail.com> - 2014-10-02 18:32 +1000
csiph-web