Heya, With python there is no real way. Pyc files can be decompiled easily to their original form.
I'd say all you can do is put up a few hurdles to make it not a too casual thing. If someone can use them and Knows what he is doing he can take them. You'll have to live with that I guess. Locking down machines and getting rid of Internet helps I'd guess. Regards, Thorsten Thorsten Kaufmann Head of Production ________________________________ Mackevision Medien Design GmbH Forststraße 7 D-70174 Stuttgart T +49 711 93 30 48 59 F +49 711 93 30 48 90 M +49 151 19 55 55 02 thorsten.kaufm...@mackevision.de http://www.mackevision.de Geschäftsführer: Armin Pohl, Joachim Lincke, Karin Suttheimer HRB 243735 Amtsgericht Stuttgart ________________________________ F_BOX picture shooter 2.0: High-End-3D as a web service Erfahren Sie mehr: www.mackevision.de/de/technology/f_box_produkt_familie/picture_shooter.html<http://www.mackevision.de/de/technology/f_box_produkt_familie/picture_shooter.html> Read more about it: www.mackevision.de/en/technology/f_box_product_family/picture_shooter.html<http://www.mackevision.de/en/technology/f_box_product_family/picture_shooter.html> ________________________________ Von: nuke-python-boun...@support.thefoundry.co.uk [mailto:nuke-python-boun...@support.thefoundry.co.uk] Im Auftrag von Sebastian Elsner Gesendet: Montag, 25. März 2013 15:53 An: nuke-python@support.thefoundry.co.uk Betreff: Re: [Nuke-python] Pipeline Enclosure - while working with freelancers Have no Internet on your machines, and block all USB, Firewire whatever. If you want nuke to read the scripts its pretty likely that the user will also have the permissions to read them. Maybe one could play with linux permissions... You can also just place the .pyc files on the nuke path. On 03/19/2013 04:13 PM, Marc Gutowski wrote: Dear Forum, how do you keep your pipeline scripts accessible, but not getting copied ? i want to keep the nuke script pipeline safe from future short term freelancers, which work in competitives companies (producing the same product) too. For the automotive visualisation, i've created several routines which cut an excessive amount workamount of nuke-scenehandling, which i don't want to get copied. How to ensure this ? We load currently our scripts from one network location. Our system-wide platform is windows. we use user account and user right to hide and protect folders from unpermissioned acces. for any solutions, hints and suggestions i am very thankfull. best regards, marc ________________________________ www.ewok1.com<http://www.ewok1.com> _______________________________________________ Nuke-python mailing list Nuke-python@support.thefoundry.co.uk<mailto:Nuke-python@support.thefoundry.co.uk>, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python -- check out www.pointcloud9.com<http://www.pointcloud9.com> Sebastian Elsner - Pipeline Technical Director - RISE t: +49 30 20180300 flor...@risefx.com<mailto:flor...@risefx.com> f: +49 30 61651074 www.risefx.com<http://www.risefx.com> RISE FX GmbH Schlesische Strasse 28, Aufgang B, 10997 Berlin c/o action concept, An der Hasenkaule 1-7, 50354 Hürth Geschaeftsfuehrer: Sven Pannicke, Robert Pinnow Handelsregister Berlin HRB 106667 B
_______________________________________________ Nuke-python mailing list Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
