From: Kris <kris@...>
Date: 2006-05-23T19:34:53+09:00
Subject: Re: Writing a interpreter extension

Hal Fulton wrote:
> Kris Leech wrote:
>> suggestions how to secure ruby (or other) code.
>> 
> 
> Oh, anything can be done... but is it worth it, and have you really
> accomplished anything?

It would be a layer of protection that would at least prevent casual 
attacks.

> 
> That's the source of the resistance you perceive. Most of us don't
> want or need what you describe.

Because you dont want it you resist its development..

> 
> I venture to say there are numerous people here who might put in
> some hours and achieve what you want. But the people who really
> understand cryptography (and I am not one) will not spend their
> time on an STO scheme.
> 
> As for coding... Most people are motivated only two ways to write code:
>    1. They're paid
>    2. The project seems cool to them
> 
> You're not paying (are you?) and people aren't convinced this is cool.

I'm not asking anyone else to do it.

> 
> Actually I remember *someone* making an obfuscator of some kind 3-4
> years ago... I played with it awhile and couldn't break it. Others
> could, though. Or I could given a few hours.
> 
> The best suggestion yet was to keep the code off the client machine
> and make a web service. That is relatively secure.

But that makes huge limits on profit. My feeling is web software can't 
be sold like desktop software is. Either boxed or a pre-installed 
server.

> 
> 
> Hal


-- 
Posted via http://www.ruby-forum.com/.