From: Ryan Davis <ryand-ruby@...>
Date: 2008-09-24T15:10:33+09:00
Subject: Re: Protecting Ruby code


On Sep 23, 2008, at 16:17 , Mike Gold wrote:

> Unless you have rewritten ruby in a *serious* way via redesigning the
> AST.  The AST is buck-naked exposed in memory, flapping its genitals  
> for
> all to see.  And even if you did rewrite eval.c, (1) I would expect
> serious compatibility problems, and (2) your new AST could be
> reverse-engineered.

I was curious about that as well... zenobfuscate did its job without  
ever exposing itself via ruby internals. I don't know of another way  
to do this for ruby code. Unless their bytecode is bundled with an  
entirely separate VM to execute them? I still don't see that as being  
feasible.