- This topic has 1 reply, 2 voices, and was last updated 8 years, 5 months ago by .
Viewing 2 posts - 1 through 2 (of 2 total)
Viewing 2 posts - 1 through 2 (of 2 total)
- You must be logged in to reply to this topic.
Welcome to GPLDL - we are still beta - please report any bugs via the contact form.
What is your stance on GPL plugins that have obfuscated code? It is not a split license, all of the plugin code and resources are GPL 2.0.
It is apparently not a violation of GPL license to obfuscate one’s code. Therefore it must be just as legal to post instructions on how to deobfuscate or bypass the obfuscated code in cases where there’s API keys or licenses being checked against.
Would you consider hosting that type of GPL plugin?
Obfuscated code is a problem, because you never know what you get. As long as it is licensed under the GPL, it is fine to deobfuscate the code and/or post instructions how to do so. It is different though, if you deobfuscate it, alter the original file and then release it under the same name, because it is not the same thing. If you release it under a different name, that is fine as well.
We only consider providing GPL plugins that we receive as 100% originals from the developers to ensure that there is no malware or other things included that threaten our users security.