UUID mechanics

[Oldschool]

I read some threads:

http://www.autoitscript.com/forum/index.ph...=18126&st=0

http://www.autoitscript.com/forum/index.ph...c=21883&hl=

http://www.autoitscript.com/forum/index.ph...mp;#entry131508

I guess the concensus is to use this structure to obtain some values from \root\CIMV2

$objWMIService = ObjGet ("winmgmts:\\" & $com & "\root\CIMV2")
    $colItems = $objWMIService.ExecQuery ("SELECT * FROM Win32_Processor", "WQL", 0x10 + 0x20)

But how do you store these values to ensure integrity?

The first time you run the program you can write them to an ini file persay with something like:

If Not FileExists(config.ini)  Then
    IniWrite($aboveValues)
Endif

And then compare the values from the file to values from \root\CIMV2

Is there a way to only iniWrite() that file once?

In other words how do you store this information securely?

[Emiel Wieldraaijer]

Do you want to encrypt the inifile or do you want to create a readonly ini file ?

Emiel

[Oldschool]

I want to store the UUID generated at 1st run in a secure way.

For example if my program generates an encrypted ini file with UUID in it @ 1st run, if there is no ini file already @ that location, then that does not really help me.

Because if you delete this ini file, the whole verification process fall apart.

What will prevent a user from copying my script to another machine??

[Emiel Wieldraaijer]

hmm difficult

You can add a serial number to your software..

but this will not prevent users from installing it on multiple machines ..

http://www.autoitscript.com/forum/index.ph...l=serial+number

[GEOSoft]

Store the value in the registry instead?