How to disable the debug remote port in node-webkit desktop app

6 views
Skip to first unread message

fabrice...@gmail.com

unread,
Apr 18, 2014, 3:44:38 AM4/18/14
to node-...@googlegroups.com
I've posted this question on StackOverflow 

I've produced some pakaged applications without any constraint of confidence but for a new production I need to protect the source code included in the application.
I've seen that a port is open for remote debugging of the app with the command "netstat -a -o"  
And while this port is open, it's possible to see all the sources.

How can I disable this port in the packaged app ? I haven't seen any flags for this action.

Thank you in advance or your replies.

Anatoly Pashin

unread,
Apr 18, 2014, 3:52:45 AM4/18/14
to node-...@googlegroups.com
Even if you don't include 'remote-debugging-port' option, remote debugging is enabled and the port is randomized.
Checked latest Chrome on Windows: remote debugging port is not created without flag.

Nice you noticed this, time to read sources of node-webkit to find solution or call Roger Wang.

ps. how your .exe is protected and created? If someone will need sources, he'll get it anyway. You'd better use v8 snapshots.


--
You received this message because you are subscribed to the Google Groups "node-webkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-webkit...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Пашин Анатолий,
эникейщик.

fabrice...@gmail.com

unread,
Apr 18, 2014, 5:06:53 AM4/18/14
to node-...@googlegroups.com
Thank you for your answer, concerning my exe, it is protected using "Enigma Virtual Box". 
All the node-webkit files are packaged and compressed in the boxed exe file 
It's slower but not a problem for our prototype.

fabrice...@gmail.com

unread,
Apr 18, 2014, 5:40:52 AM4/18/14
to node-...@googlegroups.com, fabrice...@gmail.com
Ok, I've found the extracted sources, I thought it was only extracted in RAM and not physically on the hard drive...

I will try to use v8 snapshots, the first problem I've seen is that I use AMD mechanism with requireJS to optimize execution during loading time (for the final version). In the prototype needed as a Proof of Concept by our customer, I need to protect the sources, so I will modify my JS files to allow snapshot usage and make a test.

Anatoly Pashin

unread,
Apr 18, 2014, 5:47:23 AM4/18/14
to node-...@googlegroups.com

Bad news: even if sources were only in memory, you can extract them. The only solution for you is Opcode's, in case of node-WebKit it's v8 snapshot.

18 апр. 2014 г. 20:40 пользователь <fabrice...@gmail.com> написал:
Reply all
Reply to author
Forward
0 new messages