🚀 go-pugleaf

In message <na.ec74224873.a70260astoneha@argonet.co.uk>
          GIJoe <astoneha@argonet.co.uk> wrote:

> Hiya
> 
> I'm currently working on a program that I am hoping to release as comercial
> software.  The main part of the program is finished (its at version 0.05
> atm).  The program can have other programs added to it that adapt the output
> of the original program I've been calling these add-on apps and have written
> 2 so far.  Now what I am looking for is 2 add-on apps or one that can do
> both of the following:
> 
> 1.  Encrypt all of the files and allow for them to be decyrpted later so    
>     that none of the files can be copied.
> 
> 2.  Have a credit scheme so that it can only be installed once.
> 
> The program I am working on is a program that makes installers for other
> peoples programs thus it is a high end solution to speed program development
> and allows you to install mainly into the !Boot structure the files that are
> needed but I have extended the idea through an add-on app that creates a
> save box interface onto the installer.
> 
> The encryption and credit scheme program(s) are a little above me as I have
> no idea how to encrypt files.  There may be some money given to the author
> of such an add-on app depending on whether the entire program becomes
> commercial or not.  I can give full details of the add-on apps format by
> e-mail so if anyone is interested in taking this on then please e-mail me
> ASAP. 
> 
> TIA
> 
> Allan :-)
> 

I don't think one can write a one-shot installation scheme that many of the
people who frequent this newsgroup couldn't hack. One can write such a
a scheme that will work for naive users and also one that will resist
some, but not all, means of copying the installation disc prior to
installation. So how much security do you want to claim for this scheme?
You'll find that any kind of copy-protection/security/privacy claim that you
make for a software product makes a disappointing selling point if your
claim is anything less than __absolute__. (Irrational, I know).

Bear in mind also that a one-shot installation scheme really also has to
embrace some method of __deinstallation__ that gets the user back to
pristine, uninstalled distribution media, but at the same time doesn't
defeat the purpose of the scheme. You cannot commit a user to installing
the software, right first time, on a single machine, for ever, unless maybe
you are only targeting games. If you do, all of your few customers will
quickly learn to hate you. The need for a sufficiently secure method of
deinstallation complicates matters considerably.

'Quota' systems, i.e. N legal installations from the original media, have
the same sort of security status and are not intrinsically harder to
program but are N times more unwieldy from a system administrator's point
of view.

As to encryption: What exactly is supposed to be achieved by the encryption
system? How do you think of it as working to protect anybody's investment
in the software?

   
 
-- 
Mike Kinghan,
Turing Tools, 20 Don Bosco Close, Temple Cowley, Oxford OX4 2LD
Tel. 01865 438231
`The truth is rarely pure and never simple' - Oscar Wilde
`Guinness is rarely pure and never ample' - Ned Kinghan