Re: [v8-users] Re: Protecting IP

a separate executable for each independent bit of javascript would become unmaintainable very quickly. From: Mike Schwartz <myk...@gmail.com> Sent: Monday, 27 June 2016 10:23 PM To: v8-users Cc: beethovian.symph...@outlook.com Subject: Re: [v8-use

Re: [v8-users] Re: Protecting IP

v8-users Cc: beethovian.symph...@outlook.com Subject: [v8-users] Re: Protecting IP Is there any way for an user run code on the node.js instance at all? I'm asking since node.js runs on the server, so the source is usually not accessible from outside. On Tuesday, June 14, 2016 at 3:33:35 PM UTC+2, Joe

Re: [v8-users] Re: Protecting IP

Maaf saya tidak kesengajaan saya. T.ksh Pada tanggal 27 Jun 2016 18.05, "Yang Guo" menulis: > Is there any way for an user run code on the node.js instance at all? I'm > asking since node.js runs on the server, so the source is usually not > accessible from outside. > > >

Re: [v8-users] Re: Protecting IP

It doesn't seem that hard to hack node to do this. You use something like nasm and include your packaged .js program. Then hack node to load and optionally decrypt your program and eval() it. Nasm generates a .o file you link your custom node with. Seems like a couple of hours' work. You would

[v8-users] Re: Protecting IP

This is actually a fairly common requirement that I've had the "pleasure" of dealing with for a host of people and firms. Unfortunately, it's also very easy to mess up without a lot of care. I have a longtime interest in reverse engineering so I may have a different standard of "trivial

[v8-users] Re: Protecting IP

Is there any way for an user run code on the node.js instance at all? I'm asking since node.js runs on the server, so the source is usually not accessible from outside. On Tuesday, June 14, 2016 at 3:33:35 PM UTC+2, Joe Bloggs wrote: > > Hi, > > My employer is looking to shift major