R14 Source Protector Flaw?
On 06/01/2016 at 15:00, xxxxxxxx wrote:
Why was the Python Source Protector changed from R14 to R15?
Was it vulnerable to hacking?
If so, should R14 be skipped for new plugins for people concerned about security?
On 07/01/2016 at 03:52, xxxxxxxx wrote:
for R15 the encryption methods got some improvements which were not downwards-compatible.
The developers want to point out that the purpose of the source protection is solely to prevent unwanted access to the source code by other users. It is not guaranteed that the protected source code cannot be accessed by proficient users or hackers. Python should not be used if your code must remain secret. See also the online documentation.
On 10/01/2016 at 23:26, xxxxxxxx wrote:
Understood. I've taken steps to thwart the hackers of your encryption already.
But, if you don't want to answer here, could you PM me about whether or not you feel as confident in the R14 encryption?
On 11/01/2016 at 02:07, xxxxxxxx wrote:
I don't have any detailed information about the R14 encryption. All I can say that both versions are not designed to assure any code security. One can only "feel" save with C++ plugins.