Alex Fenton
8/28/2008 6:41:00 PM
Rock Roll wrote:
> Lex Williams wrote:
>> but,what if I don't want the end-user to be able to see the source code
>> of the script ?
>
> Ya. I too have doubt in the expose of .rb files to the end user.
>
> I installed Weft-Qda( www.pressure.to/qda/ ) which is s qualitative
> analysis software application which is built using ruby. After
> installation i saw the .rb files inside the installation directory. They
> could be easily changed by the user or if any hacker gets access to the
> user's computer..
Weft QDA's an open-source product aimed at end-users so the fact that
the source is accessible in the installation directory of the source
isn't a problem.
Even with a compiled product, if the user starts tinkering with the
program's files in C:/Program Files/ they might expect trouble, and if a
hacker has access to their local file system, they've got more to worry
about in general ...
It would be nice in some circumstances to properly obscure the ruby
source, but RubyScript2Exe definitely isn't it. It solves other problems
quite well though, even though for Weft QDA I've moved away from using it.
alex