VMProtect Software » Forum

hey

im only using VMProtectGetCurrentHWID to generate a constant HWID.
have it saved in a server then compare that string each time for authorization.

i noticed vmp hwid is in some random string format
ie
sHdfK6mPQSFecfozjr3nN2I4tNRKjUr5i9z7yA==

total length of 40 characteres
it contains both upper/lower/special symbols.

because my server rinse the string for special symbols each time.
so i may need to convert it to hex all at once.

but i want to make sure

1. does vmp hwid only contain letters, numbers and '='. is there any other symbols that may appear on vmp hwid? ie '$' ';' etc

2. is it always 40 characters long? if not whats the range of length

3. anyway i can verify its validity? as this is quite insecure and confusing.
because i have no idea what format vmp hwid has on different computer. and i won't have any idea when the users input a fake one storing in my server

thanks

1. does vmp hwid only contain letters, numbers and '='. is there any other symbols that may appear on vmp hwid? ie '$' ';' etc

It is the base64 dictionary. The symbols '$' ';' are not used in base64.

2. is it always 40 characters long? if not whats the range of length

The length of HWID can be different. It depends on count of network cards in the computer (MAC addresses in HWID).

3. anyway i can verify its validity? as this is quite insecure and confusing.
because i have no idea what format vmp hwid has on different computer. and i won't have any idea when the users input a fake one storing in my server

We don`t recommend you verify HWID on your side - it must be processed only in VMProtect`s licensing system.

are you saying this generated hwid will change on the same computer ? or its going to stay the same assuming no new hardware is installed.

because MAC addy can be easily changed.

i really want a safe to generate unqiue id for each computer without having it changed easily.
thats why i got the ultimate version

HWID has many identificators inside (hdd, mac, cpuid, host name) and if any identificator is changed the HWID is changed also. As I wrote - we recommend use HWID only for generation serial numbers (only for jobs of licensing system) otherwise you will have a problem of comparing HWIDs on server side.

P.S. VMProtect has a special algorithm for comparing HWIDs inside licensing system and the result of comparing "different" HWIDs can be equal.