Re: Using the registry
- From: Dodgy <Dodgy@xxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 26 May 2005 11:55:06 +0100
On Wed, 25 May 2005 20:23:30 +0100, "Jan"
<JanetMcDonald67@xxxxxxxxxxx> waffled on about something:
>Hi
>
>I have been using the old TurboPower Onguard components to implement reduced
>functionality demo's that can be released via a key. I followed the basic
>idea in their tutorials and used ini files to store data.
>
>I would like the option to store the data in the registry so that it is less
>obvious, but what keys should I generate do store this info?
>What happens if by some fluke I try generating a key that already exists?
There are specific areas of the registry for your program to store
it's config data.
If you want to store for the current user (an nobody else on that
machine), you want
HKEY_CURRENT_USER\Software\Your company name\Your application name
If you want the key to work for every user on the machine use
HKEY_LOCAL_MACHINE\SOFTWARE\Your company name\Your application name
You can store whatever you like under these keys, but as this is the
legit way of doing things (as defined by Microsoft) and the way all
programs are supposed to do things, it's the first place a
hacker/cracker will look. (Okay, maybe the second after the ini file).
>Does anyone else use the Onguard components? They seemed quite good in their
>day, but I don't see much about them anymore.
Dunno. Never used them
Dodgy
--
MUSHROOMS ARE THE OPIATE OF THE MOOSES
.
- References:
- Using the registry
- From: Jan
- Using the registry
- Prev by Date: Re: distance between lats and lons
- Next by Date: Chinese characters and autosize
- Previous by thread: Using the registry
- Next by thread: Re: Using the registry
- Index(es):
Relevant Pages
|
|
