OpenEuphoria

Re: Proprietariness or levels of it, anyway

• Posted by gshingles <gshingles at ?mail.co?> May 25, 2008
• 703 views

Mike777 wrote:
> 
> Right.  Which is why I am interested in what people have as a favorite
> mechanism,
> because I know that it is useless to try and write the perfect concept into
> code, as there isn't anything of the sort.
> 
> I definitely think that, for the most part, the folks are honest who will buy
> what I might sell.  It is their employees that I'm most interested in ensuring
> don't do something their bosses would dislike.  Just a little protection is
> required, not a 24-hour German Shepherd who hasn't been fed for a week.

One method I have used in the past (with spreadsheets actually :) is to place
the critical data on a server in a 'hidden' share. This prevents casual copying
and taking away of data, since the uninformed user won't know about the extra
step involved, but still won't prevent someone who knows what they are doing
getting the data.

Another avenue might be to use PGP encryption to verify license files. That's
still vulnerable to direct binary hacking but probaly hard to defeat without
resorting to that (especially if the binary md5sum is checked as well).

For example (and I'm not a crypto expert) if your license is signed by bob's
private key (they author) and the binary is signed by the same key then the
license is valid?  Even better I suppose would be to sign the license with
alice's (the user) public key and only run if the executable is signed (somehow,
in Euphoria) with the same key?

I don't know, just thinking at my keyboard :)

Gary