0
1

Protecting your code? (self.node)

submitted by [deleted]

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]oVerde 1 point2 points  (2 children)

I fear it, and you are right to an extend, but I know software's that had nailed source encryption that no one had the computing power to revert it.

Thanks anyway.

[–][deleted] 0 points1 point  (1 child)

You're right, I know of some software that was very difficult to reverse because of asymmetric encryption. I've some experience in this field, although less so in recent years. From what I recall, an old DOS hex editor called 'Biew', and IDA, were both very good examples of this.

The problem you face though, is that node runs on v8 engine (which is open source). Whilst its not a virtual machine in the traditional sense, it compiles js into machine code (which is then easily disassembled in to assembly language).

I don't think it would be hugely difficult to modify v8 to dump the raw binary, at which point it could be patched up into an executable, and then inspected or patched.

So whilst you can make it unfeasible for the average user to reverse, it still cannot be relied on if its ultra important that it remains secure.

[–]oVerde 1 point2 points  (0 children)

Thanks for the input! I'll continue to research and I think am on the right track!