1. Proprietariness or levels of it, anyway
This may be a hornet's nest type issue, or it may be benign, but does anybody
have a favorite mechanism for making one's code proprietary? Other than a
commercial solution.
Thanks
Mike
2. Re: Proprietariness or levels of it, anyway
Mike777 wrote:
>
> This may be a hornet's nest type issue, or it may be benign, but does anybody
> have a favorite mechanism for making one's code proprietary? Other than a
> commercial
> solution.
>
> Thanks
>
> Mike
Study MicroSoft-- then you can learn not only how to make anyone's code
proprietary.
Ken Rhodes
Folding at Home: http://folding.stanford.edu/
100% MicroSoft Free
SuSE Linux 10.3
No AdWare, SpyWare, or Viruses!
Life is Good, 
3. Re: Proprietariness or levels of it, anyway
Mike777 wrote:
>
> This may be a hornet's nest type issue, or it may be benign, but does anybody
> have a favorite mechanism for making one's code proprietary? Other than a
> commercial
> solution.
I don't think it's a bad thing (this issue). I think just about everyone would
want to benefit financially from their efforts for at least some of what they do,
even if they are involved with other free software projects. After all, the more
they can support themselves financially the more free time they may have to
benefit other efforts.
That said, and even though I don't personally try to sell software, if I want it
to remain closed (perhaps for example in a commercial environment where you are
not specifically paid to write software) is only to release the compiled
translated to C program.
Even if you do release code, a carefully worded and placed license agreement
could help if you are in a position of being related to lawyers, or being able to
afford their services. :)
If you want to prevent copying of binaries then that's another story I suppose.
The fact that you could download and install a Microsoft operating system or
major product in less than an hour shows that no level of sophisticated copy
protection will be foolproof. Like my father always used to say "locks are to
keep honest people out".
I think the license is the most important, assuming you can catch who is
infringing on your proprietary rights, because at least then you have an
unabiguous leg to stand on.
Gary
4. Re: Proprietariness or levels of it, anyway
gshingles wrote:
>
> Mike777 wrote:
> >
> > This may be a hornet's nest type issue, or it may be benign, but does
> > anybody
> > have a favorite mechanism for making one's code proprietary? Other than a
> > commercial
> > solution.
>
>
> If you want to prevent copying of binaries then that's another story I
> suppose.
That is the story I'm trying to write.
> The fact that you could download and install a Microsoft operating system or
> major product in less than an hour shows that no level of sophisticated copy
> protection will be foolproof. Like my father always used to say "locks are
> to keep honest people out".
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.
Mike
5. Re: Proprietariness or levels of it, anyway
Mike777 wrote:
> gshingles wrote:
> > If you want to prevent copying of binaries then that's another story I
> > suppose.
> That is the story I'm trying to write.
Key each executable to the hard drive serial number. That way the executable
will only work on PCs with that particular serial number.
You can do it one of two ways: build a custom executable for each customer
after you get the serial number of the drive to which it will be installed,
or use an ini file (or registry or whatever) that uses a format like this:
----License File------------------------------------------
-- Do not tamper with this file or your license will be --
-- broken and you will have to purchase another copy. --
----------------------------------------------------------
>84753984573094
#849HW98FH9WFAKJSH08
The number after the bracket is the licensed PC serial number. The number
after the pound sign is a checksum of the contents of the license file.
Without the license file, the program doesn't work. If the person tries
to tamper with the license file, the checksum will not match and the
program won't work.
It has worked for me for 15 years.
6. Re: Proprietariness or levels of it, anyway
c.k.lester wrote:
>
> >84753984573094
>
> #849HW98FH9WFAKJSH08
>
> The number after the bracket is the licensed PC serial number. The number
> after the pound sign is a checksum of the contents of the license file.
> Without the license file, the program doesn't work. If the person tries
> to tamper with the license file, the checksum will not match and the
> program won't work.
>
> It has worked for me for 15 years.
What about Linux? I am sure the hd serial number must be somewhere, but does
that mean when I do an upgrade I can to call you and relicense my software?
--
Jeremy Cowgar
http://jeremy.cowgar.com
7. Re: Proprietariness or levels of it, anyway
Jeremy Cowgar wrote:
> c.k.lester wrote:
> > It has worked for me for 15 years.
> What about Linux?
We don't make stuff that works in Linux, but the same ideas apply.
> I am sure the hd serial number must be somewhere, but does
> that mean when I do an upgrade I can to call you and relicense my software?
Not only that, but you have to transfer that license... so, if you are getting
an upgrade, you uninstall first. Then we can put the license on the new PC. If
your hard drive dies... well... that's on a case-by-case basis. :/
8. Re: Proprietariness or levels of it, anyway
Mike777 wrote:
>
> This may be a hornet's nest type issue, or it may be benign, but does anybody
> have a favorite mechanism for making one's code proprietary? Other than a
> commercial
> solution.
>
> Thanks
>
Mike:
You can always put your code in a DLL or a SO library and ship the
application that accesses the dll in a bound exe.
Bernie
My files in archive:
WMOTOR, XMOTOR, W32ENGIN, MIXEDLIB, EU_ENGIN, WIN32ERU, WIN32API
Can be downloaded here:
http://www.rapideuphoria.com/cgi-bin/asearch.exu?dos=on&win=on&lnx=on&gen=on&keywords=bernie+ryan
9. Re: Proprietariness or levels of it, anyway
- Posted by gshingles <gshingles at ?mail.co?>
May 25, 2008
-
Last edited May 26, 2008
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
