Some software developers have such a demand, is the use of U disk to release the software at the same time, want to save costs, to prevent the software in the U disk is copied, but do not want to buy expensive encryption dog, so want to bind the software on the U disk on the implementation, when the U disk pull down, the software can not run normally, Similar to the previously introduced binding hardware fingerprint, use a USB disk to encrypt the software.
In the software security is not particularly concerned about the situation, you can use the binding U-disk internal ID in the way to achieve this encryption, the first use of the program will be a U disk ID read out, and then generate license files based on this ID, when the decryption disk in the file copied to other computers, Failed to read U disk ID during software execution, so you cannot verify license.
usually two U disk ID is not the same, so even if the software copy to another U disk, software execution, according to U disk ID Verification license, also will appear mismatch phenomenon, so that the software binding U disk encryption mode.
It is to be noted that the U disk encryption is not safe, most of U disk manufacturers have internal production tools, you can modify the internal ID number of u disk, this exists the possibility of copying U disk, but for ordinary users, usually do not modify the internal ID of U disk ability, it also has a certain degree of encryption.
This encryption method, read the U disk ID number of the function of the VB source code as follows:
Se t objw MISe rvice = Ge tobject ("Winmg mts:.ro otcimv2")
Se t Colite ms = Objwmiser Vice. E Xecq uery ("select * Fro m Wi n32_us Bhub")
F or Ea ch objite m in ColI tems
A = o bjitem.de viceid
If in Str (A, "VI D") the n B = Sp lit (A, "")
US b_id = B (UBound (b))
Ne XT