Source code protection not working in 0.8.x

[Roger]

Hi,

The experimental feature "Source code protection" is not working in
node-webkit 0.8.x.
https://github.com/rogerwang/node-webkit/wiki/Protect-JavaScript-source-code-with-v8-snapshot
. The compiled binary code in snapshot comes with the source code.

So please stop using this feature with 0.8.0-0.8.4. In future, please
always check the functions is being protected before you release your
application, by checking it in devtools , or with
"Function.toString()".

I'll try to fix this in 0.8.5 and 0.9.0.

Thanks,

Roger

[Maximilian Stroh]

Wouldn't it be better if you separate you important business logic from the presentation code, encrypt it using node.js' crypto module before distributing, and hand out the "unlock"-key separately? But i think even then, the devtools are the dealbreaker for any "secure" encryption.+, right?

[Roger]

Maximilian Stroh <hisak...@gmail.com> writes:

> Wouldn't it be better if you separate you important business logic from the
> presentation code, encrypt it using node.js' crypto module before
> distributing, and hand out the "unlock"-key separately? But i think even
> then, the devtools are the dealbreaker for any "secure" encryption.+,
> right?

Right.

But with the snapshot feature in node-webkit, the source code is not
there because it's been compiled to native. When you try to see the
source code in devtools it will reports "native code".

--
Roger

[Roger Wang]

It's fixed in 0.9.x now.

Roger