@ denisT, did you see my Edit?
That’s a fair point Denis.
But I’m quite sure ADSK would seriously refrain from stealing your “code” (they could steal your idea, though So if it’s good, you better patent it!), from the legal perspective (this would be a major legal bomb dropped on their lap) and from the practical perspective (they already have so much code to deal with, so much work, imagine if they would be digging through people’s Maxscripts to steal their code and call it a day).
If the past (AFAIK) serves of anything, they prefer first to get in touch with the developers and offer a deal to work with them, or sell the code to them. It’s far safer since it avoids the legal headaches.
Of course, I do not believe that Autodesk sifts all the garbage packed into MSE to find pearls there
About the malicious code being hidden inside maxscript, yeah, it is possible, but that entitles one to release a decryption mechanism because of that?
1 – Most of the users will never know how to differentiate between good and malicious code – even if it is decrypted and visible to them.
2 – People who can differentiate good, bad and malicious, probably can circumvent the encryption already, so nothing to win for them here.
3 – Having such tool released would not prevent from malicious code to continue to be written, and would also not protect the common user from those type of codes.
The initiative to protect the user from malicious maxscripts should come from ADSK, but then again, what is the potential gain (from a hacker POV) to learn MAxscript and write some malicious code exploring its vulnerabilities? And what are the potential gains to to the same to other softwares (browsers, games, text editors)? Would you be willing to have development resources (the money you pay ADSK) being applied to make MAxscript more robust on the security side? Potentially making tools and subtools to scan Maxscripts for vulnerabilities?
of course!
there is no such thing as encryption in Maya scripts development for example
I want say it again – the MXS encryption was very bad idea and must be stopped! All MXS scripts have to be free and opened.
Many developers can say – “WTF, I spent months looking for this solution, and I have to post it free, haven’t I?”
Yes… Or find another way to deliver the code
I understand where you’re coming from (or better yet, where you wanna go to).
But this decision you’re thinking about making is too serious to be made by one person because that person can do it. Even if the underlying reasons are sound. Why? Because you will be hurting people who have nothing to do with the wrongdoings (stealing code, or hiding bad code).
This should be part of a larger discussion, with the involvement of many more people. But that’s just a thought from someone who can’t touch your feet coding wise, so take that for what it’s worth.
Don’t worry… Of course I will never post a MSE decrypter public.
I just want to say it again – The MSE encryption is WRONG. It kills third-party MAX tools development
I like it. Because my learning of scripts is it analysis how other do the things. I’m not coder, mostly I’m artist but some times needs small maxscript tools to achieve a goal.
BTW Spend 5 min in google allows you to find free decrypter for .mse… so, use or not is mostly ethic problem not technical…
it’s a sad conclusion… I’m here for many years giving an examples, trying to teach max coding… my private mail-box is always full.
I know you are! You have helped me (and many people I know) in many many instances! Don’t look down on this, it’s just that coding is not everyone’s thing!
Just like modeling (or any other area), there are people who model REALLY well, with perfect loops and geometry density, and those who make models that pass as OK-ish, even though if you look at the wireframe, it’s a complete mess.
So, I admire your skills, and I know it’s not something that you learn from overnight. Many stuff you must have build up from sheer experience, trial and error, and digging on uncharted (undocumented) stuff It’s not easy to get to your level (even close to it) but I see some people walking the same avenue, and becoming quite good coders themselves. It just takes time, and the notion that this is not for everyone, so you can’t have too high expectations, or force it. People are just different
I guess you have fair points on your side, and I can agree with them.
But I’m not a user of MSE (I don’t encrypt, and AFAIK I only have 5 MSE in my script folder (that I rarely use, if ever). But this conversation have to happen with other devs, so we can hear and weight their perspectives as well. I appreciate your initiative to tackle this. Maybe the Ideas forum is the place for that? So maybe in the future ADSK strips this feature entirely?
i delivered more than 300 tools for my clients. the tools were never been encrypted. sometimes my clients asked me, what if we use outsource and don’t want to share code which we paid you…this is not my business.