On Friday, 27 June 2014 22:09:09 UTC-5, Sheyam Selvaraj 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: http://www.backerstreet.com/decompiler/decompilers.htm 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 more 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 of 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 SEKRIT ALGORITHMS can do something impossible, watch out. Take the $199 and spend it on getting a good lawyer to write up a contract that specifies strong penalties for stealing source - but realize that *enforcing* such a contract will cost even more money. --Matt Jones -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/f03da405-bd4e-49d3-b242-fbf56c65f5b0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
