Application Security

[Khalid]

Hi,

The values are in HEX.  They're described here:
http://msdn.microsoft.com/library/en-us/wmisdk/wmi/win32_processor.asp

After (re)reading the description for ProcessorID, I am not sure if it's really unique.  You may want to test this on different machines of the same processor type (either all PIIIs, or all P4s, etc.)  Win32_Processor class also has "UniqueID," which may be unique(??).  Would appreciate if you could share your findings.

The following forum thread has some other options for what you're trying to achieve:
http://www.mcse.ms/archive114-2004-11-1215438.html

Regards,

-Khalid

[TNeilson]

Well, I ran this on 2 nearly identical PCs and got the same ID on both.  You are right, this isn't unique.  I'm guessing I can go back to the HD SN# though, that should be unique for each hard drive.  Has that code already been posted here?

[TNeilson]

I found the code, but I'm assuming the models will be the same on both these computers as well.  That may be less of an issue though.  We aren't concerned with people installing multiple instances of the software at the same facility, we are more concnerned with our competitors getting ahold of this software and using/selling this for their devices. 

[Khalid]

You could try using the "Signature" property of the disk drive... see if that's unique:

http://msdn.microsoft.com/library/en-us/wmisdk/wmi/win32_diskdrive.asp

In the VI, just change the String constant which says 'Model' to 'Signature' (or any other parameter for that matter).

Sorry for all the confusion!

-Khalid

[TNeilson]

I finally figured out how to change these for different items.  The signature was not unique either. 

What do you think about the Bios serial number?  That is unique.  We aren't looking for incredibly type security, we just don't want this to have full functionality without our approval.  If someone figures out how to unlock it, or hack in and change their Bios serial number, we aren't that concerned.

[Khalid]

That's a good idea.  And should suffice for your needs.  I normally use the MAC ID, even though it can be spoofed.  I guess we accept the fact that a determined hacker can break this; we really just want to protect (make it hard) free distribution of the software. 

As you may have figured out, in the VI you change the WMI Class to "Win32_BIOS" in this case, and the parameter to "SerialNumber." 

http://msdn.microsoft.com/library/en-us/wmisdk/wmi/win32_bios.asp

-Khalid

[TNeilson]

Yep, I did figure it out, finally.  Thanks for all your help.  I think this will work for us.

[TNeilson]

I got this working, and it runs great, on my computer.  Is this something that cannot be read on every computer?

[Khalid]

Hmmm..  I do not get a Serial Number on my XP.  Guess this won't work either  

-Khalid

[TNeilson]

Well, I guess I'll keep looking.  If I find something that seems to work, I'll throw it out here, maybe it can help someone else.