On Friday, 27 June 2014 22:09:09 UTC-5, Sheyam S. wrote:
I am trying to implement my application in my client place and the
application is developed in Ruby on Rails.
Since I am going to deploy on their premise I wish to make the code as
encrypted can be compiled but not be able to view, use or copy.
How can I do that using open-source tools.
You can’t do that with ANY tools. Even “Ruby Encoder” can be reversed to
regenerate source code, as can alternative approaches (using Jruby and
compiling to .class files, etc). Even compiled machine code can be
reversed back into C:
If they can execute the code, they can reassemble it. You’re trying to
protect code by putting a lock on it and then GIVING THEM THE KEY.
Ultimately, it’s a question of effort: you can make extracting source
difficult, but never impossible.
Also, this is an enormous red flag (from Ruby Encoder’s FAQ):
“Some of our techniques, for obvious reasons, are not documented outside
our core team and this is to provide a hightened level of protection for
the Ruby or Ruby on Rails scripts.”
A basic rule of security: if somebody’s promising that their SUPER
ALGORITHMS can do something impossible, watch out.
Take the $199 and spend it on getting a good lawyer to write up a
that specifies strong penalties for stealing source - but realize that
enforcing such a contract will cost even more money.