As already pointed out above, there is no reliable way other than compiling (using cython), to protect your source code.
Here's a crazy idea, and I am just thinking aloud so this might sound stupid - - Why not encrypt all your python code as plain text files. - The source files can be decrypted only with a key. - Write a layer between the client and the source code that does the decryption using the key. This layer can be conveniently compiled once using cython. - The client code loads the libraries dynamically using the encryption layer. - Any updates to the library source code can be done by writing the source code in python and decrypting it using the decryption layer. This does not solve the problem entirely but simplifies it to a certain extent. You have to secure one and one only thing - The encryption-decryption source code. The encrypt-decrypt layer is to be designed in such a way that it can not run outside the studio of the environment. There are many ways to do this using the mac-addresses etc. This could even be written in C/C++ Again, just as a huge caveat - This is not a well-thought approach, it just occurred to me and instead of making notes somewhere else I am writing it in the mail. On Mon, May 15, 2017 at 7:22 PM, Justin Israel <justinisr...@gmail.com> wrote: > > > On Mon, May 15, 2017, 9:10 PM Rudi Hammad <rudiham...@gmail.com> wrote: > > So if they make it only readable, no one can copy it to an external usb >> or send to their personal emails the files etc.. >> > > If people are allowed to read it for import, then your only way to address > these specific concerns is to prevent mounting of attached storage to the > workstations, and to disable external internet access on the workstations > that can mount these production locations. > > From a code standpoint, as mentioned in previous mail threads, you could > go about adding a license checkout but that would only work well for > compiled python extensions and not py, pyc, pyo. > > >> -- >> You received this message because you are subscribed to the Google Groups >> "Python Programming for Autodesk Maya" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to python_inside_maya+unsubscr...@googlegroups.com. >> To view this discussion on the web visit https://groups.google.com/d/ >> msgid/python_inside_maya/42429ff3-f031-414e-8508- >> b7f119ba413d%40googlegroups.com >> <https://groups.google.com/d/msgid/python_inside_maya/42429ff3-f031-414e-8508-b7f119ba413d%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- > You received this message because you are subscribed to the Google Groups > "Python Programming for Autodesk Maya" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to python_inside_maya+unsubscr...@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/python_inside_maya/CAPGFgA24TtnJZVm3SRcM_qCUpAZ_ > EttXbZt0fMzOEN3Jw%2BiGCA%40mail.gmail.com > <https://groups.google.com/d/msgid/python_inside_maya/CAPGFgA24TtnJZVm3SRcM_qCUpAZ_EttXbZt0fMzOEN3Jw%2BiGCA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to python_inside_maya+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/CAPaTLMR9w6a%3DBeZCMvKvdN0YHnuqAkCCi3tzj2O1cRzo-gUYfg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
