Closed Thread Icon

Preserved Topic: Not really web... (Page 1 of 1) Pages that link to <a href="http://ozoneasylum.com/backlink?for=20978" title="Pages that link to Preserved Topic: Not really web... (Page 1 of 1)" rel="nofollow" >Preserved Topic: Not really web... <span class="small">(Page 1 of 1)</span>\

 
DmS
Paranoid (IV) Inmate

From: Sthlm, Sweden
Insane since: Oct 2000

posted posted 06-11-2001 09:57

but, they want to know here at the office if there is some ready made proggies that does this:
I've got a VB application and I'd like to have a twin-version of the installation package, one for the whole paid-for-shebang and one eval-version, you know, the good old 30-day trial version to choose between.

Or, just one separate eval-version.

Thanx.
Dan



mr.maX
Maniac (V) Mad Scientist

From: Belgrade, Serbia
Insane since: Sep 2000

posted posted 06-11-2001 21:35

The best protection is the one that is implemented in the program itself. Doing that only in the setup can make your program very easy to crack...

DmS
Paranoid (IV) Inmate

From: Sthlm, Sweden
Insane since: Oct 2000

posted posted 06-11-2001 23:24

Yup mr.Max, I agree.
As it is, it's an Access application built by another party for our company, we don't want to work with them anymore, and they "didn't know how...", so we're stuck with either rewriting the sourcecode, or go the easy way.

I'm getting the code in a couple of days and I'll take a look then, but it would be nice to know if there is such an install package.
Dan

mr.maX
Maniac (V) Mad Scientist

From: Belgrade, Serbia
Insane since: Sep 2000

posted posted 06-12-2001 08:10

Most setup builders should be able to password protect specific components that get to be installed, but as I've said that's not reliable...

kevincar
Paranoid (IV) Inmate

From: north hills, ca usa
Insane since: Apr 2001

posted posted 06-12-2001 08:37

You have to consider your licensing strategy.
I think the easiest way would be to build a set of
registry entries with GUIDsthat have the ol ' "security through
obscurity" strategy - i.e., some bizarre half-baked, half-cocked GUID-based variable string, like 356454gdfgdfhfj4r6474dfdbf-65etvcnn, that
have equally bizarre values-
Your "crippled" version would function in a crippled fashion
without these REGEDIT entries... Your "paying customers" would get
the full-treatment with these values.

How do they get added securely?
The most common strategy is a VB DLL that is either present or not
present at the beginning of installation... This DLL makes the HKEY
registry pairs. The "classic" tech tip for adding registry entries in VB can be found here .

But hey -- that's only the BEGINNING. Heh - If your app is an "Add-on"
to Office 2K/XP, you need to follow THIS tech tip, and THIS one too.

Sorry I have to quit, but I'm starting to feel brain damage after reading Q238228. Have fun.



DmS
Paranoid (IV) Inmate

From: Sthlm, Sweden
Insane since: Oct 2000

posted posted 06-12-2001 11:51

Ok, thanx Max & Kevin.
I've got the basic idea down, that's good enough for now.
I'll see how we will approach this as I get the source-code.
/Dan

« BackwardsOnwards »

Show Forum Drop Down Menu