On 09/07/2013 at 01:44, xxxxxxxx wrote:
Hi guys.
Can you help me protecting me PYP file? I have a plugin that will be finished really soon, so I am thinking of making it protected. I know I can go Script -> Source Protector and it will produce PYPE file.
However, I read somewhere that PYPE files are easy to crack. Is that right?
So do you know any other way to protect source code? Thank you.
On 09/07/2013 at 02:20, xxxxxxxx wrote:
I haven't heard of any decryption for the PYPE encryption yet. Which doesn't mean it isn't possible
to decrypt it, but you'd need to invest a lot of time. There are some other ways to protect your
plugin, but I wouldn't say they are more secure since part of it still relies on the PYPE encryption.
-Nik
On 09/07/2013 at 02:41, xxxxxxxx wrote:
why has it to be a pype file ? i personally rarely use the pype files for more than implementing a loader, the rest goes into seperate py(c) files. it is very difficult to implement obfuscation in python due to its nature as an interpreted language and the restrictions of python byte code. thre are some ways, see link below for more. another approach is using pythons zip feature (python modules can execute from a password protected zip file). the general weakness of that approach is usually the password handling. but on the other hand i don't see how decompiling python byte code is meant to be easier than some weak obfuscation / encryption measurements. people who can decompile python byte code can also use a decomplier to fetch password arguments or reverse engineer some encryption methods.
read more here :
http://stackoverflow.com/questions/261638/how-do-i-protect-python-code
http://docs.python.org/release/2.6.4/library/zipimport.html?highlight=zip module
On 11/07/2013 at 23:58, xxxxxxxx wrote:
Originally posted by xxxxxxxx
I haven't heard of any decryption for the PYPE encryption yet. Which doesn't mean it isn't possible
to decrypt it, but you'd need to invest a lot of time. There are some other ways to protect your
plugin, but I wouldn't say they are more secure since part of it still relies on the PYPE encryption.-Nik
Our lon-lat plugin was cracked very quickly and we were told very easy due to the nature of Python being an interpreter.
Look at it as a compliment when your plugin is cracked.
Professional buyers will buy it anyway.
See also this series of articles: http://c4dprogramming.wordpress.com/2012/12/21/licensing-plugins-part-i/#more-623
Pim
On 12/07/2013 at 00:36, xxxxxxxx wrote:
Hi Pim,
Ay, that's bad news. Sure I knew it was possible, but I haven't heard of any plugin in the Python
4D district having been cracked up until now. I mean, no matter how much you protected your
plugin, it'll always be cracked (with the respective anmount of work) if they really want to. But
as you said, professional buyers will buy it anyway so I don't care about if it was cracked or not. Its
only important that when you sell a plugin, it will not just run on every machine but restrict it to
the C4D license or something als.
Cheers,
-Nik