SoftwareShield
System Feature Guide > Virgin Registry
Data
Virgin Registry DataThe first time the ClientProtector executes the StartUp function on a license on a particular machine, the Virgin Registry Data (if any) is written to the registry (if the license also uses at least one Alias File of any kind). Virgin Registry Data is simply a hidden registry key that can be located to determine if the application (license) had ever been executed on the host machine before. Unlike Alias Files, the Virgin Registry Data is only written the first time the license is successfully loaded. Unlike Alias Files, It is not a copy or a hash of the Main License File, but is completely independent of it. The purpose of the Virgin Registry Data is as a fail-safe check to ensure that a license had never been executed on a particular machine before. If a cracker attempts to monitor your program and finds and successfully deletes all the Alias Files, the Virgin Registry Data will probably be missed because it is only written the very first time the program is run (StartUp is called). Also, the Virgin Registry key is only ever read if all the Alias Files are missing. You have the option of not using Virgin Registry Data if you wish. If you do decide to use it, You have the option of completely configuring where the Virgin Registry Data is written and its contents. You have the option of writing it to one of four root keys:
You have complete control over the key path, value name and value of the Virgin Registry Data. However, be very careful that you do not create a conflict or use a key name that already exists. The SoftwareShield License Manager can assist you in creating unique keys. Example
NOTE: If you do decide to Virgin Registry Data, there are some important Windows Security and Permission Considerations you must take into account. More InformationFor help on exactly how to define Virgin Registry Data for your license, see Virgin Registry Data Tab in the SoftwareShield License Manager Reference. |