Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
I think that there is a way of doing it by using Maya to protect the code and not Python as suggested in other websites - a way which should be very hard to reverse engineer.
I will start working on it after I get at least _10 votes_.
How 'bout 6 votes? ;) I didn't know this was possible. I write plenty of python tools but haven't had time to make the jump to C++, which was originally the only way I was going to sell them to keep my code more secure. What a great little tool!
Python obfuscation tools exist already, but python is HARDER to entirely obfuscate than mel is.
It is pretty easy to deduce your code anyway unless its a node.
Essentially having the code protected is just a small hassle to anybody who would REALLY want to know how to do your code anyway, its not like the protection works for anybody seriously interested. Simply you can not protect code it must be readable at one time or another. (but if it can still be obscure)
And off course it makes it much worse for your end user. Basically thats whet the law is for. So if you want protection write something thats actually worth having your support. As a interesting side note this is why you can find cracks to all software that are worth pirating.
So in essence if your code is long, doing something useful and priced right then its protected intrinsically. if its short then its always easy to reverse engineer unfortunately, no matter how un-obvious it would be. However is it legal is another matter.
Protection can make it harder, but basically needing protection either tells that you don't trust your clients, or that your code sucks in some way or another that makes it a attractive target for misuse. In which case you have already failed somewhere else. So mostly people pay for the convenience of having something that they can work on right now, if they would have the time and effort to even begin to bother to break your code you'll be screwed anyway.
Actually we're not talking about obfuscation here as this is, as you've said, limited and can be compromised in one way or another. The idea behind Python protection is that the code is encrypted.
This can only be done within the confines of a specific run-time environment such as Maya.
kjaft
Comments on this feature request:
Rainrock said about 14 years ago:
Rainrock said about 14 years ago:
kurianos3d said about 14 years ago:
nicholasguan said about 14 years ago:
Strongwings said over 13 years ago:
Rainrock said over 13 years ago:
Joojaa said over 13 years ago:
Rainrock said over 13 years ago: