diff options
| author | jmpoep <OriginalEntryPoint@qq.com> | 2023-12-07 16:51:07 +0800 |
|---|---|---|
| committer | jmpoep <OriginalEntryPoint@qq.com> | 2023-12-07 16:51:07 +0800 |
| commit | 28008a746a31abb7909dd86cb0cd413ac8943b0b (patch) | |
| tree | a30b74b8cad548048c3c1551d652828ab76fa9bd /help/en | |
| download | vmprotect-3.5.1-master.tar vmprotect-3.5.1-master.tar.gz vmprotect-3.5.1-master.tar.bz2 vmprotect-3.5.1-master.zip | |
Diffstat (limited to 'help/en')
136 files changed, 7335 insertions, 0 deletions
diff --git a/help/en/about_vmprotect.htm b/help/en/about_vmprotect.htm new file mode 100644 index 0000000..10a6e25 --- /dev/null +++ b/help/en/about_vmprotect.htm @@ -0,0 +1,207 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>What is VMProtect?</title> + <style type="text/css"> + </style> +</head> + +<body> + <h1>What is VMProtect?</h1> + + <p>VMProtect is a new generation of software protection utilities. VMProtect supports + Delphi, Borland C Builder, Visual C/C++, Visual Basic + (native), Virtual Pascal and XCode compilers. At the same time VMProtect has a built-in + disassembler that works with Windows and Mac OS X executables, + and also can link a MAP-file created by the compiler to quickly select fragments of code for protection. + For easy automation of application protection tasks, VMProtect implements a built-in script language. + VMProtect fully supports 32/64-bit operating systems of the Windows family starting from Windows 2000, and Mac OS X starting from version 10.6. + Importantly, regardless of the target platform, VMProtect supports all range of executables, that is, the Windows version can work with files from the Mac OS X version and vice versa.</p> + + <p>The cornerstone principle of VMProtect is to provide efficient protection of the application code from + examination by making the application code and logic very complex for further analysis and cracking. + Main software code protection mechanisms VMProtect applies are: virtualization, mutation, and combined protection that + involves mutation of the application code with subsequent virtualization.</p> + + <p>The crucial advantage of the virtualization method used in VMProtect is + the fact that the virtual machine executing virtualized fragments of code is embedded into the resulting code of the protected application. + Therefore, the app protected with VMProtect needs no third-party libraries or modules to function. + VMProtect allows using several different virtual machines to protect different fragments of code of the same application resulting in even more complicated + cracking process, because a hacker now has to analyze architecture of multiple virtual machines. + </p> + + <p>The method of application code mutation applied in VMProtect is based on obfuscation — a process that adds to the application code + various excessive, "garbage" commands, "dead" parts of the code, random conditional jumps. + It also mutates original commands and transfers execution of certain operations to the stack. + </p> + + <p>The key difference of VMProtect from other software protectors is its ability to protect different parts of the code with different methods: + part of the code can be virtualized, the other part is obfuscated and critical fragments are protected using the combined method.</p> + + <p>To prevent false positives from antiviruses the registered version of VMProtect uses the + <a href="http://standards.ieee.org/develop/indconn/icsg/taggant.pdf">Taggant</a> library that signs the protected file with a certificate of the license owner.</p> + + <p>Another unique feature of VMProtect is embedding of <a href= + "dictionary.htm#Watermarks">watermarks</a> to the code of the application. Watermarks allow to definitely identify the official + owner of the hacked copy of the program, and therefore to take certain measures to him or her.</p> + + <p>VMProtect is available in 3 editions:</p> + + <ul> + <li>Lite;</li> + <li>Professional;</li> + <li>Ultimate;</li> + </ul> + + <p>The below table lists differences in functionality of certain VMProtect editions:</p> + + <table border="1" cellspacing="0" cellpadding="2"> + <tr align="center"> + <td rowspan="2" align="center"> + <strong>Capabilities</strong></td> + + <td colspan="3" align="center"><strong> + VMProtect edition</strong></td> + </tr> + + <tr align="center"> + <td width="12%" align="center">Lite</td> + <td width="12%" align="center">Professional</td> + <td width="12%" align="center">Ultimate</td> + </tr> + + <tr bgcolor="#E0E0E0"> + <td align="left" colspan="4" class="c1"><strong>Protection methods</strong></td> + </tr> + + <tr> + <td>Mutation</td> + <td align="center">+</td> + <td align="center">+</td> + <td align="center">+</td> + </tr> + + <tr> + <td>Virtualization</td> + <td align="center">+</td> + <td align="center">+</td> + <td align="center">+</td> + </tr> + + <tr> + <td>Ultra (mutation+virtualization)</td> + <td align="center">+</td> + <td align="center">+</td> + <td align="center">+</td> + </tr> + + <tr> + <td>Console version</td> + <td align="center">-</td> + <td align="center">+</td> + <td align="center">+</td> + </tr> + + <tr bgcolor="#E0E0E0"> + <td align="left" colspan="4"><strong>Protection options</strong></td> + </tr> + + <tr> + <td>Memory protection</td> + <td align="center">+</td> + <td align="center">+</td> + <td align="center">+</td> + </tr> + + <tr> + <td>Import protection</td> + <td align="center">+</td> + <td align="center">+</td> + <td align="center">+</td> + </tr> + + <tr> + <td>Resource protection</td> + <td align="center">+</td> + <td align="center">+</td> + <td align="center">+</td> + </tr> + + <tr> + <td>Packing</td> + <td align="center">+</td> + <td align="center">+</td> + <td align="center">+</td> + </tr> + + <tr> + <td>Debuger detection</td> + <td align="center">+</td> + <td align="center">+</td> + <td align="center">+</td> + </tr> + + <tr> + <td>Virtual box detection</td> + <td align="center">+</td> + <td align="center">+</td> + <td align="center">+</td> + </tr> + + <tr bgcolor="#E0E0E0"> + <td align="left" colspan="4"><strong>Service functions</strong></td> + </tr> + + <tr> + <td>Watermarks</td> + <td align="center">-</td> + <td align="center">+</td> + <td align="center">+</td> + </tr> + + <tr> + <td>Script language</td> + <td align="center">-</td> + <td align="center">+</td> + <td align="center">+</td> + </tr> + + <tr> + <td>Licensing system</td> + <td align="center">-</td> + <td align="center">-</td> + <td align="center">+</td> + </tr> + + <tr> + <td>License manager</td> + <td align="center">-</td> + <td align="center">-</td> + <td align="center">+</td> + </tr> + + <tr> + <td>File protection</td> + <td align="center">-</td> + <td align="center">-</td> + <td align="center">+</td> + </tr> + </table> + + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/contacts.htm b/help/en/contacts.htm new file mode 100644 index 0000000..ac5b76c --- /dev/null +++ b/help/en/contacts.htm @@ -0,0 +1,40 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Contacts</title> + <style type="text/css"> + </style> +</head> + +<body> + <h1>Contacts</h1> + + <p>Please direct all your inquiries regarding operation of the program and ordering it to:<br /> + www: <a href= + "http://www.vmpsoft.com">http://www.vmpsoft.com</a><br /> + e-mail: <a href= + "mailto:info@vmpsoft.com">info@vmpsoft.com</a><br /> + icq uin: <a href= + "http://wwp.icq.com/scripts/search.dll?to=65107137">65107137</a><br /> + </p><a href="http://www.vmpsoft.com/news.php" target= + "_blank">News</a> | <a href="http://www.vmpsoft.com/buy.php" + target="_blank">Order</a> | <a href= + "http://www.vmpsoft.com/forum/index.php" target= + "_blank">Forum</a><br /> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/create_project.htm b/help/en/create_project.htm new file mode 100644 index 0000000..bb2e4ec --- /dev/null +++ b/help/en/create_project.htm @@ -0,0 +1,106 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Preparing a project</title> + <style type="text/css"> + </style> +</head> + +<body> + <h1>Preparing a project</h1> + + <p>Let us take a look to a very simple application consisting of only one form (Form1), + a text element (Edit1) and a button (Button1). The application works as follows: when the + Button1 is clicked, the app checks if the password entered is correct and displays a corresponding message.</p><br /> + <img src="images/delphi_project.png" /> + + <p>A password is checked using a very simple algorithm: on the first step we transform it to a numeric form, + then we calculate the remainder on dividing it by 17. The password is correct if the remainder on dividing the numeric representation of the entered password by 17 is equal to 13. + The password check procedure implementation on Delphi looks as follows:</p> + <pre class="code">function TForm1.CheckPassword: Boolean; +begin + Result:=(StrToIntDef(Edit1.Text, 0) mod 17=13); +end; + +procedure TForm1.Button1Click(Sender: TObject); +begin + if CheckPassword then + MessageDlg('Correct password', mtInformation, [mbOK], 0) + else + begin + MessageDlg('Incorrect password', mtError, [mbOK], 0); + Edit1.SetFocus; + end; +end; +</pre> + + <p>Selection of procedures and functions to protect can be done in three ways:</p> + + <ul> + <li><a href="use_map_file.htm">Using a MAP-file</a> + created by the compiler along with the executable of the program. + The MAP-file contains all necessary information about names and addresses of all procedures and functions of the app. + If the MAP-file is used, you can select procedures and functions to protect by their names. + With the MAP-file, every time the project is recompiled, VMProtect automatically determines new addresses of procedures and functions.</li> + + <li><a href="use_markers.htm">Using markers</a> + inserted to the source code of the application. Markers are + special marks VMProtect uses to determine the boundaries of the protected fragment. + Also, VMProtect supports markers with a predefined compilation type. + Using markers makes sense when you only want to protect a part of a function or procedure. + Using markers allows you to specify parts of the code where string constants to protect will be further placed.</li> + + <li>By address of protected procedures in the executable file. In comparison with the above two ways, this one is less convenient for use. + Every time the application is modified and recompiled, you have to specify all addresses again. This type of protection is recommended for applications without the source code available. + </li> + </ul> + + <p>Using a MAP-file to define boundaries of the protected code has one more significant advantage. It is worth reviewing it a bit more. + Almost any procedure or function that has local variables or that uses the stack to save registers and/or intermediate calculation results + has the so called prologue and epilogue located correspondingly in the beginning and in the end of the compiled procedure or function:</p> + <pre class="code">push ebp \ +mov ebp, esp \ prologue +push 00 / +push ebx / + +... + +pop ebx \ +pop ecx \ epilogue +pop ebp / +ret / +</pre> + + <p>Due to the way modern compilers work, code markers never incorporate the prologue and the epilogue of a function. + Even if the entire code of the CheckPassword function between begin and end is enclosed to markers. + It would be enough for a hacker to modify the prologue of the function so that the virtualized code was never executed. + For the CheckPassword function this can be done as follows:</p> + <pre class="code">mov eax, 1 +ret +</pre> + + <p><strong>Important:</strong><br /> + If a MAP-file is used to choose code fragments for virtualization, the prologue and the epilogue are also virtualized + significantly boosting hack-proof capability of the protected program. Moreover, is one + virtualized function is called from another virtualized function, control transfers between them without actually jumping to the address of the called function + (a call in this case is a simple jump to another address within the bytecode of the virtual machine interpreter). + This also strengthens protection of the program as all modification of the entry point a hacker makes are rendered useless. + When working with virtualized functions, transfer of control to the entry point of a virtualized function only happens when the protected function is called from + an unprotected or mutated fragment of code.</p><br /> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/default.css b/help/en/default.css new file mode 100644 index 0000000..2aed7c2 --- /dev/null +++ b/help/en/default.css @@ -0,0 +1,55 @@ +body,td,th +{ + font-family: Tahoma, Arial, Helvetica, sans-serif; + font-size: 1em; +} + +tt +{ + font-family: "Courier new"; + font-size: 1.1em; +} + +tr +{ + vertical-align: top; +} + +pre +{ + font-family: "Courier new", monospace; + font-size: 1.1em; +} + +.indent +{ + margin-left: 2em; +} + +.code +{ + font-family: "Courier new"; + background: #f8f8f8; + color: black; + padding: 4px; + border-style: solid; + border-color: #e0e0e0; + overflow: auto; + border-width: 1px; +} + +td, th +{ + border-style: solid; + border-color: black; +} + +table +{ + border-collapse: collapse; +} + +div.unhide_if_no_site +{ + visibility: visible !important; +} diff --git a/help/en/dictionary.htm b/help/en/dictionary.htm new file mode 100644 index 0000000..926f0cc --- /dev/null +++ b/help/en/dictionary.htm @@ -0,0 +1,73 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Glossary</title> + <style type="text/css"> + </style> +</head> + +<body> + <h1>Glossary</h1> + + <p>You can't use a tool effectively if you don't know the terminology specific to the corresponding subject. + The following glossary explains terminology used in VMProtect. + The glossary is not intended to be exhaustive, so some terms may provide meanings that differ from classic ones. + </p> + + <p><a name="ByteCode" id="ByteCode"><strong>Bytecode</strong></a> - the code received after transcoding commands of the real processor to commands of the virtual machine. + </p> + + <p><a name="Virtualization" id="Virtualization"><strong>Virtualization</strong></a> - a process that transforms a part of the executable code of the application + to commands of the virtual machine featuring command system, architecture and operational logic that are unknown to a potential hacker. + Virtualized fragments of code are executed by the interpreter of the virtual machine without transforming them to machine language code of the physical processor. + Generally, reverse engineering of virtualized fragments comes down to building a disassembler with the same architecture as the processor the virtual machine imitates and analyzing of the resulting disassembled code. + </p> + + <p><a name="VirtualMachine" id="VirtualMachine"><strong>Virtual machine</strong></a> - a program code directly executing bytecode in the protected application.</p> + + <p><a name="Watermarks" id="Watermarks"><strong>Watermarks + </strong></a> - a unique for each user array of bytes that allows to definitely identify a legal owner of the hacked copy of the program.</p> + + <p><a name="Mutation" id="Mutation"><strong>Mutation</strong></a> - replacing an original command with an analogue or with a certain set of commands producing the same result + </p> + + <p><a name="Obfuscation" id="Obfuscation"><strong>Obfuscation</strong></a> - a group of methods and techniques + intended to complicate analysis of a program code. Depending on the programming language a protected program is written on, different obfuscation types are used. + Obfuscation of applications written on interpreting languages (Perl, PHP and others) is made through modifying the source code: + comments are removed, variables are given senseless names, string constants are encrypted and so on. + Obfuscation of Java / .NET applications is performed through transforming the bytecode processed by the virtual machine. + Obfuscation of compiled programs relies on modifying machine language codes: the obfuscator adds various "garbage" commands, "dead code", random jumps. + Also, original commands mutate, a part of operations is moved to the stack, and a number of structural (or less frequently mathematical) transformations is made. + Reverse engineering of obfuscated fragments of code attempts to bring the fragments back to their original state, and that is a time-consuming task as long as obfuscation is done properly. + </p> + + <p><a name="Protector" id="Protector"><strong>Protector</strong></a> - software intended to protect other programs from being hacked. + The majority of today's protectors do not modify the source code of an application, packing or encrypting the app instead. The main focus + is put to protecting the unpacking/decrypting program or procedure. + </p> + + <p><a name="EntryPoint" id="EntryPoint"><strong>Entry point</strong></a> - the initial address execution of the application loaded into the memory starts from.</p> + + <p><a name="Pack" id="Pack"><strong>Packing</strong></a> - a way to protect the program code by compressing the executable file of the program and/or libraries + using non-typical algorithms. The protected fragments of code are compressed by the packer, and unpacked completely or partially at user's side when the application is executed. + </p> + + <p><a name="Crypt" id="Crypt"><strong>Encryption</strong></a> protects a part of the application's code with strong cryptographic algorithms. + Software protected by encryption requires an end-user to enter the activation code to remove limitations set by the developer for the unregistered version of the program.</p><br /> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/en.qhcp b/help/en/en.qhcp new file mode 100644 index 0000000..e91c869 --- /dev/null +++ b/help/en/en.qhcp @@ -0,0 +1,14 @@ +<?xml version="1.0" encoding="utf-8" ?> +<QHelpCollectionProject version="1.0"> + <docFiles> + <generate> + <file> + <input>en.qhp</input> + <output>../../bin/en.qch</output> + </file> + </generate> + <register> + <file>../../bin/en.qch</file> + </register> + </docFiles> +</QHelpCollectionProject>
\ No newline at end of file diff --git a/help/en/en.qhp b/help/en/en.qhp new file mode 100644 index 0000000..a70030e --- /dev/null +++ b/help/en/en.qhp @@ -0,0 +1,260 @@ +<?xml version="1.0" encoding="UTF-8"?> +<QtHelpProject version="1.0"> + <namespace>ru.com.vmpsoft.vmprotect.3.0</namespace> + <virtualFolder>doc</virtualFolder> + <customFilter name="VMProtect 3.0"> + <filterAttribute>vmpg</filterAttribute> + <filterAttribute>3.0</filterAttribute> + </customFilter> + <filterSection> + <filterAttribute>vmpg</filterAttribute> + <filterAttribute>3.0</filterAttribute> + <toc><section title="Introduction" ref="terms.htm"> + <section title="Glossary" ref="dictionary.htm" /> + <section title="Analysis, cracking and protection of software" ref="software_protection.htm" /> + <section title="What is VMProtect?" ref="about_vmprotect.htm" /> + <section title="Recommendations on protecting your application" ref="recommendations.htm" /> + <section title="History of changes" ref="history.htm" /> + </section> + <section title="Working with VMProtect" ref="work.htm"> + <section title="Preparing a project" ref="create_project.htm"> + <section title="Using a MAP-file" ref="use_map_file.htm" /> + <section title="Using markers" ref="use_markers.htm" /> + <section title="SDK functions" ref="sdk_functions.htm" /> + </section> + <section title="Main window" ref="main_window.htm"> + <section title="Main menu" ref="main_menu.htm"> + <section title=""File" menu" ref="menu_file.htm" /> + <section title=""Edit" menu" ref="menu_edit.htm" /> + <section title=""Project" menu" ref="menu_project.htm" /> + <section title=""Tools" menu" ref="menu_tools.htm" /> + <section title=""Help" menu" ref="menu_help.htm" /> + </section> + <section title="Toolbar" ref="toolbar.htm" /> + <section title=""Project" section" ref="project.htm"> + <section title=""Functions for Protection" section" ref="project_functions.htm" /> + <section title=""Licenses" section" ref="manager/licenses.htm" /> + <section title=""Files" section" ref="project_files.htm" /> + <section title=""Script" section" ref="project_script.htm" /> + <section title=""Options" section" ref="project_options.htm" /> + </section> + <section title=""Functions" section" ref="functions.htm" /> + <section title=""Details" section" ref="info.htm"> + <section title=""Directories" section" ref="info_directories.htm" /> + <section title=""Segments" section" ref="info_segments.htm" /> + <section title=""Imports" section" ref="info_imports.htm" /> + <section title=""Exports" section" ref="info_exports.htm" /> + <section title=""Resources" section" ref="info_resources.htm" /> + <section title=""Calculator" section" ref="info_calc.htm" /> + <section title=""Dump" section" ref="info_dump.htm" /> + </section> + </section> + <section title="Console version" ref="mode_console.htm" /> + </section> + <section title="Licensing system" ref="manager/index.htm"> + <section title="Licensing system features" ref="manager/features.htm" /> + <section title="How the licensing system works?" ref="manager/howitworks.htm" /> + <section title="Example of usage" ref="manager/usage/index.htm"> + <section title="Stage 1: Test mode" ref="manager/usage/index.htm#TestMode"> + <section title="Step 1.1: Create test application" ref="manager/usage/step11_app.htm" /> + <section title="Step 1.2: Add license checking code" ref="manager/usage/step12_code.htm" /> + <section title="Step 1.3: Get state of serial number" ref="manager/usage/step13_flags.htm" /> + <section title="Step 1.4: Get user name and e-mail" ref="manager/usage/step14_name.htm" /> + <section title="Step 1.5: Check serial number expiration date" ref="manager/usage/step15_exp.htm" /> + <section title="Step 1.6: Limit application running time" ref="manager/usage/step16_time.htm" /> + <section title="Step 1.7: Limit period of free updates" ref="manager/usage/step17_maxbuild.htm" /> + <section title="Step 1.8: Put serial number to "black" list" ref="manager/usage/step18_blacklist.htm" /> + <section title="Step 1.9: Lock serial number to hardware" ref="manager/usage/step19_hwid.htm" /> + <section title="Step 1.10: Read user data from serial number" ref="manager/usage/step1A_userdata.htm" /> + </section> + <section title="Stage 2: Real mode" ref="manager/usage/index.htm#RealMode"> + <section title="Step 2.1: Create new test application" ref="manager/usage/step21_src.htm" /> + <section title="Step 2.2: Create VMProtect project" ref="manager/usage/step22_vmp.htm" /> + <section title="Step 2.3: Create product in the License Manager" ref="manager/usage/step23_product.htm" /> + <section title="Step 2.4: Test results" ref="manager/usage/step24_test.htm" /> + <section title="Step 2.5: Lock code to serial number" ref="manager/usage/step25_codelock.htm" /> + </section> + <section title="Licensing API functions" ref="manager/usage/api.htm" /> + </section> + <section title="Serial number generators" ref="manager/keygen/index.htm"> + <section title="Windows-version" ref="manager/keygen/keygen_dll.htm" /> + <section title=".Net-version" ref="manager/keygen/keygen_net.htm" /> + <section title="UNIX-version" ref="manager/keygen/keygen_php.htm" /> + <section title="Serial number format" ref="manager/keygen/serial_format.htm" /> + <section title="Serial number encryption algorithms" ref="manager/keygen/algorithms.htm" /> + </section> + <section title="Activation System" ref="manager/activation.htm"> + <section title="Configuring activation in VMProtect" ref="manager/activation/vmprotect.htm" /> + <section title="Activation in Web License Manager" ref="manager/activation/weblm.htm" /> + <section title="Activation API" ref="manager/activation/api.htm" /> + </section> + </section> + <section title="Using scripts" ref="script.htm"> + <section title="Classes" ref="script_classes.htm" /> + <section title="Built-in functions" ref="script_functions.htm" /> + <section title="Events" ref="script_events.htm" /> + </section> + <section title="Watermarks" ref="watermarks.htm"> + <section title=""Setup" tab" ref="watermarks_setup.htm" /> + <section title=""Search" tab" ref="watermarks_search.htm" /> + </section> + <section title="Frequently Asked Questions" ref="faq.htm" /> + <section title="Contact information" ref="contacts.htm" /> + </toc> + <keywords> + <keyword id="default" ref="terms.htm"/> + <keyword id="project::functions" ref="project_functions.htm"/> + <keyword id="project::options" ref="project_options.htm"/> + <keyword id="project::script" ref="project_script.htm"/> + <keyword id="project::files" ref="project_files.htm"/> + <keyword id="project::licenses" ref="manager/licenses.htm"/> + <keyword id="project::mapfunctions" ref="functions.htm"/> + <keyword id="project::details" ref="info.htm"/> + <keyword id="functions::setup" ref="project_functions.htm#AddProcedure"/> + <keyword id="functions::search" ref="project_functions.htm#Search"/> + <keyword id="watermarks::setup" ref="watermarks_setup.htm"/> + <keyword id="watermarks::search" ref="watermarks_search.htm"/> + <keyword id="settings" ref="menu_tools.htm#Settings"/> + <keyword id="contacts" ref="contacts.htm"/> + </keywords> + <files> + <file>default.css</file> + <file>about_vmprotect.htm</file> + <file>contacts.htm</file> + <file>create_project.htm</file> + <file>default.css</file> + <file>dictionary.htm</file> + <file>faq.htm</file> + <file>functions.htm</file> + <file>history.htm</file> + <file>info.htm</file> + <file>info_calc.htm</file> + <file>info_directories.htm</file> + <file>info_dump.htm</file> + <file>info_exports.htm</file> + <file>info_imports.htm</file> + <file>info_resources.htm</file> + <file>info_segments.htm</file> + <file>info_calc.htm</file> + <file>main_menu.htm</file> + <file>menu_file.htm</file> + <file>menu_edit.htm</file> + <file>menu_project.htm</file> + <file>menu_tools.htm</file> + <file>menu_help.htm</file> + <file>main_window.htm</file> + <file>mode_console.htm</file> + <file>project.htm</file> + <file>project_files.htm</file> + <file>project_functions.htm</file> + <file>project_options.htm</file> + <file>project_options_external_addresses.htm</file> + <file>project_script.htm</file> + <file>recommendations.htm</file> + <file>script.htm</file> + <file>script_classes.htm</file> + <file>script_events.htm</file> + <file>script_functions.htm</file> + <file>sdk_functions.htm</file> + <file>software_protection.htm</file> + <file>terms.htm</file> + <file>toolbar.htm</file> + <file>use_map_file.htm</file> + <file>use_markers.htm</file> + <file>watermarks.htm</file> + <file>watermarks_search.htm</file> + <file>watermarks_setup.htm</file> + <file>about_vmprotect.htm</file> + <file>work.htm</file> + <file>images/activation_setup.png</file> + <file>images/button_compilation.png</file> + <file>images/button_execute.png</file> + <file>images/button_open.png</file> + <file>images/button_project.png</file> + <file>images/button_save.png</file> + <file>images/button_action.png</file> + <file>images/button_search.png</file> + <file>images/delphi_project.png</file> + <file>images/expert_find.png</file> + <file>images/export_keys.png</file> + <file>images/functions.png</file> + <file>images/import_key.png</file> + <file>images/licenses1.png</file> + <file>images/lock_to_serial.png</file> + <file>images/main_window.png</file> + <file>images/menu_edit.png</file> + <file>images/menu_file.png</file> + <file>images/menu_help.png</file> + <file>images/menu_project.png</file> + <file>images/menu_project_import.png</file> + <file>images/menu_tools.png</file> + <file>images/preferences.png</file> + <file>images/project_add_folder.png</file> + <file>images/project_add_function.png</file> + <file>images/project_add_license.png</file> + <file>images/project_file_delete.png</file> + <file>images/project_file_menu.png</file> + <file>images/project_file_protection.png</file> + <file>images/project_file_settings.png</file> + <file>images/project_functions.png</file> + <file>images/project_functions_content.png</file> + <file>images/project_functions_content2.png</file> + <file>images/project_functions_menu.png</file> + <file>images/project_functions_menu2.png</file> + <file>images/project_functions_menu3.png</file> + <file>images/project_functions_search.png</file> + <file>images/project_generate_keys.png</file> + <file>images/project_options.png</file> + <file>images/project_script.png</file> + <file>images/properties_directory.png</file> + <file>images/properties_dump.png</file> + <file>images/properties_dump_goto.png</file> + <file>images/properties_export.png</file> + <file>images/properties_import.png</file> + <file>images/properties_resources.png</file> + <file>images/properties_segments.png</file> + <file>images/properties_calc.png</file> + <file>images/watermarks_add.png</file> + <file>images/watermarks_menu.png</file> + <file>images/watermarks_search.png</file> + <file>images/watermarks_setup.png</file> + <file>images/delphi_map.png</file> + <file>images/visual_studio_map.png</file> + <file>manager/activation/api.htm</file> + <file>manager/activation/vmprotect.htm</file> + <file>manager/activation/weblm.htm</file> + <file>images/weblm_1.png</file> + <file>images/weblm_2.png</file> + <file>manager/keygen/algorithms.htm</file> + <file>manager/keygen/index.htm</file> + <file>manager/keygen/keygen_dll.htm</file> + <file>manager/keygen/keygen_net.htm</file> + <file>manager/keygen/keygen_php.htm</file> + <file>manager/keygen/serial_format.htm</file> + <file>manager/usage/api.htm</file> + <file>images/codelock_error.png</file> + <file>images/depends.png</file> + <file>manager/usage/index.htm</file> + <file>manager/usage/step11_app.htm</file> + <file>manager/usage/step12_code.htm</file> + <file>manager/usage/step13_flags.htm</file> + <file>manager/usage/step14_name.htm</file> + <file>manager/usage/step15_exp.htm</file> + <file>manager/usage/step16_time.htm</file> + <file>manager/usage/step17_maxbuild.htm</file> + <file>manager/usage/step18_blacklist.htm</file> + <file>manager/usage/step19_hwid.htm</file> + <file>manager/usage/step1A_userdata.htm</file> + <file>manager/usage/step21_src.htm</file> + <file>manager/usage/step22_vmp.htm</file> + <file>manager/usage/step23_product.htm</file> + <file>manager/usage/step24_test.htm</file> + <file>manager/usage/step25_codelock.htm</file> + <file>manager/activation.htm</file> + <file>manager/features.htm</file> + <file>manager/howitworks.htm</file> + <file>manager/index.htm</file> + <file>manager/licenses.htm</file> + </files> + </filterSection> +</QtHelpProject> diff --git a/help/en/faq.htm b/help/en/faq.htm new file mode 100644 index 0000000..4a0d931 --- /dev/null +++ b/help/en/faq.htm @@ -0,0 +1,109 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Frequently Asked Questions</title> + <style type="text/css"> + </style> +</head> + +<body> + <h1>Frequently Asked Questions</h1> + + <h3>Ordering VMProtect</h3> + + <p><strong>If I order VMProtect, will I be able to use it on different computers?</strong><br /> + You can install and use VMProtect on any number of computers you want and need for your work.</p> + + <p><strong>What is a difference between Personal and Company + licenses, and which license should I prefer?</strong><br /> + The only difference between these license types is who owns them. If you are a private developer, choose the Personal license. + If you represent a company or plan to use the product in your organization, select the Company license.</p> + + <p><strong>How the full version of VMProtect is delivered upon purchase?</strong><br /> + The full version (and all further updates of VMProtect within the one-year subscription) are delivered to your e-mail address. + A message contains a link to the archive containing installer of the full version of VMProtect. + That is why we recommend turning off all spam filters in the settings of your mailbox before purchasing VMProtect.</p> + + <p><strong>Will I receive new versions of VMProtect for free or they should be purchased individually? + </strong><br /> + After purchase you are eligible for all new versions within one year after the date of purchase. + When this period expiresm you can <a href= + "http://www.vmpsoft.com/buy.php">renew your annual subscription</a> + or continue using the version of VMProtect you have without any restrictions.</p> + + <p><strong>Can I pay for VMProtect with my credit card or PayPal?</strong><br /> + You can purchase VMProtect with a credit card or + PayPal. To do this, select the desired version of VMProtect at the <a href= + "http://www.vmpsoft.com/buy.php">order page</a> and then choose a credit card or PayPal as your payment method.</p> + + <h3>General questions</h3> + + <p><strong>Is there a way to encrypt strings and data arrays automatically?</strong><br /> + In VMProtect you can hide <a href= + "sdk_functions.htm#VMProtectDecryptStringA">ANSI constants</a> and + <a href="sdk_functions.htm#VMProtectDecryptStringW">Unicode + constants</a>. All other data the code operates with remain intact. We recommend storing all confidential information + encrypted and decrypt it directly before use. + The unpacker itself can be <a href= + "project_functions.htm#CompilationTypes">virtualized</a>.</p> + + <p><strong>Is there a way to protect procedures that I call from various threads in my application?</strong><br /> + VMProtect is 100% multi-thread compatible and there are no any specific limitations for this type of protection.</p> + + <p><strong>Can I use VMProtect along with another protector (packer)?</strong><br /> + Using any other packers (protectors) after a file is processed by VMProtect can render the protected application non-functional. + </p> + + <p><strong>Should I include + VMProtectSDK32.dll/VMProtectSDK64.dll into the setup package of the program?</strong><br /> + These libraries are only used at the debug stage of the program (before protecting it). After you protect the application with VMProtect + all information about usage of these DLLs is removed completely, so you don't have to include them into the release package.</p> + + <h3>Compiler messages</h3> + + <p><strong>What does this error mean: VMProtectMarker + "ToolButton1Click.1".0044327D: Address is used by procedure + "TForm1.ToolButton1Click"?</strong><br /> + This error means the same command at the address + 0044327D is used in two procedures that are included into the list of protected objects. + To solve this issue, you should exclude one of procedures (in this particular case these are + VMProtectMarker "ToolButton1Click.1" and TForm1.ToolButton1Click) + from the list of protected objects.</p> + + <p><strong>What does this error mean: [Error] + TForm1.Test.004433F4: Minimum procedure size for compilation is 5 bytes?</strong><br /> + This error means the procedure TForm1.Test is too small and cannot be protected. To solve this issue, exclude this procedure from the list of protected objects.</p> + + <p><strong>What does this warning mean: + TForm1.ToolButton1Click.00443368: Inner address jump: + 00443337?</strong><br /> + The following warning means a possible jump from the unprotected code fragment into the protected code fragment is detected. + Such jump may cause malfunction of the protected program. To solve the issue, mark + the 00443337 address as <a href= + "project_functions.htm#ExtAddress">external</a>.</p> + + <p><strong>What does this error mean: The ".text" section allocates space required for the new section?</strong><br /> + The following error usually take place when drivers are protected. + It means that free space between the first section of the file and service information in the + header of the file is too small to create a new section + To solve this problem, increase the value of the section alignment parameter in driver's source codes and rebuild the driver completely. + (For example: if you compile the driver using WDK/DDK, you should add + DRIVER_ALIGNMENT=0x200 into SOURCES).</p> + + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/functions.htm b/help/en/functions.htm new file mode 100644 index 0000000..ef72c49 --- /dev/null +++ b/help/en/functions.htm @@ -0,0 +1,33 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>"Functions" section</title> + <style type="text/css"> + </style> +</head> + +<body> + <h1>"Functions" section</h1> + + <p>The "Functions" section lists all functions available for protection:</p> + <p><img src="images/functions.png" /></p> + <p>When a function is selected, you can see its properties and protection options on the main panel. + For each function you can specify a <a href="project_functions.htm#CompilationTypes">compilation type</a> and enable + <a href="manager/features.htm#lock">lock to a serial number</a>.</p> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/history.htm b/help/en/history.htm new file mode 100644 index 0000000..a1cae6e --- /dev/null +++ b/help/en/history.htm @@ -0,0 +1,819 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>History of changes</title> +</head> + +<body> + <h1>History of changes</h1> + + <h3>Version 3.5</h3> + <p>[!] .NET: Many bugs are fixed<br /> + [!] ELF: Fixed a bug that occurred inside VMProtectGetCurrentHWID while getting HDD information<br /> + [+] .NET: Added support of .NET Core (3.0+) and .NET Standard (2.1+)<br /> + [+] .NET: Added import protection<br /> + [+] .NET: Added resources protection<br /> + [+] .NET: Added support of mixed assemblies<br /> + [*] Mach-O: Improved support of sections with types S_THREAD_LOCAL_VARIABLES and S_THREAD_LOCAL_REGULAR<br /> + [*] Mach-O: Improved support of Objective-C<br /> + [*] ELF: Improved support of relocations with type R_386_PC32<br /> + [*] PE: Improved antidebug<br /> + </p> + + <h3>Version 3.4</h3> + <p>[!] Fixed a bug that occurred during virtualization of BT [m16], POP [m64]<br /> + [+] Added support of .NET applications<br /> + [+] Added disassembling PMULLD<br /> + [+] PE: Added support of COFF symbols<br /> + [*] ELF: Improved disassembling of SWITCH<br /> + [*] ELF: Improved support of relocations with type R_386_PC32<br /> + [*] PE: Improved exception handling<br /> + [*] PE: Improved support of Windows Server 2016 Datacenter<br /> + </p> + + <h3>Version 3.3</h3> + <p>[+] PE: Added support of "Control Flow Guard"<br /> + [+] PE: Added support of PDB files for loading symbols<br /> + [+] Mach-O: Added support of OS X 10.13 and later<br /> + [+] ELF: Added support of statically linked libstdc++.so<br /> + [+] ELF: Added support of CentOS 5 and CentOS 6<br /> + [+] ELF: Added support of TLS segments<br /> + [+] ELF: Added support of HTTPS for VMProtectActivateLicense<br /> + [*] PE: Improved exception handling for x64 applications<br /> + [*] PE: Improved detection of virtualization tools under the Hyper-V role<br /> + [*] PE: Improved demagling of MSVC symbols<br /> + [*] Mach-O: Improved exception handling<br /> + [*] Mach-O: Improved support of Objective-C<br /> + [*] ELF: Fixed a bug that occurred when the "Pack the Output File" option was used<br /> + </p> + + <h3>Version 3.2</h3> + <p>[!] PE: Fixed an error that occurred in VMProtectIsValidImageCRC in protected driver<br /> + [!] Fixed an error that occurred during virtualization of XOR with relocations<br /> + [*] PE: Improved packing of sections with the TLS directory<br /> + [*] PE: Improved antidebug<br /> + [*] PE: The Taggant System has been removed<br /> + [*] Accelerated unpacking when the "<a href= + "project_options.htm#PackOutputFile">Packing output file</a>" option was used<br /> + [+] Added support of ELF format<br /> + [+] Added disassembling of AVX commands<br /> + </p> + + <h3>Version 3.1</h3> + + <p>[!] Fixed an error that occurred during disassembling of MOVUPS with REX prefix 0x41<br /> + [!] Fixed an error that occurred during virtualization of XLAT, FSIN and POPAD<br /> + [*] Improved exceptions handling<br /> + [*] Improved VM architecture<br /> + [*] Improved checking the integrity of a file on disk when the "<a href= + "project_options.htm#MemoryProtection">Memory protection</a>" option was used<br /> + [*] Improved virtualization of FSTENV, FSTCW, FSAVE and FSTSW<br /> + [*] PE: VMProtectActivateLicense now works via WinHTTP and uses IE proxy settings by default<br /> + [*] PE: VMProtectGetCurrentHWID has been improved for kernel drivers<br /> + [*] PE: Improved support of Delphi 6 when the "<a href= + "project_options.htm#ImportProtection">Import protection</a>" option was used<br /> + [*] PE: Improved antidebug<br /> + [+] Added virtualization of ADD, AND, SUB, XOR, OR with LOCK prefix<br /> + [+] Added virtualization of CQO<br /> + [+] Added disassembling PINSRB, PINSRD, PINSRQ, PMINSD, PMINUW, PMINUD, PMAXSB, PMAXSD, PMAXUW and PMAXUD<br /> + [+] Mach-O: Added support of section "__unwind_info"<br /> + [+] Mach-O: Added support of LC_LOAD_WEAK_DYLIB<br /> + [+] Mach-O: Added support of Delphi Berlin<br /> + [+] PE: Added support of Windows 10 for kernel drivers<br /> + [+] PE: Now the "Rich Header" is deleted when the "<a href= + "project_options.htm#Additional">Strip debug information</a>" option was used<br /> + [+] Ultimate: Functionality of "<a href="project_files.htm">Files</a>" has been enhanced. Now you can create folders and use symbols ".." for indication of the parent directory<br /> + [+] GUI: At displaying of protected ANSI strings the code page from Windows settings is used now<br /> + [+] LUA: Usage of functions from external DLLs has been added<br /> + </p> + + <h3>Version 3.0</h3> + + <p>[*] PE: Added support for exceptions in x64 code<br /> + [*] Mach-O: Added support for <a href="sdk_functions.htm">SDK functions</a><br /> + [*] Ultimate: Added support for <a href="manager/usage/api.htm">licensing functions</a> for drivers and applications written on VB6<br /> + [*] Ultimate: Functionality of <a href="project_files.htm">DLL Box</a> has been enhanced. Now the protected application can envelope any files + including ActiveX servers with optional automatic registration in the virtual registry.<br /> + [*] Virtual Box detection has been improved<br /> + [*] Script engine changed to LUA<br /> + [*] New VM architecture<br /> + [+] A new function <a href="sdk_functions.htm#VMProtectIsProtected">VMProtectIsProtected</a> is added to the SDK<br /> + </p> + + <h3>Version 2.13</h3> + + <p>[!] PE: Added support for Delay Import<br /> + [!] PE: Improved compatibility with VS2012<br /> + [!] PE: Improved compatibility with Embarcadero RAD Studio XE3<br /> + [!] PE: Improved compatibility with MinGW<br /> + [!] Ultimate: Improved compatibility of DLL Box with Windows 8<br /> + [+] WebLM: Added support for mbstring.func_overload = 2<br /> + [+] WebLM: In the activation code a new field "Expiry date" has been added. + (Now VMProtectActivateLicense can return ACTIVATION_EXPIRED if the current date exceeds the expiry date)<br /> + [+] WebLM: Fields "Expiry date" and "Maximum build date" now contain the "days since purchase" value<br /></p> + + <h3>Version 2.12</h3> + + <p>[!] PE: Fixed bugs in x64 applications<br /> + [!] PE: Fixed an error that occurred if an application had the IMAGE_DLLCHARACTERISTICS_NX_COMPAT flag<br /> + [+] PE: Added support for Windows 8<br /> + [+] WebLM: Added Russian and Chinese language<br /></p> + + <h3>Version 2.11</h3> + + <p>[!] Fixed a bug during <a href= + "project_options.htm#PackOutputFile">packing</a> in х64 + applications<br /> + [!] PE: Fixed a bug that occurred when the + "<a href="project_options.htm#ImportProtection">Import protection</a>" option was used<br /> + [!] PE: Fixed a bug emerging when a TLS section with relocation tables was processed<br /> + [+] Ultimate: Added <a href= + "manager/activation.htm">activation/deactivation</a><br /> + [+] Mach-O: Added <a href= + "project_options.htm#PackOutputFile">packing</a><br /> + [*] PE: Support for DriverVerifier<br /> + [*] PE: Improved support for SEH for MSVC<br /> + [*] Mach-O: Improved support for IndirectSymbols<br /></p> + + <h3>Version 2.10</h3> + + <p>[!] Fixed a bug that occurred when the + "<a href="project_options.htm#ResourceProtection">Resource protection</a>" option was used<br /> + [!] Fixed a bug that occurred when the + "<a href="project_options.htm#ImportProtection">Import protection</a>" option was used<br /> + [!] Fixed a bug that occurred when x64 drivers without relocation tables were protected<br /> + [+] Added support for Max OS X executables (Mach-O format)<br /> + [+] Added support for HLT command<br /> + [+] New API is added to SDK - <a href= + "sdk_functions.htm#VMProtectFreeString">VMProtectFreeString</a><br /> + [*] Improved identification of markers and strings marked with <a href= + "sdk_functions.htm#VMProtectDecryptStringA">VMProtectDecryptStringA</a>/<a href="sdk_functions.htm#VMProtectDecryptStringW">VMProtectDecryptStringW</a><br /> + [*] Now you can use relative paths in output file name and license parameters<br /> + [*] Improved support for SEH for Delphi<br /> + [*] SenseLock Edition: Added the "<a href= + "project_options.htm#ResourceProtection">Resource protection</a>" option<br /> + [*] SenseLock Edition: A <a href= + "manager/licenses.htm">license manager</a> is added to the GUI version<br /> + [*] SenseLock Edition: programming of keys is added to the GUI version<br /> + [*] Licenses in the license manager can now be copied and pasted to/from the clipboard<br /></p> + + <h3>Version 2.09</h3> + + <p>[!] Fixed a bug that occurred when <a href= + "project_options.htm#DebuggerDetection">a debugger was detected</a> + under Windows 2000<br /> + [!] Fixed a bug that occurred while disassembling PMULHUW and LDMXCSR commands<br /> + [!] Fixed a bug that occurred when <a href= + "project_options.htm#MemoryProtection">memory protection</a> was used(file integrity wasn't checked)<br /> + [!] Ultimate: Fixed a bug that occurred when running protected files under Windows 2000 (this required + EncodePointer/DecodePointer functions from kernel32.dll)<br /> + [*] Improved virtualization of exception handlers for Visual + C<br /> + [*] <a href="project_options.htm#ResourceProtection">Resource protection</a> is now available in Lite and Professional versions<br /> + [*] Added support for EnumResourceTypes, EnumResourceNames and + EnumResourceLanguages when using <a href= + "project_options.htm#ResourceProtection">resource protection</a> (available only when called from the main module)<br /> + [+] Added support for exceptions for Borland C Builder<br /> + [+] Ultimate: Improved performance of <a href= + "manager/usage/api.htm#VMProtectGetSerialNumberState">VMProtectGetSerialNumberState</a> + and <a href= + "manager/usage/api.htm#VMProtectGetSerialNumberData">VMProtectGetSerialNumberData</a> functions<br /> + + [+] The script for <a href= + "script_classes.htm#TLicenseManager">TLicenseManager</a> now includes the + <a href= + "script_classes.htm#TLicenseManager.Save">Save</a> method<br /> + [-] The "Move resources to the end of the file" option is removed. The resource section is always the last one now.<br /></p> + + <h3>Version 2.08</h3> + + <p>[!] Fixed a bug that occurred when assembling the TEST [XXXX], REG command<br /> + [!] Fixed a bug that occurred while disassembling х64 commands with the 0x67 prefix<br /> + [*] Improved support for files with small values of + SectionAlignment<br /> + [*] Improved placement of markers and strings for Intel + Compiler 12 and Lazarus<br /> + [*] Improved <a href="project_options.htm#ImportProtection">import protection + </a><br /> + [*] Ultimate: Now you can load project files with licensing parameters<br /> + [+] Ultimate: Added <a href= + "project_options.htm#ResourceProtection">resource protection</a><br /> + [+] Ultimate: The script now includes classes: <a href= + "script_classes.htm#TLicense">TLicense</a> and <a href= + "script_classes.htm#TLicenseManager">TLicenseManager</a><br /></p> + + <h3>Version 2.07</h3> + + <p>[!] Fixed an error occurred when working with the <a href= + "manager/licenses.htm">license manager</a> if Windows had other system language than English<br /> + [+] In the expert mode you can now change the default messages: "Debugger is detected", "Virtualization tools are detected", "File is corrupted" and "Serial number is required" + <br /> + [+] The script class <a href= + "script_classes.htm#TVMProtector">TVMProtector</a> now has the <a href= + "script_classes.htm#TVMProtector.Messages">Messages</a> property<br /> + [*] Improved compatibility of <a href= + "project_options.htm#MemoryProtection">memory protection</a> with some antiviruses<br /></p> + + <h3>Version 2.06</h3> + + <p>[!] Fixed a bug with marker name identification for MinGW<br /> + [!] Fixed an error occurred during <a href= + "project_options.htm#ImportProtection">import protection</a> in х64 files + <br /> + [!] Fixed an error occurred during virtualization of FILD WORD + PTR [XXXX]<br /> + [!] Fixed an error occurred while disassembling PSRLW<br /> + [!] Fixed an error occurred in <a href= + "project_files.htm">DLL Box</a> when the antivirus was active<br /> + [*] Project file is now saved as XML<br /> + [*] Script is now stored in a project file<br /> + [*] Ultimate: <a href="manager/licenses.htm">License manager</a> is now in the GUI version<br /> + [*] Ultimate: Significantly sped up execution of code <a href= + "project_functions.htm#LockToKey">locked to a serial number</a><br /> + [+] Added support for MAP files for MinGW<br /> + [+] Added support for JCLDEBUG<br /> + [+] The script class <a href= + "script_classes.htm#TPEDirectory">TPEDirectory</a> now has the + Clear method<br /> + [+] The script class <a href= + "script_classes.htm#TVMProcedure">TVMProcedure</a> now has properties: + <a href= + "script_classes.htm#TVMProcedure.InputSize">InputSize</a> and + <a href= + "script_classes.htm#TVMProcedure.OutputSize">OutputSize</a><br /> + [+] Ultimate: New API are added to SDK - <a href= + "sdk_functions.htm#VMProtectBeginVirtualizationLockByKey">VMProtectBeginVirtualizationLockByKey</a> + and <a href= + "sdk_functions.htm#VMProtectBeginUltraLockByKey">VMProtectBeginUltraLockByKey</a><br /> + </p> + + <h3>Version 2.05</h3> + + <p>[!] Fixed errors with line identification for MinGW programs<br /> + [!] Fixed the "Out of system resources" error occurred when many procedures were added to the project<br /> + [!] Fixed an error occurred in the console version during output of strings<br /> + [*] MAP file date is now taken from its contents<br /> + [+] Ultimate: Added examples on working with the <a href= + "manager/index.htm">licensing system</a> (on MSVC and + Delphi)<br /> + [+] Ultimate: Added source codes of the <a href= + "manager/keygen/keygen_dll.htm">serial number generator</a> + on MSVC<br /> + [+] Ultimate: Added <a href="project_files.htm">DLL Box</a> + (available only for EXE files)<br /> + [+] Ultimate: A new class <a href= + "script_classes.htm#TInternalDLLs">TInternalDLLs</a> is added to the script<br /> + [+] Ultimate: In the script class <a href= + "script_classes.htm#TVMProtector">TVMProtector</a> a new property is added: <a href= + "script_classes.htm#TVMProtector.InternalDlls">InternalDlls</a><br /> + + [+] In the script class <a href= + "script_classes.htm#TMapRecord">TMapRecord</a> a new property is added: + <a href= + "script_classes.htm#TMapRecord.SegmentName">SegmentName</a><br /> + [+] In the script class <a href= + "script_classes.htm#TIntelRecord">TIntelRecord</a> a new property is added: <a href= + "script_classes.htm#TIntelRecord.Operands">Operands</a><br /> + [+] Czech language is added<br /></p> + + <h3>Version 2.04</h3> + + <p>[!] Fixed an error occurred during obfuscation of FDIVR + [ESP+XXXX]<br /> + [!] Fixed an error occurred during obfuscation of SWITCH in x64 applications + <br /> + [*] When using the "<a href= + "project_options.htm#MemoryProtection">Memory protection</a>" option, a file is checked for integrity now<br /> + [*] Ultimate: Better licensing module integration to the protected program<br /> + [+] Added support for files with overlay<br /> + [+] Ultimate: Added an example of <a href= + "manager/keygen/keygen_net.htm">C# serial number generator</a><br /> + [+] Ultimate: <a href="manager/licenses.htm">License manager</a> now has export of product parameters for a generator on C#<br /> + [+] Ultimate: The <a href="mode_console.htm">console version</a> + now has the "-lf" parameter to specify a file with licensing parameters<br /> + [+] Added French help file<br /></p> + + <h3>Version 2.03</h3> + + <p>[!] Fixed an error occurred when using <a href= + "project_options.htm#ImportProtection">import protection</a> in SYS files (base address of hal.dll wasn't determined under Windows 7)<br /> + [!] Fixed an error occurred during obfuscation of command using CRx registers in SYS files<br /> + [!] Fixed small issues<br /> + [*] Improvements in <a href="manager/index.htm">licensing system</a> of the Ultimate version<br /> + [+] French language is added<br /></p> + + <h3>Version 2.02</h3> + + <p>[!] An error is fixed in SenseLock Edition occurred when several programs using different licenses on the key run simultaneously + (users of SenseLock Edition should update master key firmware)<br /> + [!] Fixed EntryPoint disassembly error in Delphi programs<br /> + [!] Fixed small issues<br /> + [*] Important improvements in <a href="manager/index.htm">licensing system</a> of the Ultimate version<br /> + [*] SenseLock Edition now uses the licensing system of the Ultimate version (users of SenseLock Edition should update master key firmware)<br /> + [*] Improved detection of strings marked with <a href= + "sdk_functions.htm#VMProtectDecryptStringA">VMProtectDecryptStringA</a>/<a href="sdk_functions.htm#VMProtectDecryptStringW">VMProtectDecryptStringW</a><br /> + + [+] GUI now supports Unicode<br /> + [+] Traditional Chinese is added<br /></p> + + <h3>Version 2.01</h3> + + <p>[!] Fixed small issues in the installer, the <a href= + "manager/licenses.htm">license manager</a> and <a href= + "sdk_functions.htm">SDK</a><br /> + [*] VMProtect is registered with its own + <a href="manager/index.htm">licensing system now</a><br /> + [+] Added Chinese Simplified<br /></p> + + <h3>Version 2.0</h3> + + <p>[!] Fixed disassembly and virtualization bugs of CALL FWORD PTR [XXXX] and JMP FWORD PTR [XXXX] commands<br /> + [!] An error is fixed in SenseLock Edition occurred when the serial number is asked after the standard PIN of a user has changed<br /> + [!] Fixed an error occurred during virtualization of SWITCH in х64 applications<br /> + [!] Fixed an error occurred while disassembling commands: + ROL, ROR, RCL, RCR, SHL, SHR, SAL and SAR, with the REX prefix in х64 applications<br /> + [!] Fixed an error occurred during virtualization of the CMOVxx command<br /> + [!] Fixed small issues<br /> + [*] The help file in Russian is updated<br /> + [*] The help file in English is updated<br /> + [+] Added the <a href="manager/index.htm">licensing system</a> (available only in Ultimate version)<br /> + [+] New API are added to the SDK - <a href= + "sdk_functions.htm#VMProtectDecryptStringA">VMProtectDecryptStringA</a> + and <a href= + "sdk_functions.htm#VMProtectDecryptStringW">VMProtectDecryptStringW</a><br /> + + [+] The script class <a href= + "script_classes.htm#TVMProcedure">TVMProcedure</a> now has a new property + <a href= + "script_classes.htm#TVMProcedure.CompilationOptions">CompilationOptions</a><br /> + + [+] The script class <a href= + "script_classes.htm#TVMProcedure">TVMProcedure</a> now has properties + <a href= + "script_classes.htm#TVMProcedure.SELicense">SELicense</a> and + <a href="script_classes.htm#TVMProcedure.SEVersion">SEVersion</a> + (available in SenseLock Edition only)<br /> + [+] The script class <a href= + "script_classes.htm#TVMProtector">TVMProtector</a> has new properties added: <a href= + "script_classes.htm#TVMProtector.VMSectionName">VMSectionName</a> + and <a href= + "script_classes.htm#TVMProtector.VMExecutorCount">VMExecutorCount</a><br /> + + [+] The script class <a href= + "script_classes.htm#TVMProtector">TVMProtector</a> has new properties added: + <a href= + "script_classes.htm#TVMProtector.SEMasterPassword">SEMasterPassword</a>, + <a href= + "script_classes.htm#TVMProtector.SEUserPIN">SEUserPIN</a>, + <a href="script_classes.htm#TVMProtector.SEKeyID">SEKeyID</a>, + <a href="script_classes.htm#TVMProtector.SELicense">SELicense</a> + and <a href= + "script_classes.htm#TVMProtector.SEVersion">SEVersion</a> + (available in SenseLock Edition only)<br /> + [-] The option "Create online commands dynamically" is removed<br /></p> + + <h3>Version 1.81</h3> + + <p>[!] Fixed an error occurred during execution of mutated code on Pentium 4 processors<br /> + [!] Fixed an error occurred during execution of virtualized code on some Athlon processors<br /> + [!] Fixed errors occurred during disassembly and virtualization of exception handler structures with an exception filter + (for program on Delphi and Borland + C++ Builder)<br /> + [!] Fixed an error occurred when using <a href= + "project_options.htm#VirtualMachines">several VM</a> in 64-bit files<br /> + [!] Fixed small issues<br /> + [*] Enhanced detection of <a href= + "use_markers.htm">marker</a> names (for programs on Visual C)<br /> + [*] Significantly reduced memory consumption during compilation<br /> + [*] The "HTML" resource is not packed now<br /> + [*] The help file in Russian is updated<br /> + [+] Added wildcard search of procedures in the "Master" mode<br /> + [+] Added <a href="project_options.htm#PackOutputFile">new packing mode</a> featuring higher compression rate<br /> + [+] Added support for files with TLS callbacks<br /> + [+] New API is added to the SDK - <a href= + "sdk_functions.htm#VMProtectIsValidImageCRC">VMProtectIsValidImageCRC</a><br /> + </p> + + <h3>Version 1.8</h3> + + <p>[!] Fixed errors occurred during <a href= + "project_options.htm#ImportProtection">import protection</a> in SYS files<br /> + [!] Fixed errors occurred during <a href= + "project_options.htm#MemoryProtection">memory protection</a> in + DLL/SYS files<br /> + [!] Fixed errors occurred when using <a href= + "project_options.htm#VirtualMachines">multiple VM</a> in + DLL/SYS-files<br /> + [!] Fixed an error occurred during mutation of the code with exception handlers<br /> + [!] Fixed an error occurred when <a href= + "project_options.htm#MemoryProtection">memory protection</a> and + <a href="project_options.htm#Watermarks">watermarks</a> were used simultaneously<br /> + [!] Fixed small bugs<br /> + [*] Improved detection of references to <a href= + "use_markers.htm">marked</a> strings (you don't have to mark every reference to a protected string now)<br /> + [*] Improved <a href="project_options.htm#ImportProtection">import protection</a><br /> + [*] Improved <a href= + "project_options.htm#DebuggerDetection">debugger detection</a><br /> + [*] The help file in Russian is updated<br /> + [+] The GUI version now allows saving project files under different names<br /> + [+] Now you can open project files<br /> + [+] Added <a href= + "project_options.htm#VirtualizationToolsDetection">Sandboxie detection</a><br /> + [+] Added support for files compiled with the /SAFESEH key<br /> + [+] Added support for CodeGear 2009<br /> + [+] Now you can have named markers (when <a href= + "sdk_functions.htm#VMProtectBegin">VMProtectBegin</a>/<a href= + "sdk_functions.htm#VMProtectBeginMutation">VMProtectBeginMutation</a>/<a href="sdk_functions.htm#VMProtectBeginVirtualization">VMProtectBeginVirtualization</a>/<a href="sdk_functions.htm#VMProtectBeginUltra">VMProtectBeginUltra</a> + from VMProtectSDKxx.dll/VMProtectDDKxx.sys are used)<br /> + [+] New API are added to the SDK (<a href= + "sdk_functions.htm#VMProtectIsDebuggerPresent">VMProtectIsDebuggerPresent</a> + and <a href= + "sdk_functions.htm#VMProtectIsVirtualMachinePresent">VMProtectIsVirtualMachinePresent</a>)<br /> + + [+] A new utility was added to SenseLock Edition - "Remote update and licensing system"<br /> + [+] SenseLock Edition now has key id lock<br /></p> + + <h3>Version 1.7</h3> + + <p>[!] Sections with SHAREABLE+WRITABLE flags are not packed now<br /> + [!] Fixed small issues<br /> + [*] Improved <a href="project_options.htm#ImportProtection">import protection</a> for SYS files<br /> + [*] Improved <a href= + "project_options.htm#PackOutputFile">packing</a> of SYS files + (packed sections are not flagged with WRITABLE any more)<br /> + [*] Improved <a href= + "project_options.htm#DebuggerDetection">debugger detection</a><br /> + [+] Added the "<a href= + "project_options.htm#MemoryProtection">Memory protection</a>" option (this option prevent changes to be made to memory while the application is running)<br /> + [+] Added the "<a href= + "project_options.htm#VirtualizationToolsDetection">Detect virtualization tools (VMware/Virtual PC)</a>" option<br /> + [+] The script class <a href= + "script_classes.htm#TPEFile">TPEFile</a> now has a property + <a href= + "script_classes.htm#TPEFile.EntryPoint">EntryPoint</a><br /></p> + + <h3>Version 1.65</h3> + + <p>[!] Fixed small issues<br /> + [*] Improved <a href="project_options.htm#ImportProtection">import protection</a><br /> + [*] Improved <a href= + "project_options.htm#DebuggerDetection">debugger detection + </a><br /> + [+] Added identification of unpaired <a href= + "use_markers.htm">markers</a> (unpaired markers are available in the general list of objects)<br /> + [+] Added markers to apply a pre-defined compilation type: + VMProtectBeginVirtualization, VMProtectBeginMutation and + VMProtectBeginUltra<br /> + [+] Added Chinese Traditional language<br /></p> + + <h3>Version 1.64</h3> + + <p>[!] Fixed a bug occurred during execution of a <a href= + "project_options.htm#PackOutputFile">packed file</a>, + if it had "TYPELIB", "REGISTRY" and "MUI" resources<br /> + [!] Fixed the R6002 error occurred during execution of a packed file (for programs written on Visual C)<br /> + [!] Fixed a bug occurred when the + "<a href="project_options.htm#ImportProtection">Import protection</a>" option was used in 64-bit SYS files<br /> + [!] Fixed small issues<br /> + [*] The settings file is now saved to %APPDATA%/PolyTech/VMProtect<br /> + [*] Improved <a href="project_options.htm#ImportProtection">import protection + </a><br /> + [+] Added the option "<a href= + "project_options.htm#VirtualMachines">Virtual machines</a>" + (different virtualized fragments of code are executed on different virtual machines with different architecture)<br /> + [+] Added the option "<a href= + "project_options.htm#DebuggerDetection">Debugger detection</a>" + (if a debugger is detected during the protected application execution, the app shows a corresponding message and closes)<br /> + [+] The script class <a href= + "script_classes.htm#TPESection">TPESection</a> now has a property + <a href= + "script_classes.htm#TPESection.IncludedInPacking">IncludedInPacking</a><br /> + + [+] Added support for IRETD command<br /> + [+] Added an example of using markers in Lazarus<br /></p> + + <h3>Version 1.63</h3> + + <p>[!] Fixed an error occurred when using the + "<a href="project_options.htm#ImportProtection">Import protection</a>" option<br /> + [!] Fixed small issues<br /> + [+] A new event was added to the script: <a href= + "script_events.htm#OnBeforePackFile">OnBeforePackFile</a><br /> + [+] The script class <a href= + "script_classes.htm#TPEFile">TPEFile</a> now has a new property + <a href="script_classes.htm#TPEFile.Handle">Handle</a><br /> + [+] Added an example of using <a href= + "use_markers.htm">markers</a> in Free Pascal<br /> + [*] Improved integrity control of VM objects<br /></p> + + <h3>Version 1.62</h3> + + <p>[!] Fixed errors occurring when using the + "<a href="project_options.htm#ImportProtection">Import protection + </a>" option<br /> + [!] Fixed an error occurred when handling an exception in the TRY/EXCEPT/END block in the "Ultra" mode (for programs written on Delphi and + Borland C++ Builder)<br /> + [*] Improved <a href="project_options.htm#ImportProtection">import protection</a> for SYS files<br /> + [+] Every object of a project now can have its own compilation options for individual performance tuning + (individual options are configured in the project tree)<br /> + [+] Added the "Move resources to the end of the file" option<br /> + [+] Added an example of using extended markers (see + Examples\Scripts\UseExtMarkers)<br /></p> + + <h3>Version 1.61</h3> + + <p>[!] Fixed an error occurred when starting packed files under Windows 95/98<br /> + [!] Fixed small issues<br /> + [+] An ability to pass a file name via the command line is added to the Lite version<br /> + [+] A history is added in the "Master" mode<br /> + [+] Language selection is added in the "Master" mode<br /> + [+] Added the "<a href= + "project_options.htm#ImportProtection">Import protection</a>" option + (recommended for use along with packing of the output file)<br /> + [+] In the <a href="mode_console.htm">console version</a>, a new parameter "-we" is added(with this parameter all warnings are displayed as error)<br /> + [+] A new class <a href= + "script_classes.htm#TPEResourceRecords">TPEResourceRecords</a> is added to the script<br /> + + [+] The script class <a href= + "script_classes.htm#TPEFile">TPEFile</a> now has a new property + <a href= + "script_classes.htm#TPEFile.ResourceRecords">ResourceRecords</a><br /> + </p> + + <h3>Version 1.6</h3> + + <p>[!] Fixed small issues<br /> + [*] Improved work with identical strings(now identical strings are displayed as a single object with multiple elements inside)<br /> + [+] Added an option to pack the output file<br /> + [+] A new class <a href= + "script_classes.htm#TPEExportRecords">TPEExportRecords</a> is added to the script<br /> + [+] The script class <a href= + "script_classes.htm#TPEFile">TPEFile</a> now has a property + <a href= + "script_classes.htm#TPEFile.ExportRecords">ExportRecords</a><br /> + + [+] A new event <a href= + "script_events.htm#OnBeforeSaveFile">OnBeforeSaveFile</a> is added to the script<br /> + [+] The help file in Chinese is added (translation by Wang + Xiaopeng)<br /> + [+] Added MAP-file date/time check. (If modification date and time of the MAP-file differ from those of the protected file, the MAP-file is not loaded)<br /></p> + + <h3>Version 1.56</h3> + + <p>[!] Fixed an error occurred during virtualization of BT, BTC, BTR and BTS commands<br /> + [!] Fixed small issues<br /> + [*] List of options is sorted in order of priority<br /> + [*] Improved support for SEH for VC8<br /> + [*] Improved dynamic online-command production<br /> + [*] Improved VM object integrity control<br /> + [+] Added support for PREFETCH and PREFETCHW commands<br /> + [+] New functions CompareText and + AnsiCompareText are added to the script<br /> + [+] The script class <a href= + "script_classes.htm#TPEFile">TPEFile</a> now has a new property + <a href="script_classes.htm#TPEFile.Size">Size</a><br /> + [+] Added an example of using <a href= + "use_markers.htm">markers</a> in MinGW<br /> + [+] Added Chinese language (translation by Wang Xiaopeng)<br /> + [+] In the procedure adding dialog <a href= + "project_functions.htm#Search">wildcard search</a> is added ("*" and "?" are allowed)<br /> + [+] Messages of the compiler now includes output file size<br /></p> + + <h3>Version 1.55</h3> + + <p>[!] Fixed an error occurred when working with a file having unaligned ImageSize value<br /> + [!] Fixed an error occurred when calculating TRY block beginning in Delphi programs<br /> + [!] Fixed an error occurred when a "mixed" code was processed in Discardable and NonDiscardable section of SYS-files<br /> + [!] Fixed an error occurred during virtualization of 64-bit DLL/SYS-files<br /> + [*] The "Encrypt registers upon exit of the VM" option is restored<br /> + [+] A new class <a href= + "script_classes.htm#TIniFile">TIniFile</a> is added to the script<br /> + [+] The script class <a href= + "script_classes.htm#TPEFile">TPEFile</a> now has new properties and methods<br /> + [+] The GUI-version now features a calculator to calculate file offsets by addresses<br /> + [+] Added Italian language (translation by Gabriele Lanza)<br /></p> + + <h3>Version 1.54</h3> + + <p>[!] Fixed an error occurred during mutation of the PUSH ESP command<br /> + [!] ИFixed an error occurred during virtualization of the FLDCW [ESP+xxxx] command<br /> + [!] Fixed an error occurred during obfuscation of the bytecode<br /> + [*] GUI is enhanced<br /> + [+] Added German and Spanish languages<br /> + [+] Added support for <a href="script.htm">scripts</a><br /> + [+] In the <a href="mode_console.htm">console version</a> a parameter is added to specify a script file name<br /></p> + + <h3>Version 1.53</h3> + + <p>[!] Fixed errors occurred during virtualization of code in DLL/SYS-files<br /> + [*] Code virtualization improvements<br /> + [*] In the <a href="mode_console.htm">console version</a> "running" percent is removed when the output is directed to a file<br /> + [+] Added an option to insert markers for x86-64<br /> + [+] Added an ability to create folders in a project<br /> + [+] In the <a href="mode_console.htm">console version</a> a new parameter is added to identify the file name of a project<br /></p> + + <h3>Version 1.52</h3> + + <p>[!] Fixed an error occurred during mutation of CMOVxx, CMPXCHG and CMPXCHG8B commands<br /> + [!] Fixed an error occurred during mutation of LEA ESP,[ESP+xxxx] command<br /> + [*] The RCL and RCR commands are added to the basic logic of VM<br /> + [+] Added support for x86-64<br /> + [+] In the GUI-version, the "<a href= + "project_options.htm">Options</a>" tab now can be set to display an output file name<br /> + [+] Added the help file in Russian and English<br /></p> + + <h3>Version 1.51</h3> + + <p>[!] Fixed an error occurred during creating a "Relocation + Table" of zero length<br /> + [!] Fixed an error occurred during mutation of the CALL [xxxx] command in the "Mutation" mode in DLL/SYS files<br /> + [!] In the Delphi example, VMProtectBegin definition now includes a command preventing optimization of VMProtectBegin + (optimization could lead to a non-functional protected application)<br /> + [+] Added the "Autosave project after compiling" option<br /></p> + + <h3>Version 1.5</h3> + + <p>[!] Fixed an error occurred while dragging files to the main window<br /> + [!] Fixed an error occurred when working with read-only files<br /> + [!] Fixed small issue during compilation in the "Ultra" mode<br /> + [*] A protected file now inherits attributes of the original file<br /> + [+] the list of protected procedures can now include strings (string assignment must be selected with markers)<br /> + [+] The installation package includes examples of using markers in Borland C++ Builder, Delphi, MASM, Visual Basic and Visual + C++<br /> + [+] Added an option: "Integrate to shell"<br /></p> + + <h3>Version 1.4</h3> + + <p>[!] Fixed an error occurred during mutation of IMUL, MUL, IDIV, DIV commands<br /> + [!] Fixed an error occurred during virtualization of multiple CASE tables following one by one<br /> + [!] Fixed an error occurred during virtualization of POP word/dword ptr [esp+xxxx] and IMUL reg8 commands<br /> + [!] Fixed an error occurred while disassembling MOVNTPS and MOVNTPD commands<br /> + [+] Added a new type of compilation "Ultra" (mutation + virtualization)"<br /> + [+] Added compilation type selection in the add/modify procedure window<br /> + [+] Added search for watermarks in processes (used for searching watermarks in packed files)<br /> + [*] Enhanced compatibility with ASM compilers (TASM, MASM etc.)<br /></p> + + <h3>Version 1.3</h3> + + <p>[!] Fixed an error occurred during emulation of the FILD word ptr [xxxx] command<br /> + [+] Each procedure can be specified a certain compilation type ("Mutation" or "Virtualization")<br /></p> + + <h3>Version 1.25</h3> + + <p>[+] Added support for SEH for VC7-8<br /> + [+] Added support for markers in Visual Basic (begin and end of a fragment are marked with the following lines: Call VarPtr("VMProtect + begin") and Call VarPtr("VMProtect end"))<br /> + [*] In the registered version, the VM interpreter completely changes now (to prevent automatic detection of protection by signature scanners such as PEiD, RDG Packer + Detector and others)<br /></p> + + <h3>Version 1.24</h3> + + <p>[+] Added a possibility to insert watermarks to a protected file<br /> + [*] VM interpreter now supports multi-threaded applications (no need to create a procedure to allocate memory for interpreter's needs)<br /> + [-] The option to allocate memory for VM interpreter's neds is removed. <br /></p> + + <h3>Version 1.23</h3> + + <p>[!] Fixed small issues [+] Added the "Master" mode [+] The procedure tree now displays links [*] Options + "Hide constants", "Dynamically create online commands", + "Encrypt registers on jumps", "VM object integrity control" and others are only available for registered users now</p> + + <h3>Version 1.22.2</h3> + + <p>[!]Fixed an error occurred during compilation of projects with the "Memory allocation in the interpreter" option enabled<br /></p> + + <h3>Version 1.22</h3> + + <p>[!] Fixed small issues<br /> + [+] Added a possibility to check integrity of a bytecode (requires enabling the "VM object integrity control" option on)<br /></p> + + <h3>Version 1.21</h3> + + <p>[!] Fixed an error occurred during emulation of CMPXCHG8b, if operands are EAX and EDX<br /> + [+] Now interpreter contains only those commands that will be used to execute a bytecode<br /> + [-] Some commands were removed from the basic logic of VM (to complicate analysis and decompiling of a bytecode)<br /></p> + + <h3>Version 1.2</h3> + + <p>[!] Fixed an error occurred when the Bound Import directory is moved<br /> + [+] Added a possibility to include marked parts of the code to the project(the beginning and the end of the + fragment are marked by the following code assembler insertions - "db $EB,$10,'VMProtect begin',0" and "db + $EB,$0E,'VMProtect end',0")<br /> + [+] Added an option to include exported functions to the project<br /> + [-] Removed the "Encrypt bytecode" option (bytecode is now always encrypted)<br /></p> + + <h3>Version 1.1</h3> + + <p>[!] Fixed errors occurred while: emulation of SBB + (wrong state of some flags); emulation of CMOVxx, + CMPXCHG and CMPXCHG8b (when the second operand was addressed using ESP or a DWORD value)<br /> + [+] Added support for SEH in VB6 (native)<br /> + [+] Added support for MAP-files generated by IDA<br /> + [+] Added an option for batch adding of procedures<br /> + [+] Added displaying of links to commands directly in the list of procedures<br /> + [+] Added a new option: "Encrypt registers on jumps"<br /></p> + + <h3>Version 1.09</h3> + + <p>[*] End of procedure detection process while disassembling of cycles is improved<br /> + [+] For UPX compatibility, Shareable flag of Writeable sections is cleared (if the old relocation table is used for VM needs)<br /></p> + + <h3>Version 1.08</h3> + + <p>[*] Big fragments of code disassembly is sped up<br /> + [*] Metamorphism mechanism of bytecode interpreter is improved<br /></p> + + <h3>Version 1.07</h3> + + <p>[!] Fixed errors occurred when: working with PE files (when code section virtual size was equal to zero); + obfuscating FPU commands (errors led to wrong results); disassembly (CWD was detected instead of CWDE); + emulation of ROL and ROR commands (if the argument was 1-byte)<br /> + [+] Added support for SSE2 command group<br /></p> + + <h3>Version 1.06</h3> + + <p>[!] Fixed an error corrupting the A flag state after emulating SUB, CMP, DEC, NEG, CMPXCHG, SCAS and + CMPS commands.<br /> + [!] Fixed an error occurred when working with an unaligned file<br /> + [+] Added support for BSF, BSR and CMPXCHG8b instructions<br /> + [+] For multi-threaded applications, you can specify a memory allocation procedure for the VM interpreter + (memory allocation procedure must be defined as fastcall)<br /></p> + + <h3>Version 1.05</h3> + + <p>[+] Added support for FUCOMPP and FCMOVxx instructions<br /> + [+] The type of strings + (ANSI/Unicode/Pascal) and comments for structure fields made by compilers are now shown + when looking at parts of the code<br /> + [+] Added a metamorphism procedure for the bytecode interpreter<br /> + [+] Added new compilation options: "Bytecode encryption" and + "Strip relocations (for EXE files only)"<br /> + [-] Removed the "Obfuscate bytecode" option (now always on)<br /></p> + + <h3>Version 1.04</h3> + + <p>[!] Fixed an error occurred while detecting SEH handlers for C++<br /> + [*] Bytecode obfuscator is totally reworked<br /> + [+] Relocations are highlighted in the code now<br /></p> + + <h3>Version 1.03</h3> + + <p>[+] "Free space" from original parts of code is used to store the bytecode<br /> + [+] Added detection of "short" pascal-format strings (first byte defines the length of a string)<br /></p> + + <h3>Version 1.02</h3> + + <p>[!] Fixed errors related to execution of online-commands in DLL/SYS<br /> + [*] Changed the calculation algorithm of bytecode checksum<br /> + [+] Added an option "VM interpreter integrity control" (also works as an anti-debug technique if the interpreter is being debugged and the debugger uses INT 03 as breakpoints).<br /> + [+] Usage of "old" relocation tables to store the bytecode<br /></p> + + <h3>Version 1.01</h3> + + <p>[!] Fixed an error occurred when files with relocations were created(the error arose during operation of DLL/SYS-files in Windows 95/98/Me)<br /> + [!] Fixed small issues in the disassembler<br /> + [+] Added support for instructions: F2XM1, FABS, FCLEX, FCOS, + FDECSTP, FINCSTP, FINIT, FLDCW, FLDLN2, FLDLG2, FPREM, FREM1, + FPTAN, FRNDINT, FSIN, FSTCW, FTST, FYL2X, FPATAN, FLDZ, + FISTP<br /> + [+] Added support for MAP-files of Borland C Builder<br /> + [+] Now you can select the language of the interface and messages (Russian and English are available)<br /></p> + + <h3>Version 1.0</h3> + + <p>[!] Fixed small bugs in the interface<br /> + [+] Added support for CMOV and CMPXCHG<br /></p> + + <h3>Version 0.97</h3> + + <p>[!] Fixed small bugs in the interface<br /> + [+] Added support for Virtual Pascal<br /></p> + + <h3>Version 0.96</h3> + + <p>[!] Fixed error in the compiler (incorrect work with the C flag while compiling NEG and SBB instructions; fixed POPF processing; + fixed wrong bytecode CRC check when processing external conditional jumps)<br /> + [!] Fixed bugs in the VM interpreter related to bytecode obfuscation<br /> + [+] Improved processing of a MAP-file generated by C/C++ + compilers (procedure names contain information about arguments)<br /></p> + + <h3>Version 0.94</h3> + + <p>[!] Fixed many errors<br /></p><br /> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/images/activation_setup.png b/help/en/images/activation_setup.png Binary files differnew file mode 100644 index 0000000..6e2fde2 --- /dev/null +++ b/help/en/images/activation_setup.png diff --git a/help/en/images/button_action.png b/help/en/images/button_action.png Binary files differnew file mode 100644 index 0000000..8484283 --- /dev/null +++ b/help/en/images/button_action.png diff --git a/help/en/images/button_compilation.png b/help/en/images/button_compilation.png Binary files differnew file mode 100644 index 0000000..bd2cc6e --- /dev/null +++ b/help/en/images/button_compilation.png diff --git a/help/en/images/button_execute.png b/help/en/images/button_execute.png Binary files differnew file mode 100644 index 0000000..82f3c9f --- /dev/null +++ b/help/en/images/button_execute.png diff --git a/help/en/images/button_open.png b/help/en/images/button_open.png Binary files differnew file mode 100644 index 0000000..b6b5bcb --- /dev/null +++ b/help/en/images/button_open.png diff --git a/help/en/images/button_project.png b/help/en/images/button_project.png Binary files differnew file mode 100644 index 0000000..19a37af --- /dev/null +++ b/help/en/images/button_project.png diff --git a/help/en/images/button_save.png b/help/en/images/button_save.png Binary files differnew file mode 100644 index 0000000..5df92e5 --- /dev/null +++ b/help/en/images/button_save.png diff --git a/help/en/images/button_search.png b/help/en/images/button_search.png Binary files differnew file mode 100644 index 0000000..92da88c --- /dev/null +++ b/help/en/images/button_search.png diff --git a/help/en/images/codelock_error.png b/help/en/images/codelock_error.png Binary files differnew file mode 100644 index 0000000..cc89c01 --- /dev/null +++ b/help/en/images/codelock_error.png diff --git a/help/en/images/delphi_map.png b/help/en/images/delphi_map.png Binary files differnew file mode 100644 index 0000000..c50db71 --- /dev/null +++ b/help/en/images/delphi_map.png diff --git a/help/en/images/delphi_project.png b/help/en/images/delphi_project.png Binary files differnew file mode 100644 index 0000000..f208ba5 --- /dev/null +++ b/help/en/images/delphi_project.png diff --git a/help/en/images/depends.png b/help/en/images/depends.png Binary files differnew file mode 100644 index 0000000..b9dd025 --- /dev/null +++ b/help/en/images/depends.png diff --git a/help/en/images/expert_find.png b/help/en/images/expert_find.png Binary files differnew file mode 100644 index 0000000..c04f64b --- /dev/null +++ b/help/en/images/expert_find.png diff --git a/help/en/images/export_keys.png b/help/en/images/export_keys.png Binary files differnew file mode 100644 index 0000000..f68cc4c --- /dev/null +++ b/help/en/images/export_keys.png diff --git a/help/en/images/functions.png b/help/en/images/functions.png Binary files differnew file mode 100644 index 0000000..7989724 --- /dev/null +++ b/help/en/images/functions.png diff --git a/help/en/images/import_key.png b/help/en/images/import_key.png Binary files differnew file mode 100644 index 0000000..df4e19a --- /dev/null +++ b/help/en/images/import_key.png diff --git a/help/en/images/licenses1.png b/help/en/images/licenses1.png Binary files differnew file mode 100644 index 0000000..62ecb6e --- /dev/null +++ b/help/en/images/licenses1.png diff --git a/help/en/images/lock_to_serial.png b/help/en/images/lock_to_serial.png Binary files differnew file mode 100644 index 0000000..b96aace --- /dev/null +++ b/help/en/images/lock_to_serial.png diff --git a/help/en/images/main_window.png b/help/en/images/main_window.png Binary files differnew file mode 100644 index 0000000..e9aba46 --- /dev/null +++ b/help/en/images/main_window.png diff --git a/help/en/images/menu_edit.png b/help/en/images/menu_edit.png Binary files differnew file mode 100644 index 0000000..95f86a6 --- /dev/null +++ b/help/en/images/menu_edit.png diff --git a/help/en/images/menu_file.png b/help/en/images/menu_file.png Binary files differnew file mode 100644 index 0000000..285fb1a --- /dev/null +++ b/help/en/images/menu_file.png diff --git a/help/en/images/menu_help.png b/help/en/images/menu_help.png Binary files differnew file mode 100644 index 0000000..e50991e --- /dev/null +++ b/help/en/images/menu_help.png diff --git a/help/en/images/menu_project.png b/help/en/images/menu_project.png Binary files differnew file mode 100644 index 0000000..99e7392 --- /dev/null +++ b/help/en/images/menu_project.png diff --git a/help/en/images/menu_project_import.png b/help/en/images/menu_project_import.png Binary files differnew file mode 100644 index 0000000..e279de9 --- /dev/null +++ b/help/en/images/menu_project_import.png diff --git a/help/en/images/menu_tools.png b/help/en/images/menu_tools.png Binary files differnew file mode 100644 index 0000000..c4a29fc --- /dev/null +++ b/help/en/images/menu_tools.png diff --git a/help/en/images/preferences.png b/help/en/images/preferences.png Binary files differnew file mode 100644 index 0000000..e0328e5 --- /dev/null +++ b/help/en/images/preferences.png diff --git a/help/en/images/project_add_folder.png b/help/en/images/project_add_folder.png Binary files differnew file mode 100644 index 0000000..eba65ac --- /dev/null +++ b/help/en/images/project_add_folder.png diff --git a/help/en/images/project_add_function.png b/help/en/images/project_add_function.png Binary files differnew file mode 100644 index 0000000..45c11a3 --- /dev/null +++ b/help/en/images/project_add_function.png diff --git a/help/en/images/project_add_license.png b/help/en/images/project_add_license.png Binary files differnew file mode 100644 index 0000000..fb1d384 --- /dev/null +++ b/help/en/images/project_add_license.png diff --git a/help/en/images/project_file_delete.png b/help/en/images/project_file_delete.png Binary files differnew file mode 100644 index 0000000..781e514 --- /dev/null +++ b/help/en/images/project_file_delete.png diff --git a/help/en/images/project_file_menu.png b/help/en/images/project_file_menu.png Binary files differnew file mode 100644 index 0000000..a2e5c32 --- /dev/null +++ b/help/en/images/project_file_menu.png diff --git a/help/en/images/project_file_protection.png b/help/en/images/project_file_protection.png Binary files differnew file mode 100644 index 0000000..dc632f9 --- /dev/null +++ b/help/en/images/project_file_protection.png diff --git a/help/en/images/project_file_settings.png b/help/en/images/project_file_settings.png Binary files differnew file mode 100644 index 0000000..37ed75f --- /dev/null +++ b/help/en/images/project_file_settings.png diff --git a/help/en/images/project_functions.png b/help/en/images/project_functions.png Binary files differnew file mode 100644 index 0000000..f0c6657 --- /dev/null +++ b/help/en/images/project_functions.png diff --git a/help/en/images/project_functions_content.png b/help/en/images/project_functions_content.png Binary files differnew file mode 100644 index 0000000..ea5d2a9 --- /dev/null +++ b/help/en/images/project_functions_content.png diff --git a/help/en/images/project_functions_content2.png b/help/en/images/project_functions_content2.png Binary files differnew file mode 100644 index 0000000..afbe976 --- /dev/null +++ b/help/en/images/project_functions_content2.png diff --git a/help/en/images/project_functions_menu.png b/help/en/images/project_functions_menu.png Binary files differnew file mode 100644 index 0000000..16796c5 --- /dev/null +++ b/help/en/images/project_functions_menu.png diff --git a/help/en/images/project_functions_menu2.png b/help/en/images/project_functions_menu2.png Binary files differnew file mode 100644 index 0000000..55c9d5a --- /dev/null +++ b/help/en/images/project_functions_menu2.png diff --git a/help/en/images/project_functions_menu3.png b/help/en/images/project_functions_menu3.png Binary files differnew file mode 100644 index 0000000..0ed1d67 --- /dev/null +++ b/help/en/images/project_functions_menu3.png diff --git a/help/en/images/project_functions_search.png b/help/en/images/project_functions_search.png Binary files differnew file mode 100644 index 0000000..d76cac6 --- /dev/null +++ b/help/en/images/project_functions_search.png diff --git a/help/en/images/project_generate_keys.png b/help/en/images/project_generate_keys.png Binary files differnew file mode 100644 index 0000000..54b4385 --- /dev/null +++ b/help/en/images/project_generate_keys.png diff --git a/help/en/images/project_options.png b/help/en/images/project_options.png Binary files differnew file mode 100644 index 0000000..1f634e7 --- /dev/null +++ b/help/en/images/project_options.png diff --git a/help/en/images/project_script.png b/help/en/images/project_script.png Binary files differnew file mode 100644 index 0000000..5b24b42 --- /dev/null +++ b/help/en/images/project_script.png diff --git a/help/en/images/properties_calc.png b/help/en/images/properties_calc.png Binary files differnew file mode 100644 index 0000000..0d19e4a --- /dev/null +++ b/help/en/images/properties_calc.png diff --git a/help/en/images/properties_directory.png b/help/en/images/properties_directory.png Binary files differnew file mode 100644 index 0000000..ce674da --- /dev/null +++ b/help/en/images/properties_directory.png diff --git a/help/en/images/properties_dump.png b/help/en/images/properties_dump.png Binary files differnew file mode 100644 index 0000000..c00b733 --- /dev/null +++ b/help/en/images/properties_dump.png diff --git a/help/en/images/properties_dump_goto.png b/help/en/images/properties_dump_goto.png Binary files differnew file mode 100644 index 0000000..f35a931 --- /dev/null +++ b/help/en/images/properties_dump_goto.png diff --git a/help/en/images/properties_export.png b/help/en/images/properties_export.png Binary files differnew file mode 100644 index 0000000..619a282 --- /dev/null +++ b/help/en/images/properties_export.png diff --git a/help/en/images/properties_import.png b/help/en/images/properties_import.png Binary files differnew file mode 100644 index 0000000..98fd578 --- /dev/null +++ b/help/en/images/properties_import.png diff --git a/help/en/images/properties_resources.png b/help/en/images/properties_resources.png Binary files differnew file mode 100644 index 0000000..b09174c --- /dev/null +++ b/help/en/images/properties_resources.png diff --git a/help/en/images/properties_segments.png b/help/en/images/properties_segments.png Binary files differnew file mode 100644 index 0000000..a48f777 --- /dev/null +++ b/help/en/images/properties_segments.png diff --git a/help/en/images/visual_studio_map.png b/help/en/images/visual_studio_map.png Binary files differnew file mode 100644 index 0000000..b04bd53 --- /dev/null +++ b/help/en/images/visual_studio_map.png diff --git a/help/en/images/watermarks_add.png b/help/en/images/watermarks_add.png Binary files differnew file mode 100644 index 0000000..4ed0ecd --- /dev/null +++ b/help/en/images/watermarks_add.png diff --git a/help/en/images/watermarks_menu.png b/help/en/images/watermarks_menu.png Binary files differnew file mode 100644 index 0000000..97470d3 --- /dev/null +++ b/help/en/images/watermarks_menu.png diff --git a/help/en/images/watermarks_search.png b/help/en/images/watermarks_search.png Binary files differnew file mode 100644 index 0000000..5840691 --- /dev/null +++ b/help/en/images/watermarks_search.png diff --git a/help/en/images/watermarks_setup.png b/help/en/images/watermarks_setup.png Binary files differnew file mode 100644 index 0000000..a074978 --- /dev/null +++ b/help/en/images/watermarks_setup.png diff --git a/help/en/images/weblm_1.png b/help/en/images/weblm_1.png Binary files differnew file mode 100644 index 0000000..26bdaee --- /dev/null +++ b/help/en/images/weblm_1.png diff --git a/help/en/images/weblm_2.png b/help/en/images/weblm_2.png Binary files differnew file mode 100644 index 0000000..6791edc --- /dev/null +++ b/help/en/images/weblm_2.png diff --git a/help/en/info.htm b/help/en/info.htm new file mode 100644 index 0000000..b8b6e35 --- /dev/null +++ b/help/en/info.htm @@ -0,0 +1,40 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>"Details" section</title> + <style type="text/css"> + </style> +</head> + +<body> + <h1>"Details" section</h1> + <p>The "Details" section displays various information about the protected application. +It also allows you to exclude certain segments of data or resources from packing. Changes you make in this section are saved to the project file.</p> + <p><img src="images/properties_directory.png" /></p> + <p>"Details" section contains the following subsections:</p> + <ul> + <li><a href="info_directories.htm">Directories</a></li> + <li><a href="info_segments.htm">Segments</a></li> + <li><a href="info_imports.htm">Imports</a></li> + <li><a href="info_exports.htm">Exports</a></li> + <li><a href="info_resources.htm">Resources</a></li> + <li><a href="info_calc.htm">Calculator</a></li> + <li><a href="info_dump.htm">Dump</a></li> + </ul> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/info_calc.htm b/help/en/info_calc.htm new file mode 100644 index 0000000..5866395 --- /dev/null +++ b/help/en/info_calc.htm @@ -0,0 +1,31 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>"Calculator" section</title> + <style type="text/css"> + </style> +</head> + +<body> + <h1>"Calculator" section</h1> + + <p>Allows you to determine the file offset by the virtual address or vice versa:</p> + <p><img src="images/properties_calc.png" /></p> + + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/info_directories.htm b/help/en/info_directories.htm new file mode 100644 index 0000000..eabe5ca --- /dev/null +++ b/help/en/info_directories.htm @@ -0,0 +1,30 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>"Directories" section</title> + <style type="text/css"> + </style> +</head> + +<body> + <h1>"Directories" section</h1> + + <p>Displays information about file directories:</p> + <p><img src="images/properties_directory.png" /></p> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/info_dump.htm b/help/en/info_dump.htm new file mode 100644 index 0000000..468e128 --- /dev/null +++ b/help/en/info_dump.htm @@ -0,0 +1,35 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>"Dump" section</title> + <style type="text/css"> + </style> +</head> + +<body> + <h1>"Dump" section</h1> + + <p>Displays the memory dump of the protected application as machine language codes and assembler instructions:</p> + <p><img src="images/properties_dump.png" /></p> + + <p>The "Go To Address" button on the toolbar allows you to go to a specified address of the protected application:</p> + <p><img src="images/properties_dump_goto.png" /></p> + <p>To quickly go to a certain function, start typing its name in the quick search box. You can also enter its exact address.</p> + + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/info_exports.htm b/help/en/info_exports.htm new file mode 100644 index 0000000..c5b3d31 --- /dev/null +++ b/help/en/info_exports.htm @@ -0,0 +1,28 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>"Exports" section</title> +</head> + +<body> + <h1>"Exports" section</h1> + + <p>Displays information about exports the file has:</p> + <p><img src="images/properties_export.png" /></p> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/info_imports.htm b/help/en/info_imports.htm new file mode 100644 index 0000000..e38d478 --- /dev/null +++ b/help/en/info_imports.htm @@ -0,0 +1,28 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>"Imports" section</title> +</head> + +<body> + <h1>"Imports" section</h1> + + <p>Displays information about imported functions and libraries:</p> + <p><img src="images/properties_import.png" /></p> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/info_resources.htm b/help/en/info_resources.htm new file mode 100644 index 0000000..6eabd8d --- /dev/null +++ b/help/en/info_resources.htm @@ -0,0 +1,31 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>"Resources" section</title> +</head> + +<body> + <h1>"Resources" section</h1> + + <p>Displays information about resources:</p> + <p><img src="images/properties_resources.png" /></p> + <ul> + <li><strong> Excluded from packing</strong> - a resource can be excluded from <a href="project_options.htm#PackOutputFile">packing</a>.</li> + </ul> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/info_segments.htm b/help/en/info_segments.htm new file mode 100644 index 0000000..60a80cb --- /dev/null +++ b/help/en/info_segments.htm @@ -0,0 +1,32 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>"Segments" section</title> +</head> + +<body> + <h1>"Segments" section</h1> + + <p>Displays information about segments:<p></p> + <p><img src="images/properties_segments.png" /></p> + <ul> + <li><strong>Excluded from memory protection</strong> - a segment can be excluded from <a href="project_options.htm#MemoryProtection">memory protection</a>.</li> + <li><strong> Excluded from packing</strong> - a segment can be excluded from <a href="project_options.htm#PackOutputFile">packing</a>.</li> + </ul> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html>
\ No newline at end of file diff --git a/help/en/main_menu.htm b/help/en/main_menu.htm new file mode 100644 index 0000000..895e79d --- /dev/null +++ b/help/en/main_menu.htm @@ -0,0 +1,41 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Main menu</title> + <style type="text/css"> +/*<![CDATA[*/ + div.c2 {text-align: center} + /*]]>*/ + </style> +</head> + +<body> + <h1>Main menu</h1> + + <p>The main menu consists of the following items:</p> + + <ul> + <li><a href="menu_file.htm">File</a></li> + <li><a href="menu_edit.htm">Edit</a></li> + <li><a href="menu_project.htm">Project</a></li> + <li><a href="menu_tools.htm">Tools</a></li> + <li><a href="menu_help.htm">Help</a></li> + </ul> + + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/main_window.htm b/help/en/main_window.htm new file mode 100644 index 0000000..22ccb2b --- /dev/null +++ b/help/en/main_window.htm @@ -0,0 +1,42 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Main window</title> +</head> + +<body> + <h1>Main window</h1> + + <p>Main window consists of the following elements:</p> + + <ul> + <li><a href="main_menu.htm">Main menu</a></li> + <li><a href="toolbar.htm">Toolbar</a></li> + <li>Control panel divided to three sections: + <ul> + <li><a href="project.htm">"Project" section</a></li> + <li><a href="functions.htm">"Functions" section</a></li> + <li><a href="info.htm">"Details" section</a></li> + </ul> + </li> + <li>Compilation log</li> + </ul> + <p><img src="images/main_window.png" /></p> + + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/manager/activation.htm b/help/en/manager/activation.htm new file mode 100644 index 0000000..415790e --- /dev/null +++ b/help/en/manager/activation.htm @@ -0,0 +1,54 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="../default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Activation system</title> +</head> + +<body> + <h1>Activation system</h1> + + <h3>What is it?</h3> + + <p>Activation is a two-stage process of registering an application. On the first step (usually, directly after the purchase) a user receives an activation code that usually looks like XXXX-YYYY-ZZZZ. On the second stage, the customer enters the code to the application, the application connects to the server of the developer via the Internet, the server checks the activation code and returns a serial number to the application tied to the given activation code and usually locked to user's hardware.</p> + + <p>Such approach allows the developer to control license usage by customers, prevent licenses from leaking and offers additional possibilities, for example, making demo licenses or offering reliable trial periods.</p><strong>Why do I need it?</strong> + + <p>The activation system gives a software developer a lot of possibilities, for instance:</p> + + <ul> + <li><strong>Short serial numbers</strong> - long serial numbers are great, except they are long. User may make a typo while entering them, e-mail client break those keys or replace some symbols. At the same time, long serial numbers can hold a sufficient volume of additional information. Activation codes can resolve all issues of long serial numbers while taking the most benefit from their advantages.</li> + + <li><strong>Installation control</strong> - all activations are available to the developer online in real-time. Each activation can be monitored, analyzed, blocked. The developer can provide support to users and so on.</li> + + <li><strong>Trial periods</strong> - you can create time-limited serial numbers by using product "modes".</li> + + <li><strong>Subscriptions</strong> - subscriptions are similar to trial periods, but are offered for a fee. You can sell the right to use the program for a specified time to a user, just like antiviruses do. Simply sell activation codes for each service year.</li> + </ul> + + <p>You can find more detailed information about the activation system in the corresponding <a href= + "http://vmpsoft.com/products/web-license-manager/" target= + "_blank">section</a> of our website.</p> + + <h3>What do I need?</h3> + + <p>VMProtect Ultimate features several <a href= + "activation/api.htm">functions</a> for relatively easy implementation of both online and offline activation. You will also need + <a href="activation/weblm.htm">Web License Manager</a> installed on your server. Finally, you should <a href="activation/vmprotect.htm">configure</a> + the protection project in VMProtect, to make the activation module know the URL of the WebLM server.</p><br /> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/manager/activation/api.htm b/help/en/manager/activation/api.htm new file mode 100644 index 0000000..4a75ad2 --- /dev/null +++ b/help/en/manager/activation/api.htm @@ -0,0 +1,174 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href= + "../../default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Activation API</title> + <style type="text/css"> +/*<![CDATA[*/ + th {text-align:left;} + table {border-collapse:collapse; margin-top: 4px;} + td,th {border: 1px solid #B0B0B0; padding-left:10;padding-right:10;} + /*]]>*/ + </style> +</head> + +<body> + <h1>Activation API</h1> + + <p>Activation API contains only 4 functions. Two for online activation and other two for offline activation when the computer has no access to the Internet. Activation API is intended to work in cooperation with Web License Manager, so a developer still should invoke licensing system API to use serial numbers obtained from WebLM.</p><strong id= + "VMProtectActivateLicense">VMProtectActivateLicense</strong> + + <p>The function passes the activation code to the server and returns a serial number for this specific computer. Otherwise, an <a href="#codes">error code</a> is returned.</p> + <pre class="code">int VMProtectActivateLicense(const char *code, char *serial, int size); +</pre> + + <p>The <strong>code</strong> parameter holds the activation code obtained from Web License Manager during the license purchase process. + The <strong>serial</strong> parameter specifies a memory block of the given + <strong>size</strong>, where the serial number generated by WebLM is put to.</p><strong id= + "VMProtectDeactivateLicense">VMProtectDeactivateLicense</strong> + + <p>This function passes a serial number to the server for deactivation. + Possible return codes are listed <a href= + "#codes">below</a>.</p> + <pre class="code">int VMProtectDeactivateLicense(const char *serial); +</pre> + + <p>The <strong>serial</strong> parameters contains the serial number (not the activation code) obtained from WebLM earlier during activation.</p><strong id= + "VMProtectGetOfflineActivationString">VMProtectGetOfflineActivationString</strong><br /> + + <strong id= + "VMProtectGetOfflineDeactivationString">VMProtectGetOfflineDeactivationString</strong> + + <p>These two functions work similar to the previous two, except they do not try to connect to the WebLM server. Instead, they return a text block that a user should copy to a computer connected to the Internet, open the WebLM offline activation form and paste the text there.</p> + <pre class="code">int VMProtectGetOfflineActivationString(const char *code, char *buf, int size); +int VMProtectGetOfflineDeactivationString(const char *serial, char *buf, int size); +</pre> + + <p>The <strong>code</strong> and <strong>serial</strong> parameters are similar to those of the online version of these functions. The + <strong>buf</strong> parameter should point to a buffer of 1000 bytes or more where the text block for the offline activation form will be copied to. Possible error codes are listed <a href= + "#codes">below</a>.</p> + + <h3 id="codes">Possible error codes</h3> + + <table border="1" cellspacing="0" cellpadding="2"> + <tr> + <th>Code</th> + + <th>Value</th> + + <th>Description</th> + </tr> + + <tr> + <td>ACTIVATION_OK</td> + + <td>0</td> + + <td>Activation is successful. The serial number is put to the + <strong>serial</strong> variable.</td> + </tr> + + <tr> + <td>ACTIVATION_SMALL_BUFFER</td> + + <td>1</td> + + <td>The buffer is too small to hold the serial number. The minimum buffer size is calculated as: bits / 8 * 3 / 2 + N, + where bits is the length of the RSA key in bits, and N is a "security constant" - additional bytes for possible line breaks and other special symbols. We recommend using at least 10.</td> + </tr> + + <tr> + <td>ACTIVATION_NO_CONNECTION</td> + + <td>2</td> + + <td>The activation module couldn't connect to Web License + Manager.</td> + </tr> + + <tr> + <td>ACTIVATION_BAD_REPLY</td> + + <td>3</td> + + <td>The activation server returned an unexpected result. This means some configuration issues on the server, wrong server URL or a hack attempt.</td> + </tr> + + <tr> + <td>ACTIVATION_BANNED</td> + + <td>4</td> + + <td>This activation code is banned on the server by the software vendor via the WebLM interface (for example, if the key has leaked or pirated). Not to be confused with ACTIVATION_ALREADY_USED.</td> + </tr> + + <tr> + <td>ACTIVATION_CORRUPTED</td> + + <td>5</td> + + <td>Something has gone completely wrong. The error is produced by the activation module self-check system and usually means a hacking attempt. If you've got this error, all further operations with serial numbers and activation are not safe.</td> + </tr> + + <tr> + <td>ACTIVATION_BAD_CODE</td> + + <td>6</td> + + <td>The specified code is not found in the database of the activation server. Perhaps, a user made a mistake while entering the code, so we can ask him or her to check if everything all right.</td> + </tr> + + <tr> + <td>ACTIVATION_ALREADY_USED</td> + + <td>7</td> + + <td>The activation counter for this code is depleted and all further activations are impossible. This doesn't mean the code is bad or banned. The code is good, but it just can't be activated any more. The user should contact the software vendor and purchase additional licenses or uninstall the software on other computer to increase the value of the activation counter on the server.</td> + </tr> + + <tr> + <td>ACTIVATION_SERIAL_UNKNOWN</td> + + <td>8</td> + + <td>Activation error. The given serial number is not found in the database on the server. Therefore, deactivation is impossible.</td> + </tr> + + <tr> + <td>ACTIVATION_EXPIRED</td> + + <td>9</td> + + <td>Activation error. Means the activation period of the code has expired.</td> + </tr> + + <tr> + <td>ACTIVATION_NOT_AVAILABLE</td> + + <td>10</td> + + <td>This error means activation/deactivation is unavailable.</td> + </tr> + + </table> + + <h3>Tips and tricks</h3> + + <p>Activation API is pretty simple, so you shouldn't experience difficulties with it. Do not forget to offer a way to activate the program offline for users who have problems with the Internet. Also, don't forget, the Activation API does not save the serial number it receives and does not pass it to the licensing module - this should be done by the developer. You don't have to call Activation API on every launch of the application. You just need to call it once, get a serial number from WebLM, save it where appropriate and then use this saved copy.</p><br /> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/manager/activation/vmprotect.htm b/help/en/manager/activation/vmprotect.htm new file mode 100644 index 0000000..cc8f8aa --- /dev/null +++ b/help/en/manager/activation/vmprotect.htm @@ -0,0 +1,33 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href= + "../../default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Configuring activation in VMProtect</title> + <style type="text/css"> + </style> +</head> + +<body> + <h1>Configuring activation in VMProtect</h1> + + <p>For the <a href="api.htm">Activation API</a> to work, the WebLM URL is required, so you should specify it in the project settings in VMProtect. To do this, open VMProtect and switch to the options section:</p><br /><img src="../../images/activation_setup.png" alt="Configuring the activation server" /> + + <p>Enter the address to the "Activation Server" field. The address should look as: <em>http://yourserver/weblm + path</em>. This is the first place to check if you face problems with online activation.</p><br /> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/manager/activation/weblm.htm b/help/en/manager/activation/weblm.htm new file mode 100644 index 0000000..cd68ed6 --- /dev/null +++ b/help/en/manager/activation/weblm.htm @@ -0,0 +1,43 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href= + "../../default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Activation in Web License Manager</title> + <style type="text/css"> + </style> +</head> + +<body> + <h1>Activation in Web License Manager</h1> + + <p>You can find the detailed Web License Manager description on <a href= + "http://vmpsoft.com/products/web-license-manager/" target= + "_blank">our website</a>, and here we merely provide minimum steps required to create an activation code for use with the Activation API.</p> + + <p>First, enter Web License Manager (you can use the demo on our website) and create a product. Then export the product as a VMProtect project to be able to configure licensing and activation. After the project is set up, all check are added to the code of your app and the executable is protected, click the "Add New Code" link on the left panel in WebLM:</p> + <p><img src="../../images/weblm_1.png" /></p> + + <p>Select the product you need from the upper drop-down list and fill in the rest of form with the data you want to put into the serial number. Click the "Save" button. You should see the activation code you can use to debug Activation API.</p> + <p><img src="../../images/weblm_2.png" /></p> + + <p>You can study rich capabilities of Web License Manager (such as integration to e-commerce providers and automatic activation code generation) in + the <a href= + "http://vmpsoft.com/products/web-license-manager/" target= + "_blank">online user manual</a>.</p><br /> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/manager/features.htm b/help/en/manager/features.htm new file mode 100644 index 0000000..a2bd877 --- /dev/null +++ b/help/en/manager/features.htm @@ -0,0 +1,71 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="../default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Licensing system features</title> + <style type="text/css"> + </style> +</head> + +<body> + <h1>Licensing system features</h1> + + <h3>Secure serial numbers</h3> + + <p>The license system uses an asymmetric algorithm to encrypt serial numbers. The number is encrypted with a private key that only the developer has. The protected product uses the corresponding public key to decrypt the serial number and checks it. Due to the length of keys the system uses (1024 bit or higher for RSA) it is virtually impossible to compute the private key and make a key generator for the application.</p> + + <h3 id="lock">Locking the code to a serial number</h3> + + <p>VMProtect allows execution of a part of the program code on a virtual machine. The set of commands of the virtual machine changes on every build of the protected program. The licensing system allows to encrypt a part of virtual machine commands with the key stored in a serial number. Therefore, even if a hacker modifies a conditional jump in the program, the code still will not work without the correct serial number. And since code decryption is managed by the virtual machine, the decryption algorithm is hard to analyze even if the serial number is available. + </p> + + <h3>Limiting the period of free upgrades</h3> + + <p>The licensing system can write a date into the key so that all application versions after that date will not work with this key. This mechanism allows you to limit the period of free upgrades. For example, upon purchase the current date plus one year is written to the key, so a user will be able to download new versions from the website within one year. The key will work in these versions only. When the one-year period ends, a user has a choice: either use the last working version of the program or purchase an update for one more year.</p> + + <h3>Key expiration date</h3> + + <p>The licensing system allows you to write a date into the key, after which that key stops working. This is a convenient option for products that require systematic updates. For example, upon purchase the current date plus one year is put to the key, and the program works for the given user for one year. Unlike the period of free upgrades, the user has no choice here - he has to purchase a new license if he wants to continue using the program.</p> + + <h3>Limiting the program operation time</h3> + + <p>The licensing system allows you to limit the maximum operation time of a copy of the program. This proves to be useful in many demo applications. For example, a user wants to test a full-featured copy of the program. In this case you can send to him or her a serial number that limits the maximum session time of the program with say ten minutes. After that, the program stops functioning. This option is also convenient for various server applications, where a user can't easily restart the program.</p> + + <h3>Hardware locking</h3> + + <p>The licensing system allows the developer to receive a hardware identifier of user's PC based on information about CPU, network card and OS. The licensing system can produce a serial number that will be only valid on that hardware only. This option allows you to limit usage of the application to several computers.</p> + + <h3>Black list</h3> + + <p>If a serial number is compromised, the licensing system allows adding such a number into the black list. The blocked serial number will not work in all further versions of the application.</p> + + <h3>Data storage</h3> + + <p>The licensing system stores in a serial number and provides to the program the following data: a user name, an e-mail and up to 255 bytes of arbitrary information (the so called custom user data). You can use this capability to show additional information in the "About" window of the program, to implement additional security checks if the entered serial number, to store constants available in the registered version of the product only and so on.</p> + + <h3>Time-limited demo versions</h3> + + <p>With the <a href="activation.htm">activation</a> system, a software developer can automatically build time-limited serial numbers locked to user's hardware. This allows you to setup a secure trial period (demo) for an application, because VMProtect does not try to hide trial marks on user's computer, and instead generates a working, but time-limited serial number. Activation is carried out over the Internet, but the activation API also provides the offline activation mode.</p><br /> + <hr noshade="noshade" size="1" /> + + <h3>What can't the system do and why</h3> + + <h3>100% secure hardware lock</h3> + + <p>Besides the licensing system allows locking a serial number to a hardware identifier, you should understand that most of hardware data is received using operating system means, so a hacker can intercept them and modify this information. The licensing system uses certain ways to minimize this risk, but if you need 100% secure hardware lock, we recommend to use a solution based on USB keys also supported by VMProtect.</p><br /> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/manager/howitworks.htm b/help/en/manager/howitworks.htm new file mode 100644 index 0000000..3a8f3f6 --- /dev/null +++ b/help/en/manager/howitworks.htm @@ -0,0 +1,42 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="../default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>How the licensing system works</title> + <style type="text/css"> + </style> +</head> + +<body> + <h1>How the licensing system works</h1> + + <h3>Application protection</h3> + + <p>To protect an application, VMProtect embeds the special code into it. This code checks serial numbers using information specified in the "Licensing" subsection of the "Project" section. A public key is embedded to the application and is used then to decrypt serial numbers. Also, the protection date and some additional information the licensing requires to work is put into the application.</p> + + <h3>Creating serial numbers</h3> + + <p>Serial numbers can be created in the <a href= + "licenses.htm">"Licensing"</a> section of the "Project" section or using third-party applications + - <a href="keygen/index.htm">key generators</a>. A serial number is a set of data about a customer encrypted using the asymmetric algorithm. The serial number then is passed to the customer, he or she enters it to the program, and the licensing system checks it.</p> + + <h3>Checking a serial number in the program</h3> + + <p>The licensing system has + <a href="usage/api.htm">several functions</a> a program can use to work with serial numbers. The program sends a serial number to the licensing system and queries information about it. The licensing system returns the state of a serial number (valid/invalid and why) and also can provide detailed information about the serial numbers including a user name, an e-mail, the expiration date of this serial number and so on. The protected program analyzes serial number information and decides whether or not to continue operation and to limit the functionality.</p><br /> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/manager/index.htm b/help/en/manager/index.htm new file mode 100644 index 0000000..81585e9 --- /dev/null +++ b/help/en/manager/index.htm @@ -0,0 +1,35 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="../default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Licensing system</title> +</head> + +<body> + <h1>Licensing system</h1> + + <p>The licensing system creates and checks for validity serial numbers. It supports limiting the protected software by date and time, locking it to specific hardware, encrypting the code with a serial number, limiting the period of free updates and many more. The system is based on asymmetric cryptographic algorithms to minimize chances that an unauthorized serial number generator will be built. To protect the licensing system itself, VMProtect uses virtualization therefore minimizing chances that the application will be cracked or patched on the code level.</p> + + <ul> + <li><a href="features.htm">Licensing system features</a></li> + <li><a href="howitworks.htm">How the licensing system works</a></li> + <li><a href="licenses.htm">Managing licenses: creating, changing, blocking and so on</a></li> + <li><a href="usage/index.htm">Example of how to integrate the system to your application</a></li> + <li><a href="keygen/index.htm">Automatic serial number generation</a></li> + </ul> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/manager/keygen/algorithms.htm b/help/en/manager/keygen/algorithms.htm new file mode 100644 index 0000000..e1a50c9 --- /dev/null +++ b/help/en/manager/keygen/algorithms.htm @@ -0,0 +1,47 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href= + "../../default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Serial number encryption algorithms</title> +</head> + +<body> + <h1>Serial number encryption algorithms</h1> + + <p>The security of a key in the licensing system is based on asymmetric cryptography algorithms. The current version implements the RSA algorithm with the key length from 1024 to 16384 bits. Future versions are planned to implement other algorithms based on ECC as well as symmetric+asymmetric combined cryptography.</p> + + <p>The algorithm used is unique for each product. Keys made with one algorithm cannot be used with another one, this means changing algorithms after at least one license is created is not allowed. The protection module in the protected program "knows" which algorithm the serial number is encrypted with and will not accept keys made with other algorithms or with the same algorithm but different parameters (say, different key length).</p> + + <h3>RSA Algorithm</h3> + + <p>A serial number is encrypted with the RSA algorithm as follows:</p> + + <ul> + <li><strong>Adding random data to the beginning of the serial number</strong> - the method is based on RFC2313, but the implementation is slightly different. The following bytes are added to the beginning of the key: 00 02 NN...NN 00, where NN..NN + are from 8 to 16 random non-zero bytes. The number of bytes is random, but the system takes into account the length of the key and its maximum capacity.</li> + + <li><strong>Adding random data to the end of the serial number</strong> + - the total number of bytes in a serial number must be equal to the number of bits in keys of the algorithm divided by 8. + The serial number is appended with the corresponding number of bytes holding random data. As a result, the following serial number format is produced: 00 02 NN..NN 00 DD..DD MM..MM, where NN is a set of random non-zero bytes, DD is the original serial number, MM is a set of random bytes (including zeros). The summary length of the sequence should be equal to the number of bits in keys of the algorithm divided by 8</li> + + <li><strong>Encryption</strong> goes using a typical procedure implemented in many libraries to process big numbers. The PHP generator contains all the required information.</li> + + <li><strong>Packing</strong> - the set of bytes obtained after encryption is encoded to base-64 — this is a serial number that goes to a customer.</li> + </ul><br /> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/manager/keygen/index.htm b/help/en/manager/keygen/index.htm new file mode 100644 index 0000000..097299f --- /dev/null +++ b/help/en/manager/keygen/index.htm @@ -0,0 +1,70 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href= + "../../default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Serial number generators</title> +</head> + +<body> + <h1>Serial number generators</h1><strong>What are they for?</strong> + + <p>Apart from VMProtect, other software can generate serial numbers too. This is necessary to automate sending serial numbers. A customer purchases the product, an e-commerce agent sends an HTTP query to the website of the vendor, the generator runs on the server and produces a serial number based on customer's data. The serial number is sent to the customer and to the vendor. The vendor then adds the serial to VMProtect manually using the import license dialog.</p><strong>How it works</strong> + + <p>The licensing system of VMProtect is based on asymmetric algorithms, that is why a secret product key is required to generate a serial number. You can export this key in the project properties window and pass it to the generator in any suitable way.</p> + + <p>The generator is called by the e-commerce agent using an HTTP query. A PHP generator can be called directly, a DLL-based generator - indirectly, but the principle is the same:</p> + + <ul> + <li>Receive user data from the e-commerce agent</li> + + <li>Add all required information specified by the vendor</li> + + <li>Generate a serial number</li> + + <li>Encrypt it with one of algorithms</li> + + <li>Send the result to the e-commerce agent</li> + </ul><strong>Are there any existing generators?</strong> + + <p>The licensing system comes with three ready to use serial number generators <a href="keygen_dll.htm">as DLL</a>, + <a href="keygen_net.htm">for the .Net platform</a> and <a href= + "keygen_php.htm">on PHP</a>.</p><strong>Can I make my own generator?</strong> + + <p>Yes, you can. The format of the serial number is <a href= + "serial_format.htm">here</a>, serial number encryption algorithms are described <a href= + "algorithms.htm">here</a>.</p><strong>Is it safe?</strong> + + <p>Generally, yes, this is safe. However, you should follow these recommendations:</p> + + <ul> + <li><strong>Use HTTPS</strong> - if your e-commerce provider can send HTTPS queries, and your web hosting provider can answer such requests - you should prefer this variant over the typical HTTP, because in this case all data are transmitted in the encrypted form and the generated serial number cannot be intercepted.</li> + + <li><strong>"Hide" your generator</strong> - make sure no one can open the generator occasionally. The + www.site.com/keygen.php address is a bad idea. While + www.site.com/abc123.php is much better. Make sure you do not put any external links to the key generator, it isn't listed in website directories, and don't put it into any service file like robot.txt. The less is known about the location of the generator, the better. Optionally, you can even place the generator on another website.</li> + + <li><strong>Make sure it is the e-commerce agent who calls the generator</strong> - + the program processing queries from the agent should check the IP address of the caller. E-commerce providers usually publish the IP-range the use to query serial number generators. Find that list at your agent and add a check to the program. If IP address sending a query lies beyond the specified IP range, do not produce comprehensible error messages. Either do not return anything or produce a simple 404. + Do not give any clues to why the query has failed.</li> + + <li><strong>Check input parameters</strong> - product settings in the e-commerce agent's control panel usually allow you to specify a query string the agent should make to receive a license. For instance, you want to receive user name, e-mail address, date of purchase and the order id. So make sure all these parameters are passed and all of them have the correct format. Do not produce any response to erroneous queries. Send a message to your own e-mail whenever an erroneous query to the generator is made. This should help to investigate the issue.</li> + + <li><strong>Add a "password"</strong> specify an additional parameter in the query sent by the e-commerce agent, a password. It should have an non-obvious name and value. Check this parameter from the receiving side. If the value is wrong, or the parameter is not specified - do not generate a serial number.</li> + </ul><br /> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/manager/keygen/keygen_dll.htm b/help/en/manager/keygen/keygen_dll.htm new file mode 100644 index 0000000..d568180 --- /dev/null +++ b/help/en/manager/keygen/keygen_dll.htm @@ -0,0 +1,199 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href= + "../../default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Windows-version</title> +</head> + +<body> + <h1>Windows-version</h1> + + <h3>Description</h3> + + <p>Windows key generators are DLL-files for x86 and x64 platforms, a C language header file and an MSVC-compatible lib-file. Therefore, the library can be both linked statically and loaded dynamically.</p> + + <p>All files of the generator are located in the + <strong>Keygen\DLL</strong> folder. A test application generating serial numbers is also there.</p> + + <h3>Generator API</h3> + + <p>The generator exports just two functions: the first one generates a serial number, while the second one frees up memory allocated by the first one. Let's start with the first and the main one:</p> + <pre class="code"><strong>VMProtectErrors</strong> __stdcall <strong>VMProtectGenerateSerialNumber</strong>( + <strong>VMProtectProductInfo *</strong> pProductInfo, + <strong>VMProtectSerialNumberInfo *</strong> pSerialInfo, + <strong>char **</strong> pSerialNumber + ); +</pre> + + <p>The first parameter is a pointer to the + <strong>VMProtectProductInfo</strong> structure, which contents are uploaded to VMProtect (see <a href= + "../licenses.htm#export">Exporting product parameters</a>). + The structure contains product private key, the algorithm used and the identifier of the product. More details on filling this structure follow below.</p> + + <p>The second parameter is a pointer to the + <strong>VMProtectSerialNumberInfo</strong> structure, which contents are moved to the generated serial number. The structure holds all fields of a serial number and a bit mask that defines which fields should be written to the serial number.</p> + <pre class="code">struct <strong>VMProtectSerialNumberInfo</strong> +{ + <strong>INT</strong> flags; + <strong>wchar_t *</strong> pUserName; + <strong>wchar_t *</strong> pEMail; + <strong>DWORD</strong> dwExpDate; + <strong>DWORD</strong> dwMaxBuildDate; + <strong>BYTE</strong> nRunningTimeLimit; + <strong>char *</strong> pHardwareID; + <strong>size_t</strong> nUserDataLength; + <strong>BYTE *</strong> pUserData; +}; +</pre> + + <p>The <strong>flags</strong> field contains bit flags from the + <strong>VMProtectSerialNumberFlags</strong> set described before the structure:</p> + + <ul> + <li><strong>HAS_USER_NAME</strong> - put the user name from the + <strong>pUserName</strong> variable into the serial number.</li> + + <li><strong>HAS_EMAIL</strong> - put the e-mail from the + <strong>pEMail</strong> variable into the serial number.</li> + + <li><strong>HAS_EXP_DATE</strong> - the serial number will expire after the date specified in the + <strong>dwExpDate</strong> variable.</li> + + <li><strong>HAS_MAX_BUILD_DATE</strong> - the serial number will only work with version of the product built up to the date specified in the <strong>dwMaxBuildDate</strong> variable.</li> + + <li><strong>HAS_TIME_LIMIT</strong> - the program stops working after the time specified in the + <strong>nRunningTimeLimit</strong> variable expires (the time is specified in minutes and shouldn't exceed 255).</li> + + <li><strong>HAS_HARDWARE_ID</strong> - the program works only on hardware with the id specified in the <strong>pHardwareID</strong> variable.</li> + + <li><strong>HAS_USER_DATA</strong> - put custom user data of + <strong>nUserDataLength</strong> length at the address of <strong>pUserData</strong> to the serial number.</li> + </ul> + + <p>The third parameter is a pointer to a pointer. The address of the generated serial number is written there. After generating the serial number, it should be copied, and the address must be passed to the second API function of the generator that will free memory taken by the serial number.</p> + <pre class="code"><strong>void</strong> __stdcall <strong>VMProtectFreeSerialNumberMemory</strong>(<strong>char *</strong> pSerialNumber); +</pre> + + <p>The <strong>VMProtectGenerateSerialNumber</strong> function + returns a <strong>VMProtectErrors</strong> value that either contains 0 if the serial number is successfully generated, or an error code. + Possible error codes are:</p> + + <ul> + <li><strong>ALL_RIGHT</strong> - no errors, the serial number is generated.</li> + + <li><strong>UNSUPPORTED_ALGORITHM</strong> - an incorrect key encryption algorithm is passed in the first parameter of the function.</li> + + <li><strong>UNSUPPORTED_NUMBER_OF_BITS</strong> - an incorrect number of bits is passed in the first parameter of the function.</li> + + <li><strong>USER_NAME_IS_TOO_LONG</strong> - the length of the UTF-8 encoded user name exceeded 255 byte.</li> + + <li><strong>EMAIL_IS_TOO_LONG</strong> - the length of the UTF-8 encoded user e-mail exceeded 255 byte.</li> + + <li><strong>USER_DATA_IS_TOO_LONG</strong> - the length of the user data exceeded 255 byte.</li> + + <li><strong>HWID_HAS_BAD_SIZE</strong> - the hardware identifier has incorrect size.</li> + + <li><strong>PRODUCT_CODE_HAS_BAD_SIZE</strong> - the identifier of the product passed in the first parameter of the function has incorrect size.</li> + + <li><strong>SERIAL_NUMBER_TOO_LONG</strong> - the serial number is too long and can't fit the number of bits specified in the algorithm.</li> + + <li><strong>BAD_PRODUCT_INFO</strong> - the first parameter of the function is incorrect or NULL.</li> + + <li><strong>BAD_SERIAL_NUMBER_INFO</strong> - the second parameter of the function is incorrect or NULL.</li> + + <li><strong>BAD_SERIAL_NUMBER_CONTAINER</strong> - the third parameter of the function doesn't point to memory to write the serial number address to.</li> + + <li><strong>NOT_EMPTY_SERIAL_NUMBER_CONTAINER</strong> - the third parameter of the function doesn't point to an empty memory cell, the cell must be NULL.</li> + + <li><strong>BAD_PRIVATE_EXPONENT</strong> - the first parameter of the function contains an incorrect value of the private exponent.</li> + + <li><strong>BAD_MODULUS</strong> - the first parameter of the function contains an incorrect value of modulus.</li> + </ul> + + <p>Errors can be of two categories: those caused by incorrect parameters or incorrect value of the first parameter, and all the rest. First category errors are rare and they indicate incorrect configuration of the structure. You should upload the product information again and check if the structure is filled correctly. An example of a proper filling of the structure can be found below.</p> + + <p>Second category errors are caused by an attempt to put more data to the key than it can hold with its size. In this case we recommend to send a message to the e-commerce provider containing a text like "The key will be sent in 24 hours" instead of the actual serial number, and send all the required information to your own e-mail. In this case, the key is generated manually in VMProtect, some data are truncated to fit all crucial information to the maximum key size.</p> + + <h3>Example of usage</h3> + + <p>Below is a code example that calls the above functions and generates a serial number. Notice the block of code in the very beginning. The example will not work until you replace it with the one exported from VMProtect for your product:</p> + <pre class="code">////////////////////////////////////////////////////////////////////////// +// !!! this block should be generated by VMProtect !!! /// +////////////////////////////////////////////////////////////////////////// + +<strong>VMProtectAlgorithms</strong> g_Algorithm = ALGORITHM_RSA; +<strong>size_t</strong> g_nBits = 0; +<strong>byte</strong> g_vModulus[1]; +<strong>byte</strong> g_vPrivate[1]; +<strong>byte</strong> g_vProductCode[1]; + +////////////////////////////////////////////////////////////////////////// +////////////////////////////////////////////////////////////////////////// + +<strong>int</strong> _tmain(<strong>int</strong> argc, <strong>_TCHAR*</strong> argv[]) +{ + <strong>VMProtectProductInfo</strong> pi; + pi.algorithm = g_Algorithm; + pi.nBits = g_nBits; + pi.nModulusSize = sizeof(g_vModulus); + pi.pModulus = g_vModulus; + pi.nPrivateSize = sizeof(g_vPrivate); + pi.pPrivate = g_vPrivate; + pi.nProductCodeSize = sizeof(g_vProductCode); + pi.pProductCode = g_vProductCode; + + <strong>VMProtectSerialNumberInfo</strong> si = {0}; + si.flags = HAS_USER_NAME | HAS_EMAIL; + si.pUserName = L"John Doe"; + si.pEMail = L"john@doe.com"; + <strong>char *</strong> pBuf = NULL; + <strong>VMProtectErrors</strong> res = <strong>VMProtectGenerateSerialNumber</strong>(&pi, &si, &pBuf); + <strong>if</strong> (res == ALL_RIGHT) + { + <strong>printf</strong>("Serial number:\n%s\n", pBuf); + <strong>VMProtectFreeSerialNumberMemory</strong>(pBuf); + } + else + { + <strong>printf</strong>("Error: %d\n", res); + } + + <strong>return</strong> 0; +} +</pre> + + <p>This is an example project for Microsoft Visual Studio from <strong>Keygen\DLL\Example</strong>. Below are the most interesting parts of the code with our comments.</p> + + <p>First lines of the <strong>main</strong> function fill the <strong>VMProtectProductInfo</strong> structure with data, exported from VMProtect. This code is typical and it shouldn't be changed to avoid errors. Then we create the + <strong>VMProtectSerialNumberInfo</strong> structure and insert a bit combination of user name and e-mail to the flag field. + In the next line, we put the user name and the password to the appropriate fields in the structure. Note, values are accepted in the UNICODE encoding. The key generator will transform them to UTF-8.</p> + + <p>Then, we initialize a pointer variable where the address of the generated key will be stored, and call + <strong>VMProtectGenerateSerialNumber</strong>, then analyze the return code. If there are no errors, the generated key goes out to console, and a call to free serial number memory function is made.</p><strong>The rest fields of the + VMprotectSerialNumberInfo structure</strong> + + <p>Some fields of the structure may needs some additional explanations. For example, <strong>dwExpDate</strong> and + <strong>dwMaxBuildDate</strong> fields contain dates in the specific format: <strong>0xYYYYMMDD</strong>, that is, the year is stored in the high wordб while the month and the day are in the respectively high and low bytes of the low word. + To produce such a number, the following macros is used: <strong>MAKEDATE(y, + m, d)</strong>. You can call it like this: <strong>MAKEDATE(2010, + 05, 12)</strong>.</p> + + <p>The <strong>pHardwareID</strong> field should contain a pointer to a string the + <strong>VMProtectGetCurrentHWID</strong> method from the licensing SDK has returned.</p><br /> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/manager/keygen/keygen_net.htm b/help/en/manager/keygen/keygen_net.htm new file mode 100644 index 0000000..e67b4a2 --- /dev/null +++ b/help/en/manager/keygen/keygen_net.htm @@ -0,0 +1,78 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href= + "../../default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>.Net-version</title> + <style type="text/css"> +/*<![CDATA[*/ + p.c1 {color:red;} + /*]]>*/ + </style> +</head> + +<body> + <h1>.Net-version</h1> + + <h3>Description</h3> + + <p>The .Net-version of the key generator is a build containing all that is required to generate serial numbers. Source codes are in <strong>Keygen\Net</strong> as two projects: KeyGen (the key generator itself) and Usage (an example of use of the key generator).</p> + + <p class="c1">The key generator is supplied in source codes for quick building under a given version of the .Net + Framework, however we strongly do not recommend to apply any changes to the code. In future versions of VMProtect some new possibilities may be added to the generator, and that may lead to repeated modification of the code. Also, this may lead to errors that are very difficult to locate. + If you found errors in the original code of the generator or would like to suggest improvements, please contact the support team.</p> + + <h3>Using the generator</h3> + + <p>Take the code from the <strong>Usage</strong> project as a base, + then add to your project a link to the VMProtect.KeyGen.dll build. After that you will be able to generate serial numbers in your application. To function properly, the generator must "know" which product you generate serial numbers for. + To achieve this, in VMProtect open the "Project | Export key pair" dialog and select the "Parameters for KeyGen.Net" option. The text area below will contain text information you should copy and paste to your application as a string constant.</p> + + <p>Here is an example code to call the generator:</p> + <pre> +try +{ + string data = @""; // put the exported data here + Generator g = new Generator(data); + g.UserName = "John Doe"; + g.EMail = "john@doe.com"; + g.ExpirationDate = DateTime.Now.AddMonths(1); + g.MaxBuildDate = DateTime.Now.AddYears(1); + g.RunningTimeLimit = 15; + g.HardwareID = "AQIDBAgHBgU="; + g.UserData = new byte[] { 10, 9, 8, 7, 6, 5, 4, 3, 2, 1, 0 }; + string serial = g.Generate(); + Console.WriteLine("Serial number:\n{0}\n", serial); +} +catch (Exception ex) +{ + Console.WriteLine("Error: {0}", ex); +} + +</pre> + + <p>The string you copied from VMProtect should be placed to the <strong>data</strong> variable passed as a parameter to the serial number class constructor. In case of any problems occur while parsing the product data, the constructor throws an exception containing a description of the problem. If the constructor successfully finishes its work, the generator is ready to produce serial numbers.</p> + + <p>A serial number can contain various information specified using the generator properties. The above example displays how to fill all and every field of a serial number. Certain fields have limitations. For example, the <strong>User Name</strong> and + <strong>E-Mail</strong> cannot accept strings exceeding 255 symbols in the UTF-8 encoding. If incorrect data are supplied, properties throw exceptions containing a description of the problem.</p> + + <p>When the generator setup is done, the + <strong>Generate()</strong> method is invoked. This method generates a serial number. At this step, all data of the serial number are combined, the checksum is calculated and the data are encrypted. If the volume of data exceeds the allowed length, the method throws an exception.</p> + + <p>If you need to generate multiple serial numbers, you can use the generator class several times in a row, without the need to create it from scratch. To clear any given property of the generator, simply assign a <strong>null</strong> value to it.</p><br /> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/manager/keygen/keygen_php.htm b/help/en/manager/keygen/keygen_php.htm new file mode 100644 index 0000000..9da8d36 --- /dev/null +++ b/help/en/manager/keygen/keygen_php.htm @@ -0,0 +1,94 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href= + "../../default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>UNIX-version</title> +</head> + +<body> + <h1>UNIX-version</h1> + + <h3>Description</h3> + + <p>The UNIX-version of the key generator is a PHP file that contains all necessary information for serial number generation. The file is located in <strong>Keygen\PHP</strong>. Below we describe the key points of using such a generator.</p> + + <h3>Configuring the generator</h3> + + <p>In the beginning of the PHP file, the setup code is located:</p> + <pre class="code">////////////////////////////////////////////////////////////////////////////////////////////// +// The following lines should be generated by VMProtect License Manager +$exported_algorithm = "RSA"; +$exported_bits = 2048; +$exported_private = "PJvj4kEpoQMIpYK+9wEt......xKeiSZgzdiln8Q=="; +$exported_modulus = "rOlny/3QgZb/VmGr3CmY......I6ESAUmtQ+RBqQ=="; +$exported_product_code = "oLQdGUn8kVk="; +////////////////////////////////////////////////////////////////////////////////////////////// +</pre> + + <p>This code is automatically generated by VMProtect (see <a href= + "../licenses.htm#export">Exporting product parameters</a>) and is unique for each particular product. It is crucial to copy it accurately, as otherwise the generator will work incorrectly.</p> + + <h3>Contents of a key</h3> + + <p>Then, the generator specifies the contents of a serial number + The contents are specified in an array, with all possible parameters of the key listed below. However, in real applications, some of them may be omitted:</p> + <pre class="code">$params = <strong>array</strong>( + user_name => "John Doe", // UTF-8! + email => "john@doe.com", + hwid => "vHGMdMRvGCPjWcCQ", // Exactly as returned by VMProtectGetCurrentHWID + expire_date => <strong>array</strong>(year => 2009, month => 10, day => 1), + maxbuild_date => <strong>array</strong>(year => 2009, month => 10, day => 1), + time_limit => 10, + user_data => <strong>base64_decode</strong>("CGCvRvMWcPHGdMjQ"), // string of bytes + ); +</pre> + + <h3>Successful key generation handler function</h3> + + <p>Below you can see a simplest function called upon successful generation of a serial number. The only parameter sent to it is a serial number string. The function must pass the serial number to the caller (an e-commerce agent), usually with the <strong>echo</strong> command. The string is preliminarily split to sub-strings 75 symbols each, for convenience. Also, this function could send the generated serial number by e-mail to the developer or add it to a database.</p> + <pre class="code">function <strong>OnSerialGenerated</strong>($serial) +{ + $serial = <strong>wordwrap</strong>($serial, 75, "\n", true); + <strong>echo</strong> $serial; +} +</pre> + + <h3>Key generator error handler function</h3> + + <p>The final part of the code that needs our attention is a function called when something goes wrong. This function receives a string with the error message, and when it finishes, the <strong>die()</strong> function is called. The handler function must do two things: instead of a key, return to an e-commerce agent a message saying the key will be sent manually. And send to the developer an exhaustive information about the error to fix it and generate the key manually.</p> + <pre class="code">function <strong>OnSerialGenerationFailed</strong>($details) +{ + <strong>echo</strong> "You will receive serial number in the next 24 hours"; // message to the customer +// mail("support@vendor.com", "Houston, we have a problem", $details); // message to vendor +} +</pre> + + <p>There are several possible causes of mistakes: incorrect parameters of the algorithms, incorrect parameters of the key, a too long user name or e-mail, or a too long serial number that doesn't fit to the number of bits specified in the algorithm. + That is why the <strong>OnSerialGenerationFailed</strong> function must send a detailed information about the issue to the developer, so he could generate a serial number and send it to the customer.</p> + + <h3>Other things to consider</h3> + + <p>Examples hold a simplified version of the key generator. It doesn't take into account <a href="index.htm">recommendations to develop web generators</a>. It does not check the IP address of the caller and does not analyze input parameters. Please pay attention to this when developing your own generator based on this one.</p> + + <p>A user name and an e-mail must be passed as UTF-8 strings. Make sure your e-commerce agent sends these data in the UTF-8 encoding, or transcode the information if this is not so. Wrong encoding won't lead to an incorrect serial number generated, but the registration name displayed for such a serial number can be different from the real user's name, so he or she may be surprised to see it in the "About" window of the application</p> + + <p>Asymmetric encryption is a complex mathematical process. If it is implemented using pure PHP without any third-party libraries, serial number generation can take dozens of seconds. The generator uses + <strong>gmp_powm</strong>, <strong>bi_powmod</strong>, + <strong>bcpowod</strong> functions whenever they are available. If serial number generation take too long on your hosting, we recommend to ask the hosting provider to enable these functions. For example, the <strong>gmp_powm</strong> function works ten of times faster than <strong>bcpowmod</strong>.</p><br /> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/manager/keygen/serial_format.htm b/help/en/manager/keygen/serial_format.htm new file mode 100644 index 0000000..9b502ea --- /dev/null +++ b/help/en/manager/keygen/serial_format.htm @@ -0,0 +1,206 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href= + "../../default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Serial number format</title> + <style type="text/css"> +/*<![CDATA[*/ + th {text-align:left;} + table {border-collapse:collapse; margin-top: 4px;} + td,th {border: 1px solid #B0B0B0; padding-left:10;padding-right:10;} + /*]]>*/ + </style> +</head> + +<body> + <h1>Serial number format</h1> + + <h3>Serial number structure</h3> + + <p>The serial number consists of blocks. Each block starts from an identifier byte that indicates contents of the block and possibly its length. The last block always has the 255 identifier that contains a checksum of the serial number except the last block.</p> + + <p>Depending on the type of the block, it can have constant or variable length. In the latter case, the length is specified in the byte following the block identifier. The exact format of each block is described below.</p> + + <h3>Block format</h3> + + <table border="1" cellspacing="0" cellpadding="2"> + <tr> + <th>ID</th> + + <th>Name</th> + + <th>Size (byte)</th> + + <th>Description</th> + + <th>Example</th> + </tr> + + <tr> + <td>0x01</td> + + <td>Version</td> + + <td>1</td> + + <td>The block contains a version of the serial number, 1-byte sized. + The version must be 1.</td> + + <td>01 01</td> + </tr> + + <tr> + <td>0x02</td> + + <td>User name</td> + + <td>1 + N</td> + + <td>The block contains a UTF-8 encoded user name. Before the user name, there is 1 byte holding the length of the name. Therefore, the total length of a user name must not exceed 255 bytes. No trailing 0 is required.</td> + + <td>02 04 4A 5F 48 4E</td> + </tr> + + <tr> + <td>0x03</td> + + <td>E-Mail</td> + + <td>1 + N</td> + + <td>The block contains a UTF-8 encoded e-mail of the user. + Before the e-mail there is 1 byte holding the length. Therefore, the total length of an e-mail must not exceed 255 bytes. No trailing 0 is required.</td> + + <td>03 07 61 40 62 2E 63 6F 6D</td> + </tr> + + <tr> + <td>0x04</td> + + <td>Hardware identifier</td> + + <td>1 + N</td> + + <td>The block contains hardware identifier as returned by the <strong>VMProtectGetCurrentHWID()</strong> function. The function returns a base-64 string. A decoded version of the string is put to the serial number. The length of the data block must be a multiple of 4. There is a length byte before the data block. The maximum block length is 32 bytes.</td> + + <td>04 08 E1 E2 E3 E4 A1 A2 A3 A4</td> + </tr> + + <tr> + <td>0x05</td> + + <td>License expiration date</td> + + <td>4</td> + + <td>The block contains serial number expiration date + Date format is described below.</td> + + <td>05 01 0A 07 DA</td> + </tr> + + <tr> + <td>0x06</td> + + <td>Maximum operation time</td> + + <td>1</td> + + <td>the block contains 1 byte holding the time in minutes the program can operate. Therefore, the maximum time can be 255 minutes.</td> + + <td>06 05</td> + </tr> + + <tr> + <td>0x07</td> + + <td>Product code</td> + + <td>8</td> + + <td>The block contains a product code - 8 bytes created by VMProtect and exported with product parameters. + These data are exported in the base-64 encoding and must be decoded to a byte array before putting to a serial number. + The size of the array must be exactly 8 bytes. + <strong>This block is obligatory! Without it, the protected program will not work correctly.</strong></td> + + <td>07 01 02 03 04 05 06 07 08</td> + </tr> + + <tr> + <td>0x08</td> + + <td>User data</td> + + <td>1 + N</td> + + <td>The block contains up to 255 bytes of custom user data. + The license system doesn't analyze these data and will return them when the + <strong>VMProtectGetSerialNumberData()</strong> function is called. Before the data block, there is a byte holding the size of the user data.</td> + + <td>08 05 01 02 03 04 05</td> + </tr> + + <tr> + <td>0x09</td> + + <td>Maximum build date</td> + + <td>4</td> + + <td>The block contains the maximum build date of the application. The format is described below.</td> + + <td>09 01 0A 07 DA</td> + </tr> + + <tr> + <td>0xFF</td> + + <td>Checksum</td> + + <td>4</td> + + <td>The block contains the serial number checksum. The block is located before the last one, and the checksum is calculated for all previous blocks. The checksum calculation mechanism is described below.</td> + + <td>FF 01 02 03 04</td> + </tr> + </table> + + <h3>Date storage format</h3> + + <p>Dates are stored in a serial number as a double word - + 0xYYYYMMDD. The high order word contains the year, and the lower order word holds the day and the month. + Bytes follow the Little Endian representation - from lower to higher. If there is a pointer to the first byte of the record, the date can be read or written with the following code:</p> + <pre class="code"><strong>byte *</strong>pDate = 0xNNNNNN; // date address +<strong>*</strong>(<strong>DWORD *</strong>)pDate = (2010 << 16) | (10 << 8) | 1; // October 1, 2010 +<strong>DWORD</strong> dwExp = *(<strong>DWORD *</strong>)pDate; +</pre> + + <h3>Checksum calculation</h3> + + <p>The checksum of the serial number is calculated using the SHA-1 hashing algorithm. The result is five 32-bit words. The first word is used as a checksum for the serial number. <strong>Please note:</strong> the word is Little Endian (from lower to higher). The string representation of SHA-1 hash the Big Endian is used - numbers go from the higher byte to the lower one, so if the SHA-1 hash is generated by a string function (like in PHP), the first four bytes of the hash must be reversed.</p> + + <h3>Additional information</h3> + + <p>Block with numbers other than those specified above are ignored by the licensing system. New blocks may be added in newer versions. <strong>We do not recommend creating your own blocks using non-occupied identifiers!</strong> Firstly, this could render the key non-functional with newer version of the licensing system. Secondly, the protected program cannot read the values of theses blocks anyway. To store additional information in a key, use the <strong>User + Data</strong> field instead. It was meant exactly for this purpose.</p> + + <p>A serial number doesn't have SALT, a random information intended to provide variability of keys based on the same input data. This task is imposed to the encryption algorithm. If you need differences on the serial number level, for example, when selling a series of keys to an organization, you can add individual indices to the user name field ("Company" LLC, + key 1 of 10) or insert this information to the <strong>User + Data</strong> field in any appropriate format.</p><br /> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/manager/licenses.htm b/help/en/manager/licenses.htm new file mode 100644 index 0000000..1eca870 --- /dev/null +++ b/help/en/manager/licenses.htm @@ -0,0 +1,72 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="../default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Managing licenses</title> +</head> + +<body> + <h1>Managing licenses</h1> + + <h3>Initialization</h3> + + <p>By default, licensing functions are off. To enable them, you should create a pair of keys in the "Licenses" subsection of the "Project" section. If the project links to the license manager database (in older versions of VMProtect the license manager was a standalone program), VMProtect will suggest you to import the corresponding licenses to the project. When initialization finishes, the Lock to Serial Number option will be available, and you will be able to create and process serial numbers.</p> + + <h3>Interface</h3> + + <p>The "Interface" section displays a full list of licenses in the left panel and parameters of the selected element in the main panel.</p> + + <p><img src="../images/licenses1.png" /></p> + + <p>The right panel displays detailed information about the selected license. It also allows blocking a serial number, copying it to the clipboard or seeing hardware id information (by clicking it).</p> + + <h3 id="AddLicense">Creating a license</h3> + + <p>To add a new license, click the corresponding button on the toolbar. + AThe Add License dialog appears:</p> + + <p><img src="../images/project_add_license.png" /></p> + + <p>The upper part of the dialog allows to specify main parameters of the new license. The lower section configures which parameters will be finally put into a serial number and allows adding additional data: for example, a hardware identifier or custom user data. + When you finish filling the data, click OK, and VMProtect creates a new license.</p> + + <h3>Removing and blocking licenses</h3> + + <p>To delete a license, right-click it in the list of licenses and choose "Delete" in the context menu. Or simply select the license and press Del. To block a license, turn the "Blocked" parameter in the main panel to "Yes".</p><p>There is a difference between deleting a license and clocking it. Removed serial numbers are not blocked by the licensing system. They simply do not exist any more in the database. If a license was created by mistake and the serial number never was sent to anyone, you can delete such a license. However, if the serial number was compromised, you should not just delete the license, you should block it instead. In this case the information about this serial number is passed to the licensing system, and it will not further accept this serial number.</p> + + <h3>Importing serial numbers</h3> + + <p>Serial numbers can be created not only in VMProtect, but also in third-party programs - key generators. Key generators allow you to automatically provide e-commerce agents with serial numbers whenever a license is purchased. To add such serial numbers to the database, you can import them. To import serial numbers, press + Ctrl+I or select the "Import" command in the "Project" menu.</p> + + <p><img src="../images/menu_project_import.png" /></p> + + <p>The first step to import a serial number is the import dialog:</p> + + <p><img src="../images/import_key.png" /></p> + + <p>If the entered license already presents in the database, the edit license window will be opened. Otherwise, the new license dialog appears where you can adjust the license information and confirm license creation by clicking the OK button. The license is added to the database.</p><a name="export" id="export"></a> + + <h3>Exporting license parameters</h3> + + <p>External key generators require secret key of the product to work properly. You can obtain this information in the most suitable form by using the "Export key pair" command from the "Project" menu. The following export dialog appears:</p> + + <p><img src="../images/export_keys.png" /></p> + + <p>The "Export format" field allows you to select one of the supported formats, while the "Results of export" field contains the key data in the most appropriate format for the selected type of a key generator. To copy the contents to the clipboard, click the "Copy" button.</p><br /> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/manager/usage/api.htm b/help/en/manager/usage/api.htm new file mode 100644 index 0000000..b227735 --- /dev/null +++ b/help/en/manager/usage/api.htm @@ -0,0 +1,259 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href= + "../../default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Licensing API functions</title> + <style type="text/css"> +/*<![CDATA[*/ + th {text-align:left;} + table {border-collapse:collapse; margin-top: 4px;} + td,th {border: 1px solid #B0B0B0; padding-left:10;padding-right:10;} + /*]]>*/ + </style> +</head> + +<body> + <h1>Licensing API functions</h1> + + <p>The licensing system API is an integral part of VMProtect API and its SDK. API allows you to specify a serial number and retrieve all information about it: whether it suits the program or not, is the serial number expired, the name this product is registered to and so on. Also, the API provides a hardware identifier of the computer the program runs on.</p><strong id= + "VMProtectSetSerialNumber">VMProtectSetSerialNumber</strong> + + <p>This function loads a serial number to the licensing system. Call syntax:</p> + <pre class="code">int VMProtectSetSerialNumber(const char *SerialNumber); +</pre> + + <p>The input <strong>SerialNumber</strong> parameter must contain a pointer to a null-terminated string ('\0') containing a base-64 encoded serial number. The function returns a bit mask of serial number status flags, the same as the one <strong>VMProtectGetSerialNumberState()</strong> returns. You can read more about flags below. The serial number is "good" if the function returned 0.</p><br /> + <strong id= + "VMProtectGetSerialNumberState">VMProtectGetSerialNumberState</strong> + + <p>This function returns status flags for the serial number specified by a call to + <strong>VMProtectSetSerialNumber()</strong>.</p> + <pre class="code">int VMProtectGetSerialNumberState(); +</pre> + + <p>If at least one flag is set, there is a problem with the serial number. The program shouldn't work if at least one bit is set. The detailed description of flags and their values is listed in the table below:</p> + + <table border="1" cellspacing="0" cellpadding="2"> + <tr> + <th>Flag</th> + + <th>Value</th> + + <th>Description</th> + </tr> + + <tr> + <td>SERIAL_STATE_FLAG_CORRUPTED</td> + + <td>0x00000001</td> + + <td>The licensing system is corrupted. Possible reasons are: incorrect setup of the protection project, cracking attempt.</td> + </tr> + + <tr> + <td>SERIAL_STATE_FLAG_INVALID</td> + + <td>0x00000002</td> + + <td>The serial number is incorrect. The flag is set if the licensing system cannot decrypt the serial number.</td> + </tr> + + <tr> + <td>SERIAL_STATE_FLAG_BLACKLISTED</td> + + <td>0x00000004</td> + + <td>The serial number matches the product, but is black listed in VMProtect.</td> + </tr> + + <tr> + <td>SERIAL_STATE_FLAG_DATE_EXPIRED</td> + + <td>0x00000008</td> + + <td>The serial number is expired. You can obtain the detailed information about the expiration date by calling + <strong>VMProtectGetSerialNumberData()</strong></td> + </tr> + + <tr> + <td>SERIAL_STATE_FLAG_RUNNING_TIME_OVER</td> + + <td>0x00000010</td> + + <td>Operating time of the program is depleted. You can obtain the detailed information about the operating time of the program by calling + <strong>VMProtectGetSerialNumberData()</strong></td> + </tr> + + <tr> + <td>SERIAL_STATE_FLAG_BAD_HWID</td> + + <td>0x00000020</td> + + <td>Hardware identifier does not match the hardware identifier prescribed in the key.</td> + </tr> + + <tr> + <td>SERIAL_STATE_FLAG_MAX_BUILD_EXPIRED</td> + + <td>0x00000040</td> + + <td>The serial number does not match the current version of the protected program. You can obtain the maximum build date of the program this serial number matches by calling + <strong>VMProtectGetSerialNumberData()</strong>.</td> + </tr> + </table><br /><br /> + <strong id= + "VMProtectGetSerialNumberData">VMProtectGetSerialNumberData</strong> + + <p>This function obtains information about contents of the serial number acquired with a call to + <strong>VMProtectSetSerialNumber()</strong>. Call syntax:</p> + <pre class="code">bool VMProtectGetSerialNumberData(VMProtectSerialNumberData *Data, int Size); +</pre> + + <p>The first parameter is a pointer to the + <strong>VMProtectSerialNumberData</strong> structure, where all necessary information will be written to. The second parameter is the size of the structure passed in the first parameter. It is required to control the structure's format. The function returns FALSE if the licensing system is corrupted (see the SERIAL_STATE_FLAG_CORRUPTED flag), if a zero address of the structure is provided or if the passed size of the structure is incorrect. In all other cases, the function returns TRUE and records all information about the serial number to the provided address. Below are the elements of the structure:</p> + + <table border="1" cellspacing="0" cellpadding="2"> + <tr> + <th>Element</th> + + <th>Type</th> + + <th>Description</th> + </tr> + + <tr> + <td>nState</td> + + <td>int</td> + + <td>A bit flag mask indicating the status of a key. Similar to the one returned by + <strong>VMProtectGetSerialNumberState()</strong>.</td> + </tr> + + <tr> + <td>wUserName</td> + + <td>wchar_t[256]</td> + + <td>The name of a customer in UNICODE, null-terminated.</td> + </tr> + + <tr> + <td>wEMail</td> + + <td>wchar_t[256]</td> + + <td>The e-Mail of a customer in UNICODE, null-terminated.</td> + </tr> + + <tr> + <td>dtExpire</td> + + <td>VMProtectDate</td> + + <td>The key expiration date. The format of the + VMProtectDate structure is described below.</td> + </tr> + + <tr> + <td>dtMaxBuild</td> + + <td>VMProtectDate</td> + + <td>The maximum product build date the given key can work with. The format of the VMProtectDate structure is described below.</td> + </tr> + + <tr> + <td>bRunningTime</td> + + <td>int</td> + + <td>The amount of minutes the program will work (maximum duration of a session). The value in minutes counts from the moment the program starts.</td> + </tr> + + <tr> + <td>nUserDataLength</td> + + <td>unsigned char</td> + + <td>The length of user data in the + <strong>bUserData</strong> field.</td> + </tr> + + <tr> + <td>bUserData</td> + + <td>unsigned char[255]</td> + + <td>User data put into the key. The actual number of bytes is specified in + <strong>nUserDataLength</strong>.</td> + </tr> + </table><br /> + + <p>The <strong>VMProtectDate</strong> structure is a compact representation of date. Its fields are listed in the table below:</p> + + <table border="1" cellspacing="0" cellpadding="2"> + <tr> + <th>Element</th> + + <th>Type</th> + + <th>Description</th> + </tr> + + <tr> + <td>wYear</td> + + <td>unsigned short</td> + + <td>Year.</td> + </tr> + + <tr> + <td>bMonth</td> + + <td>unsigned char</td> + + <td>Month, starts from 1.</td> + </tr> + + <tr> + <td>bDay</td> + + <td>unsigned char</td> + + <td>Day, starts from 1.</td> + </tr> + </table><br /> + <br /> + <strong id= + "VMProtectGetCurrentHWID">VMProtectGetCurrentHWID</strong> + + <p>This function obtains a hardware identifier of the PC the program is working on. Call syntax:</p> + <pre class="code">int VMProtectGetCurrentHWID(char * HWID, int Size); +</pre> + + <p>The first parameter is a pointer to a memory area where the identifier is written to. The second parameter is the size of this area. The function returns the number of bytes written inclusive of the trailing zero byte ('\0'). If NULL is provided in the first parameter, the function returns the number of bytes required to store the hardware identifier. Here is the correct way to use the function:</p> + <pre class="code"><strong>int</strong> nSize = <strong>VMProtectGetCurrentHWID</strong>(NULL, 0); // get the required buffer size +<strong>char *</strong>pBuf = <strong>new char</strong>[nSize]; // allocate memory for the buffer +<strong>VMProtectGetCurrentHWID</strong>(pBuf, nSize); // obtain the identifier +// use the identifier +<strong>delete</strong> [] pBuf; // release memory +</pre><br /> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/manager/usage/index.htm b/help/en/manager/usage/index.htm new file mode 100644 index 0000000..50f55d1 --- /dev/null +++ b/help/en/manager/usage/index.htm @@ -0,0 +1,74 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href= + "../../default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Integrating to application</title> + <style type="text/css"> + </style> +</head> + +<body> + <h1>Integrating to application</h1> + + <p>In the several steps described below we will create a test application that queries the licensing system: provides serial numbers to it, receives the status of a serial number and its contents. On the first stage, we use the license system in the test mode; one the second stage we use it as it would be used in actual practice.</p><strong>Work modes of the licensing system</strong> + + <p>Building protection always goes through two main steps: development and release. As for licensing, at first you create an application, integrate protection into it, then add checks and functional limitations. And only after thorough testing you can make the product available to users and begin the second stage. Testing of a protected application is a complex process, because you need to make sure all checks and conditional jumps operate correctly. Making "real" serial numbers for all possible test cases is inconvenient. That is why the licensing system offers the "developer mode" (AKA "test mode") as well. In this work mode, no protection is applied to the app, and reaction of the system to supplied serial numbers is adjusted in the configuration file. When the application is free from bugs and it correctly works with the licensing system, VMProtect replaces the "test" licensing module with the real one that do perform real serial number checking. This is done when the application is protected, so you can't avoid this step by mistake.</p><strong id="TestMode">Stage 1: + Test mode</strong> + + <p>In the test mode, all reactions of the licensing system (statuses and data it returns) to supplied serial numbers is described in the configuration file. The file is called VMPLicense.ini and should be located in the working folder of the application. In 10 steps provided below we will go from creating the simplest application to full-featured use of the licensing system in the test mode with hardware locking and limiting the period of free upgrades.</p> + + <ul> + <li><a href="step11_app.htm">Step 1.1: Creating a protected application</a></li> + + <li><a href="step12_code.htm">Step 1.2: Adding the license checking code</a></li> + + <li><a href="step13_flags.htm">Step 1.3: Retrieving serial number status flags</a></li> + + <li><a href="step14_name.htm">Step 1.4: Retrieving the name and the e-mail of a user</a></li> + + <li><a href="step15_exp.htm">Step 1.5: Checking the expiration date of the serial number</a></li> + + <li><a href="step16_time.htm">Step 1.6: Limiting the operation time of the program</a></li> + + <li><a href="step17_maxbuild.htm">Step 1.7: Limiting the free upgrades period</a></li> + + <li><a href="step18_blacklist.htm">Step 1.8: Serial numbers in the black list</a></li> + + <li><a href="step19_hwid.htm">Step 1.9: Hardware lock</a></li> + + <li><a href="step1A_userdata.htm">Step 1.10: User data</a></li> + </ul><strong id="RealMode">Stage 2: Real mode</strong> + + <p>In the real mode VMProtect licensing system puts a special licensing module to the protected application. This module carries out the same functions as the test one in the SDK, but works with contents of a serial number instead of the configuration ini-file. The next five steps illustrate the process of protecting a simple application with a full-featured protection based on VMProtect and the licensing system.</p> + + <ul> + <li><a href="step21_src.htm">Step 2.1: Creating a new protected application</a></li> + + <li><a href="step22_vmp.htm">Step 2.2: Creating a VMProtect protection project</a></li> + + <li><a href="step23_product.htm">Step 2.3: First start of the protected product</a></li> + + <li><a href="step24_test.htm">Step 2.4: Testing the results</a></li> + + <li><a href="step25_codelock.htm">Step 2.5: Locking the code to a serial number</a></li> + </ul><strong>Additional information</strong> + + <p>Values of all bit flags, structure formats and function call parameters can be found in the <a href="api.htm">Licensing system API + </a> section of this help file. Use this section as a reference, while Steps provided above help to easily implement a typical ready-to-use protection.</p><br /> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/manager/usage/step11_app.htm b/help/en/manager/usage/step11_app.htm new file mode 100644 index 0000000..59bee08 --- /dev/null +++ b/help/en/manager/usage/step11_app.htm @@ -0,0 +1,53 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href= + "../../default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Step 1.1: Creating a protected application</title> +</head> + +<body> + <h1>Step 1.1: Creating a protected application</h1> + + <p>The first step is to create an application. This would be a simple app without any user interface and with no serious capabilities. Our goal is to pass a serial number to the licensing system and receive its answer..</p> + <pre class="code">#include <windows.h> +#include <stdio.h> + +bool is_registered(const char *serial) +{ + return serial && serial[0] == 'X'; +} + +int main(int argc, char **argv) +{ + char *serial = "Xserialnumber"; // we set the serial number directly in the code, for simplicity + if (!is_registered(serial)) + { + printf("please register!\n"); + return 0; + } + printf("We are registered.\n"); + return 0; +} +</pre> + + <p>The program uses a very simple way to check the serial number. The <strong>is_registered()</strong> function compares the first symbol of the serial number with 'X' and thinks the number is correct if this they match. For an incorrect serial number, a registration message is displayed, while if a user enter the correct key, "We are registered." is shown instead</p> + + <p>The <a href="step12_code.htm">next step</a> is to add the code to check the serial number using the licensing system of + VMProtect.</p><br /> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/manager/usage/step12_code.htm b/help/en/manager/usage/step12_code.htm new file mode 100644 index 0000000..7281851 --- /dev/null +++ b/help/en/manager/usage/step12_code.htm @@ -0,0 +1,79 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href= + "../../default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Step 1.2: Adding the license checking code</title> +</head> + +<body> + <h1>Step 1.2: Adding the license checking code</h1><strong>Include VMProtect SDK</strong> + + <p>If you haven't do this before, it is time to include VMProtect SDK to your project. The SDK is three files: the header file (VMProtectSDK.h), the library file (VMProtectSDK32.lib) and the dll-file with implementation (VMProtectSDK32.dll). There are individual implementations of the library and the dll-file for 64-bit systems.</p> + + <p>Put the dll-file, the header file and the library file to the working folder of our application, where the source files are, and include the header file to the main file:</p> + <pre class="code">#include <windows.h> +#include <stdio.h> +#include "VMProtectSDK.h" +</pre> + + <p>Build the project and make sure it compiles and runs as before. The licensing system is inactive yet.</p><strong>Sending a serial number to the licensing system</strong> + + <p>Now, right below the line with the serial number, we add a call to the SDK function of the licensing system:</p> + <pre class="code">char *serial = "Xserialnumber"; // we set the serial number directly in the code, for simplicity +int res = VMProtectSetSerialNumber(serial); +printf("res = 0x%08X\n", res); +</pre> + + <p>If after you did this the program stops with an error saying the required dll-file is missing, make sure you put the corresponding DLL-file to the working folder of our application. In case of a successful execution, you should see the following message:</p> + <pre class="code">res = 0x00000002 +</pre> + + <p>2 corresponds to the SERIAL_STATE_FLAG_INVALID flag + <a href="api.htm">described in the API</a>. This means the licensing system thinks our key is incorrect, which is pretty true, as we didn't "explain" to the system which keys are correct, and which ones are not.</p><strong>Specifying the "correct" serial number</strong> + + <p>In the test mode, the licensing system analyzes the + VMProtectLicense.ini file and reacts to function calls in accordance with the specified settings. We will thoroughly review the file on later steps, and now we simply create such a file and add the following text there:</p> + <pre class="code">[TestLicense] +AcceptedSerialNumber=Xserialnumber +</pre> + + <p>Now, run our program again. If you still receive the "2" error code, make sure the ini-file is located in the working folder of the app. This time we should receive "0". That's the sign that the licensing system accepted and approved the serial number. Now we can remove the + <strong>is_registered()</strong> function from the code - the licensing system is now in charge for checking serial numbers:</p> + <pre class="code">#include <windows.h> +#include <stdio.h> +#include "VMProtectSDK.h" + +int main(int argc, char **argv) +{ + char *serial = "Xserialnumber"; // we set the serial number directly in the code, for simplicity + + int res = VMProtectSetSerialNumber(serial); + printf("res = 0x%08X\n", res); + + if (res) + { + printf("please register!\n"); + return 0; + } + printf("We are registered.\n"); + return 0; +} +</pre><br /> + <a href="step13_flags.htm">Next step</a> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/manager/usage/step13_flags.htm b/help/en/manager/usage/step13_flags.htm new file mode 100644 index 0000000..d6c6469 --- /dev/null +++ b/help/en/manager/usage/step13_flags.htm @@ -0,0 +1,75 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href= + "../../default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Step 1.3: Retrieving serial number status flags</title> +</head> + +<body> + <h1>Step 1.3: Retrieving serial number status flags</h1><strong>A handy function to print flags</strong> + + <p>First of all, we need a handy function to transform numeric values of flags to comprehensible statuses of a serial number. Here is the code of this function:</p> + <pre class="code">#define PRINT_HELPER(state, flag) if (state & flag) printf("%s ", #flag) +void print_state(INT state) +{ + if (state == 0) + { + printf("state = 0\n"); + return; + } + + printf("state = "); + PRINT_HELPER(state, SERIAL_STATE_FLAG_CORRUPTED); + PRINT_HELPER(state, SERIAL_STATE_FLAG_INVALID); + PRINT_HELPER(state, SERIAL_STATE_FLAG_BLACKLISTED); + PRINT_HELPER(state, SERIAL_STATE_FLAG_DATE_EXPIRED); + PRINT_HELPER(state, SERIAL_STATE_FLAG_RUNNING_TIME_OVER); + PRINT_HELPER(state, SERIAL_STATE_FLAG_BAD_HWID); + PRINT_HELPER(state, SERIAL_STATE_FLAG_MAX_BUILD_EXPIRED); + printf("\n"); +} +</pre> + + <p>Despite the size, function is really simple - checks all bit flags one by one and print all that are present in the status variable. Replace + <strong>printf</strong> in the code after checking the serial number to the call to + <strong>print_state</strong>, and make changes to the serial number we pass to the licensing system:</p> + <pre class="code">char *serial = "Xserialnumber1"; // we set the serial number directly in the code, for simplicity +int res = VMProtectSetSerialNumber(serial); +print_state(res); +</pre> + + <p>Now, if we run this program, the following message will be printed to the console:</p> + <pre class="code">state = SERIAL_STATE_FLAG_INVALID +please register! +</pre> + + <p>Now, we put the old key back by removing "1" and run the program again:</p> + <pre class="code">state = 0 +We are registered. +</pre> + + <p>Now, as we can see status flags of a serial number, let's move to retrieving flags and data from a serial number.</p><strong>Retrieving serial number status</strong> + + <p>You can get the status of a serial number in three ways: by calling + <strong>VMProtectSetSerialNumber()</strong>, by calling + <strong>VMProtectGetSerialNumberState()</strong> or by calling + <strong>VMProtectGetSerialNumberData()</strong> - status flags are put into one of fields of the structure. Each method is intended to use in specific time. The first check of the serial number is performed during installation. At this moment you should decline incorrect numbers, expired numbers, numbers in the black list and so on. Some limitations, for example, the maximum operation time of the program or serial number expiration date should also be checked in run-time. And the <strong>VMProtectGetSerialNumberState()</strong> method is the fastest and the most convenient way here. And if you need to receive complete information about the serial number, you can use the more powerful + <strong>VMProtectGetSerialNumberData()</strong> function.</p><br /> + <a href="step14_name.htm">Next step</a> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/manager/usage/step14_name.htm b/help/en/manager/usage/step14_name.htm new file mode 100644 index 0000000..5868070 --- /dev/null +++ b/help/en/manager/usage/step14_name.htm @@ -0,0 +1,48 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href= + "../../default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Step 1.4: Retrieving the name and the e-mail of a user</title> +</head> + +<body> + <h1>Step 1.4: Retrieving the name and the e-mail of a user</h1> + + <p>Let's start with simple things. We want to get the name and the e-mail of a user from a serial number to show them in the About window (or anywhere else). To do this, we have to add two more lines to our ini-file:</p> + <pre class="code">[TestLicense] +AcceptedSerialNumber=Xserialnumber +UserName=John Doe +EMail=john@doe.com +</pre> + + <p>And in the program, if the registration is successful, we obtain these data and output them to the screen:</p> + <pre class="code">VMProtectSerialNumberData sd = {0}; +VMProtectGetSerialNumberData(&sd, sizeof(sd)); +printf("name = %ls,\ne-mail = %ls\n", sd.wUserName, sd.wEMail); +</pre> + + <p>The structure contains UNICODE data, so <strong>printf()</strong> uses %ls specifiers instead of %s. + The program should print the following text on the screen:</p> + <pre class="code">state = 0 +We are registered. +name = John Doe, +e-mail = john@doe.com +</pre><br /> + <a href="step15_exp.htm">Next step</a> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/manager/usage/step15_exp.htm b/help/en/manager/usage/step15_exp.htm new file mode 100644 index 0000000..5d7628d --- /dev/null +++ b/help/en/manager/usage/step15_exp.htm @@ -0,0 +1,55 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href= + "../../default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Step 1.5: Checking the expiration date of the serial number</title> +</head> + +<body> + <h1>Step 1.5: Checking the expiration date of the serial number</h1> + + <p>Now put a new line to the ini-file in the following format: ExpDate=YYYYMMDD. For example:</p> + <pre class="code">ExpDate=20000101 +</pre> + + <p>The date specified in this line must be already passed, that is, the maximum date is yesterday. When we run the program, we should see the following:</p> + <pre class="code">state = SERIAL_STATE_FLAG_DATE_EXPIRED +please register! +</pre> + + <p>Now let's get some more information before the "please register" message is shown and the program exists:</p> + <pre class="code">if (res) +{ + VMProtectSerialNumberData sd = {0}; + VMProtectGetSerialNumberData(&sd, sizeof(sd)); + printf("exp. date: y = %d, m = %d, d = %d\n", sd.dtExpire.wYear, sd.dtExpire.bMonth, sd.dtExpire.bDay); + printf("please register!\n"); + return 0; +} +</pre> + + <p>The second run of the app now provides more details to us:</p> + <pre class="code">state = SERIAL_STATE_FLAG_DATE_EXPIRED +exp. date: y = 2000, m = 1, d = 1 +please register! +</pre> + + <p>Ok, now remove the ExpDate=... line from the ini-file, so it will not influence everything else we are to do.</p><br /> + <a href="step16_time.htm">Next step</a> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/manager/usage/step16_time.htm b/help/en/manager/usage/step16_time.htm new file mode 100644 index 0000000..58e3a13 --- /dev/null +++ b/help/en/manager/usage/step16_time.htm @@ -0,0 +1,62 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href= + "../../default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Step 1.6: Limiting the operation time of the program</title> +</head> + +<body> + <h1>Step 1.6: Limiting the operation time of the program</h1> + + <p>You can limit the program operates since the moment it is started. This can be useful for demonstration purposes: you provide a real serial number to a user, but the program works no longer than 5 minutes. The licensing system doesn't force such a program to shut down, but merely sets the status flag. So, let's set a maximum working time of one minute, by adding the following line to the ini-file:</p> + <pre class="code">TimeLimit=1 +</pre> + + <p>And modify the program as follows:</p> + <pre class="code">int main(int argc, char **argv) +{ + char *serial = "Xserialnumber"; // we set the serial number directly in the code, for simplicity + + int res = VMProtectSetSerialNumber(serial); + print_state(res); + if (res) return 0; + + VMProtectSerialNumberData sd = {0}; + VMProtectGetSerialNumberData(&sd, sizeof(sd)); + printf("I will run for %d minute(s)\n", sd.bRunningTime); + print_state(VMProtectGetSerialNumberState()); + Sleep(60 * 1000 * sd.bRunningTime); + printf("After %d minute(s):\n", sd.bRunningTime); + print_state(VMProtectGetSerialNumberState()); + + return 0; +} +</pre> + + <p>The program prints the status of the serial number upon start up, then calculates the maximum operating time and waits it to expire. Then the serial number status is printed again. With the maximum operation time set to one minute we should receive the following result:</p> + <pre class="code">state = 0 +I will run for 1 minute(s) +state = 0 +After 1 minute(s): +state = SERIAL_STATE_FLAG_RUNNING_TIME_OVER +</pre> + + <p>The protected program should analyze the status of a serial number periodically and shut down if the flag is set. The licensing system does not do this automatically, because the program may need to free memory, save data to a file and so on. Also, you may want the program to not stop after the operation time has expired, but instead switch to a more restricted mode. The licensing system leaves this up to the developer.</p><br /> + <a href="step17_maxbuild.htm">Next step</a> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/manager/usage/step17_maxbuild.htm b/help/en/manager/usage/step17_maxbuild.htm new file mode 100644 index 0000000..3eab065 --- /dev/null +++ b/help/en/manager/usage/step17_maxbuild.htm @@ -0,0 +1,69 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href= + "../../default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Step 1.7: Limiting the free upgrades period</title> +</head> + +<body> + <h1>Step 1.7: Limiting the free upgrades period</h1><strong>How it works</strong> + + <p>When VMProtect protects an application it records the date. The licensing system treats this date as a build date of the application. And you can put into a serial number the maximum build date this serial number can work with. Therefore, if you put the current date plus one year to the serial number, it will work with all versions of your programs you will be releasing in a year. A version you release one year and a day after will not work with this serial number, and a user will have a choice: use older version of your program or purchase a new key to work with the latest version of the program for one more year.</p><strong>Let's try it</strong> + + <p>Put the line formatted as MaxBuildDate=YYYYMMDD into the ini-file:</p> + <pre class="code">MaxBuildDate=20000101 +</pre> + + <p>In the test mode, the licensing system treats today as the build date, so it is important that the date specified in this line already passed. That is, the maximum date is yesterday. Modify the code of the <strong>main()</strong> function so that it looked like this:</p> + <pre class="code">int main(int argc, char **argv) +{ + char *serial = "Xserialnumber"; // we set the serial number directly in the code, for simplicity + + int res = VMProtectSetSerialNumber(serial); + print_state(res); + + if (res) + { + VMProtectSerialNumberData sd = {0}; + VMProtectGetSerialNumberData(&sd, sizeof(sd)); + printf("max. build date: y = %d, m = %d, d = %d\n", sd.dtMaxBuild.wYear, sd.dtMaxBuild.bMonth, sd.dtMaxBuild.bDay); + printf("please register!\n"); + return 0; + } + + printf("I'm registered\n"); + + return 0; +} +</pre> + + <p>Then, upon program run you should see the following:</p> + <pre class="code">state = SERIAL_STATE_FLAG_MAX_BUILD_EXPIRED +max. build date: y = 2000, m = 1, d = 1 +please register! +</pre> + + <p>By replacing the date in the ini-file to today or tomorrow, we end up with the "working" program:</p> + <pre class="code">state = 0 +I'm registered +</pre> + + <p>Remove the MaxBuildDate=... line from the ini-file so that it would not influence our further steps.</p><br /> + <a href="step18_blacklist.htm">Next step</a> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/manager/usage/step18_blacklist.htm b/help/en/manager/usage/step18_blacklist.htm new file mode 100644 index 0000000..c0ae408 --- /dev/null +++ b/help/en/manager/usage/step18_blacklist.htm @@ -0,0 +1,55 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href= + "../../default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Step 1.8: Serial numbers in the black list</title> +</head> + +<body> + <h1>Step 1.8: Serial numbers in the black list</h1> + + <p>A serial number marked in VMProtect as "blocked" should not be accepted by the licensing system. When you will rebuild your application next time, VMProtect will add the hash of blacklisted serial numbers to the protected application. As a result, the licensing system of the application will decline these serial numbers in the future.</p> + + <p>Firstly, lets minimize the contents of the <strong>main()</strong> function:</p> + <pre class="code">int main(int argc, char **argv) +{ + char *serial = "Xserialnumber"; // we set the serial number directly in the code, for simplicity + + int res = VMProtectSetSerialNumber(serial); + print_state(res); + + return 0; +} +</pre> + + <p>Now, run the program and make sure the licensing system do accept our serial number:</p> + <pre class="code">state = 0 +</pre> + + <p>Now, add this serial number to the black list of the licensing system. Add the following line to the ini-file:</p> + <pre class="code">BlackListedSerialNumber=Xserialnumber +</pre> + + <p>And run the program again:</p> + <pre class="code">state = SERIAL_STATE_FLAG_BLACKLISTED +</pre> + + <p>Should we inform a user that the serial number he or she enters is blacklisted? It is up to you. You can simply tell the serial number is incorrect or inform the user that the key is compromised. The licensing system simply informs the program about the fact of using the blacklisted serial number.</p><br /> + <a href="step19_hwid.htm">Next step</a> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/manager/usage/step19_hwid.htm b/help/en/manager/usage/step19_hwid.htm new file mode 100644 index 0000000..5fcb599 --- /dev/null +++ b/help/en/manager/usage/step19_hwid.htm @@ -0,0 +1,98 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href= + "../../default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Step 1.9: Hardware lock</title> + <style type="text/css"> +/*<![CDATA[*/ + div.c2 {text-align: center} + p.c1 {color:red;} + /*]]>*/ + </style> +</head> + +<body> + <h1>Step 1.9: Hardware lock</h1><strong>Receiving a hardware identifier</strong> + + <p>Before we lock to hardware, we must receive a hardware identifier. The identifier is put into a serial number, and when the number is passed to the licensing system, it checks if identifiers match. So, first we need to receive the identifier of our hardware. Let's reduce the + <strong>main()</strong> function to the bare minimum:</p> + <pre class="code">int main(int argc, char **argv) +{ + int nSize = VMProtectGetCurrentHWID(NULL, 0); + char *buf = new char[nSize]; + VMProtectGetCurrentHWID(buf, nSize); + printf("HWID: %s\n", buf); + delete [] buf; + return 0; +} +</pre> + + <p>By running the program, we receive a default test hardware identifier:</p> + <pre class="code">HWID: myhwid +</pre> + + <p>To change the identifier, add the following line to the ini-file:</p> + <pre class="code">MyHWID=test +</pre> + + <p>If we run the program afterwards, we can see the system thinks "test" is a hardware identifier of our PC:</p> + <pre class="code">HWID: test +</pre> + + <p class="c1"><strong>Important!</strong> The program will display the real hardware identifier only after it is processed with VMProtect.</p><br /> + <strong>Hardware-locked serial number</strong> + + <p>To lock our test serial number to hardware, we should add one more line to the ini-file. This time we define the identifier that is "put into" the serial number:</p> + <pre class="code">KeyHWID=test +</pre> + + <p>Then we complicate <strong>main()</strong> back a bit. Now it will pass a serial number and analyze the result it gets:</p> + <pre> +int main(int argc, char **argv) +{ + int nSize = VMProtectGetCurrentHWID(NULL, 0); + char *buf = new char[nSize]; + VMProtectGetCurrentHWID(buf, nSize); + printf("HWID: %s\n", buf); + delete [] buf; + + char *serial = "Xserialnumber"; + int res = VMProtectSetSerialNumber(serial); + print_state(res); + return 0; +} +</pre> + + <p>After running the code we will see the following result:</p> + <pre class="code">HWID: test +state = 0 +</pre> + + <p>The licensing system has compared the current hardware identifier with the one written in the serial number. Identifiers are equal, so the + <strong>VMProtectSetSerialNumber()</strong> function returned 0 - the serial number matches.</p> + + <p>Now let's try to "run" our program on another hardware. We simply change the value of the MyHWID parameter in the ini-file from "test" to "new test". Run the program again:</p> + <pre class="code">HWID: new test +state = SERIAL_STATE_FLAG_BAD_HWID +</pre> + + <p>This time the licensing system returned the + SERIAL_STATE_FLAG_BAD_HWID flag, which means the real hardware identifier and the one stored in the serial number are not matching. The current identifier we see on the screen is "new test", while the serial number holds "test". If we change the KeyHWID parameter in the ini-file to "new test" we can make our serial number work on this "hardware" too.</p><br /> + <a href="step1A_userdata.htm">Next step</a> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/manager/usage/step1A_userdata.htm b/help/en/manager/usage/step1A_userdata.htm new file mode 100644 index 0000000..16209ad --- /dev/null +++ b/help/en/manager/usage/step1A_userdata.htm @@ -0,0 +1,65 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href= + "../../default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Step 1.10: User data</title> +</head> + +<body> + <h1>Step 1.10: User data</h1> + + <p>A serial number can hold up to 255 bytes of arbitrary data that the licensing system passes to the program as they are. The data can hold any additional information about the sale, data required for operation of the full version or something else. Let's modify our + <strong>main()</strong> function so that it would read data from a serial number and display them on the screen:</p> + <pre class="code">int main(int argc, char **argv) +{ + char *serial = "Xserialnumber"; + int res = VMProtectSetSerialNumber(serial); + print_state(res); + if (res) return 0; + + VMProtectSerialNumberData sd = {0}; + VMProtectGetSerialNumberData(&sd, sizeof(sd)); + printf("Serial number has %d byte(s) of data\n", sd.nUserDataLength); + for (int i = 0; i < sd.nUserDataLength; i++) + printf("%02X ", sd.bUserData[i]); + printf("\n"); + return 0; +} +</pre> + + <p>We also reduce the Ini-file to this:</p> + <pre class="code">[TestLicense] +AcceptedSerialNumber=Xserialnumber +</pre> + + <p>Now, we run the program and make sure our serial number works well, but doesn't contain any data:</p> + <pre class="code">state = 0 +Serial number has 0 byte(s) of data +</pre> + + <p>To add new user data into the serial number, we need to create the UserData variable in the ini-file and assign data to it in the HEX format. Symbols must go in pairs, that is the length of a line must be a multiple of 2. Like this:</p> + <pre class="code">UserData=010203A0B0C0D0E0 +</pre> + + <p>In this case, if we runthe program we will receive the following result:</p> + <pre class="code">state = 0 +Serial number has 8 byte(s) of data +01 02 03 A0 B0 C0 D0 E0 +</pre><br /> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/manager/usage/step21_src.htm b/help/en/manager/usage/step21_src.htm new file mode 100644 index 0000000..b1cfa0b --- /dev/null +++ b/help/en/manager/usage/step21_src.htm @@ -0,0 +1,98 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href= + "../../default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Step 2.1: Creating a new protected application</title> +</head> + +<body> + <h1>Step 2.1: Creating a new protected application</h1> + + <p>At the first stage we made several simple apps to test the API of the licensing system. Now, on the second stage we'll create just one application. It will also be a console app with the <strong>foo()</strong> function working only in the registered version. Here is the code of our test application:</p> + <pre class="code">#include <windows.h> +#include <stdio.h> +#include "VMProtectSDK.h" + +#define PRINT_HELPER(state, flag) if (state & flag) printf("%s ", #flag) +void print_state(INT state) +{ + if (state == 0) + { + printf("state = 0\n"); + return; + } + + printf("state = "); + PRINT_HELPER(state, SERIAL_STATE_FLAG_CORRUPTED); + PRINT_HELPER(state, SERIAL_STATE_FLAG_INVALID); + PRINT_HELPER(state, SERIAL_STATE_FLAG_BLACKLISTED); + PRINT_HELPER(state, SERIAL_STATE_FLAG_DATE_EXPIRED); + PRINT_HELPER(state, SERIAL_STATE_FLAG_RUNNING_TIME_OVER); + PRINT_HELPER(state, SERIAL_STATE_FLAG_BAD_HWID); + PRINT_HELPER(state, SERIAL_STATE_FLAG_MAX_BUILD_EXPIRED); + printf("\n"); +} + +char *read_serial(const char *fname) +{ + FILE *f; + if (0 != fopen_s(&f, fname, "rb")) return NULL; + fseek(f, 0, SEEK_END); + int s = ftell(f); + fseek(f, 0, SEEK_SET); + char *buf = new char[s + 1]; + fread(buf, s, 1, f); + buf[s] = 0; + fclose(f); + return buf; +} + +// The foo() method is very short, but we need it to be an individual function +// so we asked the compiler to not compile it inline +__declspec(noinline) void foo() +{ + printf("I'm foo!\n"); +} + +int main(int argc, char **argv) +{ + char *serial = read_serial("serial.txt"); + int res = VMProtectSetSerialNumber(serial); + delete [] serial; + if (res) + { + printf("serial number is bad\n"); + print_state(res); + return 0; + } + printf("serial number is correct, calling foo()\n"); + foo(); + printf("done\n"); + return 0; +} +</pre> + + <p>Compile the program without the debug information, but in the linker settings we enable creating of the MAP-file - we will need it to work with VMProtect. After we run the program, we should see the following text:</p> + <pre class="code">serial number is bad +state = SERIAL_STATE_FLAG_INVALID +</pre> + + <p>Currently, the licensing system still works in the test mode, because the file wasn't processed by VMProtect and doesn't contain a licensing module in it. On the <a href= + "step22_vmp.htm">next step</a> we will create a VMProtect project and will try to protect our application.</p><br /> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/manager/usage/step22_vmp.htm b/help/en/manager/usage/step22_vmp.htm new file mode 100644 index 0000000..3457643 --- /dev/null +++ b/help/en/manager/usage/step22_vmp.htm @@ -0,0 +1,37 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href= + "../../default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Step 2.2: Creating a VMProtect protection project</title> + <style type="text/css"> + </style> +</head> + +<body> + <h1>Step 2.2: Creating a VMProtect protection project</h1> + + <p>Now, as our test app is ready, compiled and has an assigned MAP-file in the same folder, we can run VMProtect + Ultimate and open the executable file. We need to add two functions to the project: _main (this is how Visual Studio renamed our main()) and foo(). Both functions can be seen in the list of functions in the "Functions" section in VMProtect.</p> + + <!-- <p class="c1"><br /><img src="../../images/real_project_functions.png" alt="Дерево проекта" /></p> --> + + <p>Then, we need to initialize the licensing system. + Open the "Licenses" section and create a pair of keys with the length of 2048 bit.</p><br /> + <a href="step23_product.htm">Next step</a> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/manager/usage/step23_product.htm b/help/en/manager/usage/step23_product.htm new file mode 100644 index 0000000..d7faa7a --- /dev/null +++ b/help/en/manager/usage/step23_product.htm @@ -0,0 +1,54 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href= + "../../default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Step 2.3: First start of the protected product</title> + <style type="text/css"> + </style> +</head> + +<body> + <h1>Step 2.3: First start of the protected product</h1> + + <p>The licensing system is initialized, so let's try to compile the VMProtect project and run the protected file. After running it from the command line we will receive the following message:</p> + <pre class="code">C:\test>dummy_app.vmp.exe +serial number is bad +state = SERIAL_STATE_FLAG_INVALID +</pre> + + <p>If you run depends.exe and can see that our protected executable file doesn't use the VMProtectSDK.dll any more. This means the licensing module is already built into the program. You can also review the list of used DLL from VMProtect, in the "Details | Imports" section.</p> + + <p><img src="../../images/depends.png" /></p> + + <p>Our protected program reads a serial number from the serial.txt file. Since there is no such file yet, the licensing module receives an empty serial number that is interpreted as incorrect. + Now we switch to the "Licenses" section and generate a serial number. + This procedure is described <a href= + "../licenses.htm">here</a> in all details, and now we merely create a simple serial number without any limitations.</p> + + <p><img src="../../images/project_add_license.png" /></p> + + <p>Then, we copy the serial number (select the "Serial number" field in the license properties and precc Ctrl+C), create a file named serial.txt in the same folder as the protected application, and paste the copied number there. Now, if we run our application we will see this:</p> + <pre class="code">C:\test>dummy_app.vmp.exe +serial number is correct, calling foo() +I'm foo +done +</pre> + + <p>The licensing system checked the serial number and found it correct. On the <a href="step24_test.htm">next step</a> we will try to apply some limitations will watch the results.</p><br /> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/manager/usage/step24_test.htm b/help/en/manager/usage/step24_test.htm new file mode 100644 index 0000000..90cf607 --- /dev/null +++ b/help/en/manager/usage/step24_test.htm @@ -0,0 +1,65 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href= + "../../default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Step 2.4: Testing the results</title> +</head> + +<body> + <h1>Step 2.4: Testing the results</h1><strong>Serial number expiration date</strong> + + <p>Let's create another serial number with a certain expiration date. For example, 2005. This date has already passed and therefore our serial number must be incorrect. Switch to the "Licenses" section and click the "Add license" button on the toolbar. In the "Add license" dialog window enable the "Expiration date" option and specify September 30, 2005. + Create the serial number, copy it and paste to serial.txt, then run the program:</p> + <pre class="code">C:\test>dummy_app.vmp.exe +serial number is bad +state = SERIAL_STATE_FLAG_DATE_EXPIRED +</pre> + + <p>the licensing module returned the "serial number is expired" flag. Now, put the working serial number back to the serial.txt file and make sure the licensing module accepts it perfectly.</p> + <pre class="code">C:\test>dummy_app.vmp.exe +serial number is correct, calling foo() +I'm foo +done +</pre><strong>Adding a serial number to the black list</strong> + + <p>Let's imagine our "good" serial number has leaked to the Internet and is compromised now. We need to block it so that it will not work in future versions of the program. To do this, select the serial number in the list and set the "Blocked" property in the main panel to "Yes". For now, the serial number is not yet blocked, but when you protect the file again, the application will not accept this number any more. Let's make sure this is really so. If we run our program now, it should accept the blocked serial number without any problems, because this is the old version that knows nothing about the blocked number:</p> + <pre class="code">C:\test>dummy_app.vmp.exe +serial number is correct, calling foo() +I'm foo +done +</pre> + + <p>Now we make a copy of our program and name it as + "dummy_app1.vmp.exe", then open VMProtect and protect the application again. Then run this new version:</p> + <pre class="code">C:\test>dummy_app.vmp.exe +serial number is bad +state = SERIAL_STATE_FLAG_BLACKLISTED +</pre> + + <p>And the old version again, for comparison:</p> + <pre class="code">C:\test>dummy_app1.vmp.exe +serial number is correct, calling foo() +I'm foo +done +</pre> + + <p>The older version doesn't know about the blocked serial number and works as before.</p><br /> + <br /><p>On the <a href= + "step25_codelock.htm">next step</a> we will try to lock the code to a serial number. But before we proceed, unblock the serial number and reapply protection in VMProtect to the application to make it accept this serial number again. Or simply create a new license.</p><br /> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/manager/usage/step25_codelock.htm b/help/en/manager/usage/step25_codelock.htm new file mode 100644 index 0000000..5fe08bb --- /dev/null +++ b/help/en/manager/usage/step25_codelock.htm @@ -0,0 +1,69 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href= + "../../default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Step 2.5: Locking the code to a serial number</title> + <style type="text/css"> +/*<![CDATA[*/ + p.c2 {color:red;} + span.c1 {background-color:yellow;} + /*]]>*/ + </style> +</head> + +<body> + <h1>Step 2.5: Locking the code to a serial number</h1> + + <p>One of the most common ways to crack programs is to locate the place where the serial number is checked and the nearby conditional jump that follows it. If the serial number is correct, the execution of the program goes one way, if not - the other way. A hacker locates this jump and replaces it with a jump to the "correct" way. Let's "crack" our test program using this technique. Directly in the source code, of course. Let's "switch off" our conditional jump:</p> + <pre class="code">char *serial = read_serial("serial.txt"); +int res = VMProtectSetSerialNumber(serial); +delete [] serial; +if (<span class="c1">false &&</span> res) +{ +</pre> + + <p>Now, our program accepts any serial number and works normally. Of course, if the file is protected with VMProtect, even an experienced hacker would spend months to locate and modify the conditional jump as we did it. And taking into account the program check the serial number multiple times and under different conditions, even such a simple check is quite secure. But let's go further.</p><strong>locking the code to a serial number</strong> + + <p class="c2"><strong>Important!</strong> The demo-version of VMProtect has a limitation on the number of processed function: only one function is processed. So if you use the demo-version, you should only include the foo() function to the project, otherwise the demo-version of VMProtect can choose the main() function and locking to a serial number will not work.</p> + + <p>The licensing system of VMProtect allows you to lock the code of one or more functions to a serial number so, that they will not work without the correct serial number provided. the body of the function is virtualized, then encrypted and can only be decrypted with the correct serial number. This means, even if a hacker finds and fixes the conditional jump in the serial number check, functions locked to the serial number still will not work. Let's try this. In the "Functions" section choose the <strong>foo()</strong> function and at the right panel change the "Lock to Serial Number" option to "Yes".</p> + + <p><img src="../../images/lock_to_serial.png" /></p> + + <p>Then, protect the application. Since, we already "hacked" it, put an arbitrary text into the serial.txt file and run the application. The following text appears in the console:</p> + <pre class="code">C:\test>dummy_app.vmp.exe +serial number is correct, calling foo() +</pre> + + <p>This means, the hacker "fixed" the conditional jump, and the program runs on the "correct" way. But when the + <strong>foo()</strong> is invoked, the program displays a message:</p> + + <p><img src="../../images/codelock_error.png" /></p> + + <p>Since we locked the <strong>foo()</strong> function to the serial number, and the hacker does not have it, an attempt to decrypt the code of the function resulted in malfunction and inability to continue execution of the program. When "OK" is pressed, the program shuts down and the "done" message is never displayed in the console. + </p><strong>What should be locked to a serial number?</strong> + + <p>It makes sense to lock to a serial number a function that should only run in the registered version of the program. Since locking requires virtualization, you should take into account some loss of performance. For instance, if a text editor does not allow saving result in a demo-version, you can lock the save document function to a serial number. If during its operation this function calls other functions, it is not necessary to lock them too, as they won't be of any use without the main function.</p> + + <p>You should also remember that invoking the locked function without the serial number leads to program shut down, without a chance to save result of the work. that is why you should thoroughly test the application to make sure it doesn't calls such functions in the trial mode. In the above example, the text editor must disable the "Save" command in the demo mode and do not react on Ctrl+S shortcut as well. Of course, it also shouldn't ask to save the document on exit too. If you don't pay attention to this, a user may be disappointed with your "buggy" demo-version.</p><strong>Locking to a serial number and invalid serial numbers</strong> + + <p>When the <strong>VMProtectSetSerialNumber()</strong> function is invoked, the licensing module checks the serial number passed to this function. Encrypted fragments of the code are only executed if the serial number was absolutely correct at the moment of check - not blacklisted, with the correct hardware identifier, not expired and so on. In this case all encrypted procedures are executed until the application is closed, or <strong>VMProtectSetSerialNumber()</strong> is invoked again.</p> + + <p>Some limitations can "trigger" during execution of the program: for example, the operating time of the program may expire or the serial number expiration date comes. In this case the licensing module still encrypts and executes functions locked to the serial number. This is so, because it is hard for the protected application to detect the moment those limitations trigger and change the behaviour accordingly (block corresponding menu items and so on). If the licensing module suddenly stops execution of the code fragments that are locked to the serial number, this will very likely lead to malfunction of the application. That is why the decision is made when a serial number is set, and the corresponding execution mode is selected.</p><br /> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/menu_edit.htm b/help/en/menu_edit.htm new file mode 100644 index 0000000..4429214 --- /dev/null +++ b/help/en/menu_edit.htm @@ -0,0 +1,60 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>"Edit" menu</title> + <style type="text/css"> +/*<![CDATA[*/ + div.c2 {text-align: center} + /*]]>*/ + </style> +</head> + +<body> + <h1>"Edit" menu</h1> + <br /><img src= + "images/menu_edit.png" alt="Image" /> + + <ul> + <!-- + <li><strong>Отменить</strong> - отменить последние + исправления;</li> + + <li><strong>Повторить</strong> - восстановить последние + отмененные исправления;</li> + + <li><strong>Вырезать</strong> - переместить выделенные данные в + буфер обмена;</li> + + <li><strong>Копировать</strong> - скопировать выделенные данные + в буфер обмена;</li> + + <li><strong>Вставить</strong> - вставить из буфера обмена;</li> +--> + <li><strong>Delete</strong> - delete the selected element;</li> + + <li><strong>Search</strong> - search for a given text string; + <p><img src="images/expert_find.png" alt="Search" /></p> + </li> + + <li><a name="Goto" id="Goto"><strong>Go To Address</strong></a> - go to the specified address in the protected application. + You can go to a specified address or to the address selected in the "Functions" list. You can also search the desired object by name; + <p><br /><img src="images/properties_dump_goto.png" alt="Image" /></p> + </li> + </ul> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html>
\ No newline at end of file diff --git a/help/en/menu_file.htm b/help/en/menu_file.htm new file mode 100644 index 0000000..8792fcb --- /dev/null +++ b/help/en/menu_file.htm @@ -0,0 +1,50 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>"File" menu</title> + <style type="text/css"> +/*<![CDATA[*/ + div.c2 {text-align: center} + /*]]>*/ + </style> +</head> + +<body> + <h1>"File" menu</h1> + <p><img src="images/menu_file.png" /></p> + + <ul> + <li><a name="Open" id="Open"><strong>Open</strong></a> - + choose an executable you want to protect, or a project file + (*.vmp). You can also select a file to open from the list of previously protected applications shown in the File menu. You can also bring up the open dialog with the corresponding button on the toolbar <img src="images/button_open.png" />. Finally, you can drag-n-drop the file you need to the VMProtect window;</li> + + <li><strong>Save Project</strong> - save application protection settings to a "*.vmp" file. + Project settings file is saved to the same folder where the executable of the protected application is located. + Saving is also available with the toolbar button <img src="images/button_save.png" />;</li> + + <li><a name="SaveProjectAs" id= + "SaveProjectAs"><strong>Save Project As...</strong></a> - + save the project file to a file with a new name;</li> + + <li><strong>Close</strong> - finish working with the current project;</li> + + <li><strong>Exit</strong> - close VMProtect.</li> + </ul> + + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html>
\ No newline at end of file diff --git a/help/en/menu_help.htm b/help/en/menu_help.htm new file mode 100644 index 0000000..fb1167a --- /dev/null +++ b/help/en/menu_help.htm @@ -0,0 +1,38 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>"Help" menu</title> + <style type="text/css"> +/*<![CDATA[*/ + div.c2 {text-align: center} + /*]]>*/ + </style> +</head> + +<body> + <h1>"Help" menu</h1> + <p><img src="images/menu_help.png" /></p> + + <ul> + <li><strong>Home Page</strong> - open VMProtect homepage;</li> + <li><strong>Contents</strong> - open VMProtect help file;</li> + <li><strong>About...</strong> - see general information about VMProtect.</li> + </ul> + + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/menu_project.htm b/help/en/menu_project.htm new file mode 100644 index 0000000..d46beb0 --- /dev/null +++ b/help/en/menu_project.htm @@ -0,0 +1,57 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>"Project" menu</title> + <style type="text/css"> +/*<![CDATA[*/ + div.c2 {text-align: center} + /*]]>*/ + </style> +</head> + +<body> + <h1>"Project" menu</h1> + <p><img src="images/menu_project.png" /></p> + + <ul> + <li><strong>Add function</strong> - add a new function to the list of protected objects. You can specify the exact address of a function, or find that function by name: + <p><img src="images/project_add_function.png"/></p></li> + <li><strong>Add folder</strong> - add a folder to the project: + <p><img src="images/project_add_folder.png" /></p> + + <p>Usage of folders do not impacts protection of objects inside. Folders are only used to arrange protected objects in the project tree. You can move objects into a folder with simple drag-n-drop;</p></li> + + <li><strong>Add license</strong> - add a license to the project: + <p><img src="images/project_add_license.png" /></p> + + <p>This command adds a new user license and generate a license key based on entered user data: name, e-mail, date, order id and others. You can write this information inside the key, as well as to limit functionality of the license. For example, allow certain number of executions or specify an expiry date for the key.<br /> + To add a license you should first generate a pair of keys:</p> + <p><img src="images/project_generate_keys.png" /></p></li> + + <li><strong>Export Key Pair</strong> - exports project keys to the specified format of the <a href="manager/keygen/index.htm">key generator</a>: + <p><img src="images/export_keys.png" /></p></li> + + <li><strong>Import</strong> - imports a license from a serial number or from another project and adds it to the current project.</li> + + <li><strong>Compile</strong> - compile the protected application with the current protection settings. To compile the project, you can also click the toolbar button: <img src="images/button_compilation.png" />.</li> + + <li><strong>Execute</strong> - executes the protected application. Original/protected executable of the application can be started with the button on the toolbar: <img src="images/button_execute.png" />. The down arrow allows you to specify command line parameters for execution.</li> + </ul> + + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html>
\ No newline at end of file diff --git a/help/en/menu_tools.htm b/help/en/menu_tools.htm new file mode 100644 index 0000000..ae2db44 --- /dev/null +++ b/help/en/menu_tools.htm @@ -0,0 +1,41 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>"Tools" menu</title> + <style type="text/css"> +/*<![CDATA[*/ + div.c2 {text-align: center} + /*]]>*/ + </style> +</head> + +<body> + + <h1>"Tools" menu</h1> + + <p><img src="images/menu_tools.png" /></p> + + <ul> + <li><strong>Watermarks</strong> - brings up the <a href="watermarks.htm">Watermarks</a> dialog window: + <p><img src="images/watermarks_setup.png" /></p></li> + <li><strong>Preferences</strong> - brings up the Preferences window of the program: + <p><img src="images/preferences.png" /></p></li> + </ul> + + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/mode_console.htm b/help/en/mode_console.htm new file mode 100644 index 0000000..5319080 --- /dev/null +++ b/help/en/mode_console.htm @@ -0,0 +1,56 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Console version</title> +</head> + +<body> + <h1>Console version</h1> + + <p>After you created a project in the <a href="main_window.htm">GUI + mode</a> you can use the console version + (VMProtect_Con.exe). You can execute it as follows:</p> + + <p><strong>VMProtect_Con File [Output File] [-pf Project File] + [-sf Script File] [-lf Licensing Parameters File] [-bd Build Date (yyyy-mm-dd)] [-wm Watermark Name] + [-we]</strong></p> + + <ul> + <li><strong>File</strong> - the file name of the executable you want to protect (*.exe, *.dll and so on), or the file name of a (*.vmp) project. If a project file name is specified, the file name of the executable is taken from the project file.</li> + + <li><strong>Output File</strong> - the file name and path to the protected file that should be created after processing the original file. If this parameter is not set, the value is taken from the project file.</li> + + <li><strong>Project File</strong> - the file name and path to the project file created in the + <a href="main_window.htm">GUI mode</a>. If the parameter is not set, the program searches for a *.vmp file in the folder of the executable.</li> + + <li><strong>Script file</strong> - the file name of the + <a href="script.htm">script</a> the protected file is processed with. If the parameter is not set, the script from the current project file is used.</li> + + <li><strong>Licensing Parameters File</strong> - the name of a file containing <a href="manager/licenses.htm">licensing parameters</a>. + If this parameter is not set, licensing parameters are taken from the current project file.</li> + + <li><strong>Build Date</strong> - Application build date in the following format: "yyyy-mm-dd". If this parameter is not set, the current date is used. + The build date is inscribed into the protected application and is used by the licensing system to check serial numbers against the "<a href="manager/licenses.htm#AddLicense">Maximum build date</a>" field.</li> + + <li><strong>Watermark Name</strong> - the name of a + <a href="watermarks.htm">watermark</a> inserted into the protected file. If the name of a watermark is not set, the watermark specified in the project settings is used.</li> + + <li><strong>we</strong> - when this parameter is set, all warnings are displayed as errors.</li> + </ul><br /> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/project.htm b/help/en/project.htm new file mode 100644 index 0000000..743eefe --- /dev/null +++ b/help/en/project.htm @@ -0,0 +1,34 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>"Project" section</title> +</head> + +<body> + <h1>"Project" section</h1> + <p><img src="images/project_functions.png" /></p> + + The "Project" section contains the following subsections: + <ul><li><a href="project_functions.htm">Functions for Protection</a> - allows selecting objects for protection + <li><a href="manager/licenses.htm">Licenses</a> - allows managing licenses and serial numbers</li> + <li><a href="project_files.htm">Files</a> - allows including additional data files or DLL to the protected EXE file</li> + <li><a href="project_script.htm">Script</a> - allows enhancing protection capabilities by means of the built-in LUA script language</li> + <li><a href="project_options.htm">Options</a> - allows configuring application protection parameters</li> + </ul> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/project_files.htm b/help/en/project_files.htm new file mode 100644 index 0000000..ff6209f --- /dev/null +++ b/help/en/project_files.htm @@ -0,0 +1,41 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>"Files" section</title> + <style type="text/css"> + </style> +</head> + +<body> + <h1>"Files" section</h1> + + <p>The "Files" section allows the developer to include to the protected EXE file additional data it requires for operation such as: images, data files, text resources and dynamically linked libraries. During execution of the protected EXE file, all types of data including DLL are loaded from memory of the process directly, bypassing writing of these data to the disk.</p> + <p><img src="images/project_file_protection.png" /></p> + + <p>The <strong>Add File</strong> toolbar button allows adding a new file to the project. You can also add a new file with the context menu:</p> + <p><img src="images/project_file_menu.png" /></p> + + <p>To adjust properties of the selected file, select it in the left list and edit its title, file name or properties.</p> + <p><img src="images/project_file_settings.png" /></p> + + <p>To remove a file from the list of protected objects, right-click it with the mouse and choose "Delete", or simply select it and press Del.</p> + <p><img src="images/project_file_delete.png" /></p> + <p>By right-clicking a section name, you can exclude the file from compiling. Compilation exclusions are saved to the project file.</p> + + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/project_functions.htm b/help/en/project_functions.htm new file mode 100644 index 0000000..3483287 --- /dev/null +++ b/help/en/project_functions.htm @@ -0,0 +1,97 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>"Functions for Protection" section</title> + <style type="text/css"> +/*<![CDATA[*/ + div.c2 {text-align: center} + /*]]>*/ + </style> +</head> + +<body> + <h1>"Functions for Protection" section</h1> + + <p>This section is for choosing which functions must be protected.</p> + <p><img src="images/project_functions.png" /></p> + <h3 id="AddFunction">Adding a function</h3> + <p>To add a new object to the project, click the "Add Function" button on the toolbar, or select the corresponding item in the context menu:</p> + <p><img src="images/project_functions_menu.png" /></p> + <p>A new function dialog appears:</p> + <p><img src="images/project_add_function.png" /></p> + <p>Specify the address of the function, or start typing function's name to the quick search box to select the function directly from the list on the "Functions" tab. Use multi-selection if you want to add several functions at once. All selected functions are added with the chosen protection options.</p> + <p><strong>Options</strong></p> + <ul> + <li><a name="CompilationTypes" id= + "CompilationTypes"><strong>Compilation type</strong></a> - + select the way the object is compiled. Selecting a proper way to protect each object (procedure, function, code fragment) from examination and hacking results in optimal balance between performance and security of the code. + VMProtect allows the developer to set the following compilation types for each protected object:</li> + <ul> + <li><strong>Mutation.</strong> The executable code is modified at the level of CPU commands - existing commands are mutated, various "garbage" commands are added and so on. This type of compilation is relatively weak in terms of protecting the code from hack or analysis. Its main purpose is to prevent detection of processed functions with automated signature analysers (PEiD+KANAL, IDA+FLIRT etc.). This type of compilation is worthwhile to protect library functions as they usually do not require strong protection from cracking and analysis. So it is enough to modify signatures so that a potential cracker couldn't automatically detect particular libraries used in the application. Mutation provides low level of protection and analysis, but high performance of code execution.</li> + + <li><strong>Virtualization.</strong> The executable code is translated to the bytecode executed on a virtual machine. + This compilation type should be applied to all critical parts of code that require both serious hacking and analysis countermeasures and high performance. Virtualization provides average protection from hacking and analysis and average execution speed.</li> + + <li><strong>Ultra (mutation + virtualization).</strong> + The executable code is mutated on the processor instruction level and then is translated to the bytecode executed on a virtual machine. + This type of compilation should be applied to all fragments of code when the speed of execution is not critical. Ultra protection provides high protection and is executed slowly.</li> + </ul> + + <li id="LockToKey"><strong>Lock to Serial Number</strong> - if this option is enable, the protected function become <a href="manager/features.htm#lock">unavailable without a valid serial number entered</a>. In such a way you can limit access to certain functions of the application in the unregistered version.</li> + </ul> + + <p id="Search"><strong>Search</strong></p> + + <p>You can locate objects you need by their name using the quick search box:</p> + <p><img src="images/project_functions_search.png" /></p> + + <p>You can use the following wildcard symbols in the search box:</p> + <ul> + <li><strong>*</strong> - replaces any number of symbols;</li> + <li><strong>?</strong> - replaces one symbol.</li> + </ul> + + <h3 id="AddFolder">Adding a folder</h3> + <p>You can add a folder to the project using the context menu:</p> + <p><img src="images/project_functions_menu.png" /></p> + <p>Folders group protected objects and allow changing protection parameters (exclusion from compilation, type of compilation) of all objects in a folder at once.</p> + <p>Enter the name of a new folder:</p> + <p><img src="images/project_add_folder.png" /></p> + + <h3>Editing objects</h3> + <p>The right side of the window displays contents of the selected object. If a protected object is selected in the project tree, the right part displays a disassembled representation of this object:</p> + + <p><img src="images/project_functions_content.png" alt= + "Code" /></p> + <p>Right-clicking a line of code brings up the context menu:</p> + <p><img src="images/project_functions_menu3.png" /></p> + <ul> + <li><a name="ExtAddress" id="ExtAddress"><strong>External address</strong></a> - Add the chosen address to the list of <a href= + "project_options_external_addresses.htm">external addresses</a>;</li> + + <li><strong>End of function</strong> - limit the list of command that should be processed during compilation;</li> + </ul> + + <p>If a folder is selected in the project tree, the right side displays the list of functions in that folder:</p> + + <p><img src="images/project_functions_content2.png" /></p> + + <p>You can move functions to and from folders with simple drag-n-drop.</p> + + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/project_options.htm b/help/en/project_options.htm new file mode 100644 index 0000000..81cfca7 --- /dev/null +++ b/help/en/project_options.htm @@ -0,0 +1,85 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>"Options" section</title> +</head> + +<body> + <h1>"Options" section</h1> + + <p>The "Options" subsection of the "Project" section allows you to configure various protection parameters:</p> + <p><img src="images/project_options.png" /></p> + + <h3>File</h3> + + <ul> + <li><strong id="MemoryProtection">Memory Protection</strong> - + this option allows you to secure the image of the file in memory from any changes (data integrity is checked for all sections that do not have the WRITABLE attribute). Image integrity check is performed before passing the control to the original entry point of the program. If integrity is violated, a corresponding message is shown and the program stops execution.</li> + + <li><strong id="ImportProtection">Import Protection</strong> - + this option allows hiding the list of API the protected program uses from a cracker. We recommend using this option along with packing of the output file.</li> + + <li><strong id="ResourceProtection">Resource Protection</strong> - + this option encrypts resources of the program (except icons, manifests and other service resources).</li> + + <li> + <strong id="PackOutputFile">Pack the Output File</strong> + - this option allows you to pack the protected file to reduce its size. The application is unpacked automatically when the protected file is executed. The entire unpacking goes without any disk writing, completely in RAM. + + <p>When using this option, we also recommend to include + <a href="dictionary.htm#EntryPoint">EntryPoint</a> to the list of protected objects.<br /> + <strong>Important:</strong><br /> + When the program starts, after the code is unpacked the control is passed to EntryPoint. If the code of EntryPoint is virtualized, this code will be executed on the same VM interpreter as the code of the unpacker itself. Virtualization of EntryPoint combined with packing of the protected file prevents manual unpacking of the protected file, as in this case an intruder has to restore EntryPoint code to get a working file image.</p> + </li> + <li> + <strong id="Additional">Additional</strong> + - additional levels of protection:</li> + <ul> + <li> + <strong id="watermarks">Watermarks</strong> - allows adding <a href="watermarks.htm">watermarks</a> to the project. + </li> + <li><strong id="VMSectionName">VM Segments</strong> - + When the file is compiled, new segments will be added to it to the place where various system data are stored (virtualized and mutated code, VM interpreters, watermarks etc.). This option allows you to specify names for these new segments. + We recommend changing the standard ".vmp" name of segments to something else + (for example ".UPX").</li> + <li><strong>Strip Debug Information</strong> - removing of debug information impedes analysis of the code by a cracker.</li> + <li><strong>Strip Relocations</strong> - some compilers (i.e. Delphi) create a relocation table for EXE files that are not used by the operating system to load EXE files. If the option is enabled, the space occupied by relocation table is be used for VM needs.</li> + </ul> + + </ul> + + <h3>Detection</h3> + + <ul> + <li><strong id="DebuggerDetection">Debugger</strong> - this option prevents debugging of the protected file. There are 2 types of debuggers: User-mode debuggers (OllyDBG, WinDBG etc.) and + Kernel-mode debuggers(SoftICE, Syser and others). + Debugger detection is performed before passing control to the entry point of the program. If a debugger is detected, a corresponding message is shown and the program stops execution.</li> + + <li><strong id="VirtualizationToolsDetection">Virtualization Tools</strong> - this option prohibits executing the protected file in various virtual environments: + VMware, Virtual PC, VirtualBox, Sandboxie. Detection of virtualization is performed before passing control to the entry point of the program. If a virtual environment is detected, a corresponding message is shown and the program stops execution.</li> + </ul> + + <h3>Messages</h3> + <p>Here you can customize messages the program displays when it detects a debugger, a virtualization tool, if the file is corrupted or when there's an attempt to execute the code protected by a serial number.</p> + + <h3 id="LicensingParameters">Licensing parameters</h3> + + <p>Choose a project file created in the <a href="manager/licenses.htm">license manager</a> as a licensing parameter file. By default, the current project file is used.</p> + + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/project_options_external_addresses.htm b/help/en/project_options_external_addresses.htm new file mode 100644 index 0000000..a15875e --- /dev/null +++ b/help/en/project_options_external_addresses.htm @@ -0,0 +1,52 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>External Addresses</title> +</head> + +<body> + <h1>External Addresses</h1> + + When protecting an application, VMProtect utilizes the space that becomes free during compilation for its own needs, including storage of various data (virtualized or mutated code, VM interpreters and so on). As a result, certain situations may occur when a jump "inside" the protected code is made from other parts of the program. Addresses such a jump is performed from are called external. A situation described above can happen when code markers are used and a jump from a non-protected part of the program is performed inside the markers: + <pre class="code">VMProtectBegin(nil); +for I:=0 to 10 do +begin + Inc(J); + VMProtectEnd; +end; +</pre> + + <p>In the assembler code this cycle looks as:</p> + <pre class="code">----------------- marker begin ---------------- +0044D12C mov eax, 0000000B +0044D131 inc ebx +----------------- marker end ----------------- +0044D132 dec eax +0044D133 jnz 0044D131 +</pre> + + <p>Apparently, when commands at 0044D12C and 0044D131 addresses are virtualized and a non-virtualized conditional jump at 0044D133 is performed, an error occurs, because the address of 0044D131 contains various data or just garbage instead of the original code. In this example, 0044D131 is an external address.</p> + + <p>When the "Debug mode" option is enabled, the INT 03 command replaces the original code. This is a simple breakpoint and a debugger command. + When the protected application is executed under a debugger and control is passed to the 0044D131 address, a breakpoint is activated, and the debugger window displays the address the given jump is initiated at.</p> + + <p>When such jumps are detected, we recommend to check all code markers, whether they are set properly. If the protected code is not marked, or if the program logic cannot be changed so to avoid passing control inside the protected code, you should mark such addresses as <a href= + "project_functions.htm#ExtAddress">external</a> in the GUI.</p> + + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/project_script.htm b/help/en/project_script.htm new file mode 100644 index 0000000..ac5b3db --- /dev/null +++ b/help/en/project_script.htm @@ -0,0 +1,33 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>"Script" section</title> +</head> + +<body> + <h1>"Script" section</h1> + + <p>The "Script" subsection of the "Project" section is for writing scripts using the built-in <a href="script.htm">script language</a>:</p> + <p><img src="images/project_script.png" /></p> + + <p>You can edit the code of the script on the main panel of the section. The right-click menu allows manipulating with fragments of the code.</p> + <p>Certain code blocks (cycles, functions) can be collapsed or expanded using a hierarchy sign (plus or minus) near the corresponding line number.</p> + <p>Right-click the section name to exclude the script from compilation. The excluded script is not executed and is not processed by the program. This parameter is saved in the project settings.</p> + + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/recommendations.htm b/help/en/recommendations.htm new file mode 100644 index 0000000..96fbeaa --- /dev/null +++ b/help/en/recommendations.htm @@ -0,0 +1,169 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Recommendations on protecting your application</title> +</head> + +<body> + <h1>Recommendations on protecting your application</h1> + + <p>VMProtect is a reliable tool to protect the application code from analysis and cracking, yet the most efficient use is only possible if the in-app protection mechanisms are built properly, without typical mistakes that could ruin the whole protection. Let's review crucial elements of developing a good protection of your program.</p> + + <h3>Registration procedure</h3> + + <p>A typical mistake many developers make when they design their own application registration procedure is enveloping the entire registration key check to an individual function that also returns an easy-to-comprehend value:</p> + <pre class="indent code">function CheckRegistration(const RegNumber: String): Boolean; +begin + if RegNumber='123' then + Result:=True + else + Result:=False; +end; + +procedure TForm1.Button1Click(Sender: TObject); +begin + ... + if not CheckRegistration(RegNumber) then + exit; + Application.CreateForm(TForm2, Form2); + Form2.ShowModal; + ... +end; +</pre> + + <p>With such an approach, an intruder doesn't even need to understand the key check algorithm. He may simply modify the code in the beginning of the check procedure so that it always returned a correct registration key value:</p> + <pre class="indent code">function CheckRegistration(const RegNumber: String): Boolean; +begin + Result:=True; + exit; + ... +end; +</pre> + + <p>A much more effective way to check the key is to embed the check for correctness to the main operation logic of the program, so that the algorithm of registration key check could not be separated from the algorithm of the calling procedure. We also recommend to "blend" the operation logic with the registration key check procedure to make the program fail if the check was bypassed. For the above example this can be done as follows:</p> + <pre class="indent code">function CheckRegistration(const RegNumber: String): Boolean; +begin + if RegNumber='123' then + begin + Application.CreateForm(TForm2, Form2); + Result:=True + end + else + Result:=False; +end; + +procedure TForm1.Button1Click(Sender: TObject); +begin + ... + Form2:=nil; + if not CheckRegistration(RegNumber) then + exit; + Form2.ShowModal; + ... +end; +</pre> + + <p>If the CheckRegistration function is implemented like that, an intruder will have to analyze the code of registration key check in all details in order to bypass it. If this application is protected by VMProtect, virtualization of both the CheckRegistration function and TForm1.Button1Click procedure is recommended. To make the hacking even more complex, you can turn on the <a href="project_functions.htm#CompilationTypes">"Ultra" protection mode</a> to combine mutation of the code and subsequent virtualization.</p> + + <h3>Checking registration keys</h3> + + <p>Another critical mistake developers make is wrong implementation of registration key checks. Often the entered key is simply compared with the correct value. A cracker can easily match the correct value of the key by tracing arguments of the string comparison function:</p> + <pre class="indent code">var ValidRegNumber: String; +... +function CheckRegistration(const RegNumber: String): Boolean; +begin + if RegNumber=ValidRegNumber then + Result:=True + else + Result:=False; +end; +</pre> + + <p>To avoid such situation we recommend comparing hashes of keys, instead of their actual values. The hash function is irreversible, so a cracker is unable to retrieve a real key value from the hash and has to spend a lot more time to study the program, because more code fragments need to be analyzed now, not just the registration key check procedure:</p> + <pre class="indent code">var + HashOfValidRegNumber: Longint; +... +// Peter Weinberger's PJW hashing algorithm example of use +function HashPJW(const Value: String): Longint; +var I:Integer; + G:Longint; +begin + Result:=0; + for I:=1 to Length(Value) do + begin + Result:=(Result shl 4)+Ord(Value[I]); + G:=Result and $F0000000; + if G<&gt0 then + Result:=(Result xor (G shr 24)) xor G; + end; +end; + +function CheckRegistration(const RegNumber: String): Boolean; +begin + if HashPJW(RegNumber)=HashOfValidRegNumber then + Result:=True + else + Result:=False; +end; +... +initialization + HashOfValidRegNumber:=HashPJW(ValidRegNumber); + +end. +</pre> + + <p>When protecting the application with VMProtect, HashPJW and CheckRegistration function should be processed to complicate hacker's life.</p> + + <h3>Saving check results</h3> + + <p>Usually, even developers who spent a lot of time on registration procedure do not give due attention to protecting the result of the registration procedure. The below example uses a global variable to store and control the registration state of the application before invoking the serial number check procedure. For an intruder, finding a global variable is a piece of cake - he simply compares data segments BEFORE and AFTER registration. By the way, the popular ArtMoney program uses the same principle.</p> + <pre class="indent code">var IsRegistered: Boolean; +... +procedure TForm1.Button1Click(Sender: TObject); +begin + ... + if not IsRegistered then + IsRegistered:=CheckRegistration(RegNumber); + if not IsRegistered then + exit; + ... +end; +</pre> + + <p>To avoid such a situation, we recommend to store results of all checks related to registration of the program in dynamic memory. In this case scanning data segments for modified memory blocks BEFORE and AFTER registration turns useless. Here is a very simple example demonstrating how to store the result in dynamically allocated memory:</p> + <pre class="indent code">type PBoolean = ^Boolean; + +var IsRegistered: PBoolean; +... +procedure TForm1.Button1Click(Sender: TObject); +begin + ... + if not IsRegistered^ then + IsRegistered^:=CheckRegistration(RegNumber); + if not IsRegistered^ then + exit; + ... +end; +... +initialization + New(IsRegistered); +</pre> + + <p>These are the simplest ways to utilize the built-in protection mechanisms. Real-world implementations of registration procedures, registration key checks and storing the result are only limited to creativity of a developer. Anyway, you should know about these potential mistakes to avoid them while developing your own protection mechanism.</p><br /> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/script.htm b/help/en/script.htm new file mode 100644 index 0000000..2016734 --- /dev/null +++ b/help/en/script.htm @@ -0,0 +1,35 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Using scripts</title> +</head> + +<body> + <h1>Using scripts</h1> + + <p>VMProtect has a built-in powerful script language <a href="http://www.lua.org/">LUA</a> greatly enhancing the default protection capabilities of VMProtect at every stage of protection.</p> + + <p>LUA syntax is very similar to that of JavaScript, but unlike it LUA doesn't contain explicit classes. Nevertheless, the script language allows easily implementing such object-oriented programming mechanisms as classes, inheritance and events. Script usage examples can be found in the "VMProtect/Examples/Scripts" folder.</p> + <ul> + <li><a href="script_classes.htm">Classes</a></li> + <li><a href="script_functions.htm">Built-in functions</a></li> + <li><a href="script_events.htm">Events</a></li> + </ul> + + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/script_classes.htm b/help/en/script_classes.htm new file mode 100644 index 0000000..e3b5b05 --- /dev/null +++ b/help/en/script_classes.htm @@ -0,0 +1,1185 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Classes</title> +</head> + +<body> + <h1>Classes</h1> + + <p>The script language <a href="http://www.lua.org/about.html">LUA</a> built into VMProtect is object-oriented: it is very similar to JavaScript in its syntax, ideology and implementation. + The script language includes standard classes providing basic functionality and specialized classes giving access to application protection functionality. + </p> + +<h3>Class hierarchy</h3> +<ul> +<li><a href="#Core">Core</a><ul> + <li><a href="#Watermarks">Watermarks</a><ul> + <li><a href="#Watermark">Watermark</a></li> + </ul></li> + <li><a href="#Licenses">Licenses</a><ul> + <li><a href="#License">License</a></li> + </ul></li> + <li><a href="#Files">Files</a><ul> + <li><a href="#File">File</a></li> + </ul></li> + <li><a href="#Folders">Folders</a><ul> + <li><a href="#Folder">Folder</a></li> + </ul></li> + + <li><a href="#PEFile">PEFile</a><ul> + <li><a href="#PEFormat">PEFormat</a><ul> + </ul></li> + <li><a href="#PEArchitecture">PEArchitecture</a><ul> + <li><a href="#PESegments">PESegments</a><ul> + <li><a href="#PESegment">PESegment</a></li> + </ul></li> + <li><a href="#PESections">PESections</a><ul> + <li><a href="#PESection">PESection</a></li> + </ul></li> + <li><a href="#PEDirectories">PEDirectories</a><ul> + <li><a href="#PEDirectory">PEDirectory</a></li> + </ul></li> + <li><a href="#PEImports">PEImports</a><ul> + <li><a href="#PEImport">PEImport</a></li> + </ul></li> + <li><a href="#PEExports">PEExports</a><ul> + <li><a href="#PEExport">PEExport</a></li> + </ul></li> + <li><a href="#PEResources">PEResources</a><ul> + <li><a href="#PEResource">PEResource</a></li> + </ul></li> + <li><a href="#PEFixups">PEFixups</a><ul> + <li><a href="#PEFixup">PEFixup</a></li> + </ul></li> + </ul></li> + </ul></li> + <li><a href="#MacFile">MacFile</a><ul> + <li><a href="#MacFormat">MacFormat</a><ul> + </ul></li> + <li><a href="#MacArchitecture">MacArchitecture</a><ul> + <li><a href="#MacSegments">MacSegments</a><ul> + <li><a href="#MacSegment">MacSegment</a></li> + </ul></li> + <li><a href="#MacSections">MacSections</a><ul> + <li><a href="#MacSection">MacSection</a></li> + </ul></li> + <li><a href="#MacCommands">MacCommands</a><ul> + <li><a href="#MacCommand">MacCommand</a></li> + </ul></li> + <li><a href="#MacSymbols">MacSymbols</a><ul> + <li><a href="#MacSymbol">MacSymbol</a></li> + </ul></li> + <li><a href="#MacImports">MacImports</a><ul> + <li><a href="#MacImport">MacImport</a></li> + </ul></li> + <li><a href="#MacExports">MacExports</a><ul> + <li><a href="#MacExport">MacExport</a></li> + </ul></li> + <li><a href="#MacFixups">MacFixups</a><ul> + <li><a href="#MacFixup">MacFixup</a></li> + </ul></li> + </ul></li> + </ul></li> + <li><a href="#MapFunctions">MapFunctions</a><ul> + <li><a href="#MapFunction">MapFunction</a><ul> + <li><a href="#References">References</a><ul> + <li><a href="#Reference">Reference</a></li> + </ul></li> + </ul></li> + </ul></li> + <li><a href="#IntelFunctions">IntelFunctions</a><ul> + <li><a href="#IntelFunction">IntelFunction</a><ul> + <li><a href="#IntelSegment">IntelSegment</a><ul> + <li><a href="#IntelRegistr">IntelRegistr</a></li> + <li><a href="#IntelCommandType">IntelCommandType</a></li> + <li><a href="#IntelFlag">IntelFlag</a></li> + <li><a href="#IntelCommand">IntelCommand</a><ul> + <li><a href="#OperandType">OperandType</a><ul> + <li><a href="#IntelOperand">IntelOperand</a></li> + </ul></li> + </ul></li> + </ul></li> + <li><a href="#CommandLinks">CommandLinks</a><ul> + <li><a href="#LinkType">LinkType</a><ul> + <li><a href="#CommandLink">CommandLink</a></li> + </ul></li> + </ul></li> + </ul></li> + </ul></li> +</ul></li> +<li><a href="#FFILibrary">FFILibrary</a><ul> + <li><a href="#FFIFunction">FFIFunction</a></li> +</ul></li> +</ul> + +<h3>Core</h3> + +<p id="ProjectOption">Project options:</p> +<pre class="code"> +enum ProjectOption { + None, + Pack, + ImportProtection, + MemoryProtection, + ResourceProtection, + CheckDebugger, + CheckKernelDebugger, + CheckVirtualMachine, + StripFixups, + StripDebugInfo, + DebugMode +} +</pre> + +<p id="Core">A class to work with the VMProtect core:</p> +<pre class="code" id="Core"> +class Core { +public: + string projectFileName(); // returns the name of the project + void saveProject(); // saves the project + string inputFileName(); // returns the name of the source file for the current project + string outputFileName(); // returns the name of the output file for the current project + void setOutputFileName(string name); // sets the name of the output file for the current project + string watermarkName(); // returns the name of the watermark of the current project + void setWatermarkName(string name); // sets the name of the watermark for the current project + int options(); // returns <a href="#ProjectOption">options</a> of the current project + void setOptions(int options); // sets options of the current project + string vmSectionName(); // returns VM segment name for the current project + void setVMSectionName(); // sets VM segment name for the current project + <a href="#Licenses">Licenses</a> licenses(); // returns the list of licenses for the current project + <a href="#Files">Files</a> files(); // returns the list of files for the current project + <a href="#Watermarks">Watermarks</a> watermarks(); // returns the list of watermarks + <a href="#PEFile">PEFile</a>/<a href="#MacFile">MacFile</a> inputFile(); // returns source file + <a href="#PEFile">PEFile</a>/<a href="#MacFile">MacFile</a> outputFile(); // returns output file + <a href="#PEArchitecture">PEArchitecture</a>/<a href="#MacArchitecture">MacArchitecture</a> inputArchitecture(); // returns source architecture + <a href="#PEArchitecture">PEArchitecture</a>/<a href="#MacArchitecture">MacArchitecture</a> outputArchitecture(); // returns output architecture +}; +</pre> + +<h3>Watermarks</h3> + +<p id="Watermarks">A class to work with the list of <a href="watermarks.htm">watermarks</a>:</p> +<pre class="code"> +class Watermarks { +public: + <a href="#Watermark">Watermark</a> item(int index); // returns a watermark with the given index + int count(); // returns a number of watermarks in the list + <a href="#Watermark">Watermark</a> itemByName(string name); // returns a watermark with the given name + <a href="#Watermark">Watermark</a> add(string name, string value); // adds a watermark with the given name and value +} +</pre> + +<p id="Watermark">A class to work with a watermark:</p> +<pre class="code"> +class Watermark { +public: + string name(); // returns the name of the watermark + string value(); // returns the value of the watermarks + bool blocked(); // returns the "Blocked" property + void setBlocked(bool value); // sets the "Blocked" property +} +</pre> + +<h3>Licenses</h3> + +<p id="Licenses">A class to work with the list of <a href="manager/licenses.htm">licenses</a>:</p> +<pre class="code"> +class Licenses { +public: + int keyLength(); // returns the length of the key + string publicExp(); // returns the public exponent + string privateExp(); // returns the private exponent + string modulus(); // returns modulus + <a href="#License">License</a> item(int index); // returns a license with the given index + int count(); // returns the number of licenses in the list +} +</pre> + +<p id="License">A class to work with a license:</p> +<pre class="code"> +class License { +public: + string date(string format = "%c"); // returns the date of the license + string customerName(); // returns the name of the license owner + string customerEmail(); // returns an e-mail of the license owner + string orderRef(); // returns the order id the license was purchased + string comments(); // returns comments to the license + string serialNumber(); // returns the serial number of the license + bool blocked(); // returns the "Blocked" property + void setBlocked(bool value); // sets the "Blocked" property +} +</pre> + +<h3>Files</h3> + +<p id="Files">A class to work with the list of <a href="project_files.htm">files</a>:</p> +<pre class="code"> +class Files { +public: + <a href="#File">File</a> item(int index); // returns a file with the given index + int count(); // returns the number of files in the list +} +</pre> + +<p id="File">A class to work with a <a href="project_files.htm">file</a>:</p> +<pre class="code"> +class File { +public: + string name(); // returns the name of the file + string fileName(); // returns the filename + int options(); // returns options + void setName(string name); // sets the name of the file + void setFileName(string name); // sets the filename of the file + void setOptions(); // sets options +} +</pre> + +<h3>Folders</h3> + +<p id="Folders">A class to work with custom folders:</p> +<pre class="code"> +class Folders { +public: + int count(); // returns the number of folders in the list + <a href="#Folder">Folder</a> item(int index); // returns a folder with the given index + <a href="#Folder">Folder</a> add(string name); // adds a new folder + void clear(); // clears the list +}; +</pre> + +<p id="Folder">A class to work with a custom folder:</p> +<pre class="code" id="Folder"> +class Folder { +public: + int count(); // returns the number of subfolders + <a href="#Folder">Folder</a> item(int index); // returns a subfolder with the given index + <a href="#Folder">Folder</a> add(string name); // adds a new subfolder + string name(); // returns the name of the folder + void clear(); // clears the list of subfolders + void destroy(); // destroys the folder an all child subfolders +}; +</pre> + +<h3>PE files</h3> + +<p id="PEFormat">Constants to work with the PE format:</p> +<pre class="code"> +enum PEFormat { + // Directory Entries + IMAGE_DIRECTORY_ENTRY_EXPORT, + IMAGE_DIRECTORY_ENTRY_IMPORT, + IMAGE_DIRECTORY_ENTRY_RESOURCE, + IMAGE_DIRECTORY_ENTRY_EXCEPTION, + IMAGE_DIRECTORY_ENTRY_SECURITY, + IMAGE_DIRECTORY_ENTRY_BASERELOC, + IMAGE_DIRECTORY_ENTRY_DEBUG, + IMAGE_DIRECTORY_ENTRY_ARCHITECTURE, + IMAGE_DIRECTORY_ENTRY_TLS, + IMAGE_DIRECTORY_ENTRY_LOAD_CONFIG, + IMAGE_DIRECTORY_ENTRY_BOUND_IMPORT, + IMAGE_DIRECTORY_ENTRY_IAT, + IMAGE_DIRECTORY_ENTRY_DELAY_IMPORT, + IMAGE_DIRECTORY_ENTRY_COM_DESCRIPTOR, + // Section characteristics + IMAGE_SCN_CNT_CODE, + IMAGE_SCN_CNT_INITIALIZED_DATA, + IMAGE_SCN_CNT_UNINITIALIZED_DATA, + IMAGE_SCN_MEM_DISCARDABLE, + IMAGE_SCN_MEM_NOT_CACHED, + IMAGE_SCN_MEM_NOT_PAGED, + IMAGE_SCN_MEM_SHARED, + IMAGE_SCN_MEM_EXECUTE, + IMAGE_SCN_MEM_READ, + IMAGE_SCN_MEM_WRITE, + // Resource types + RT_CURSOR, + RT_BITMAP, + RT_ICON, + RT_MENU, + RT_DIALOG, + RT_STRING, + RT_FONTDIR, + RT_FONT, + RT_ACCELERATOR, + RT_RCDATA, + RT_MESSAGETABLE, + RT_GROUP_CURSOR, + RT_GROUP_ICON, + RT_VERSION, + RT_DLGINCLUDE, + RT_PLUGPLAY, + RT_VXD, + RT_ANICURSOR, + RT_ANIICON, + RT_HTML, + RT_MANIFEST, + RT_DLGINIT, + RT_TOOLBAR +}; +</pre> + +<p id="PEFile">A class to work with a PE file:</p> +<pre class="code"> +class PEFile { +public: + string name(); // returns the filename + string format(); // returns the "PE" format name + uint64 size(); // returns the size of the file + int count(); // returns the number of architectures in the list + <a href="#PEArchitecture">PEArchitecture</a> item(int index); // returns an architecture with the given index + uint64 seek(uint64 offset); // sets a file position + uint64 tell(); // returns a file position + int write(string buffer); // records a buffer to the file +}; +</pre> + +<p id="PEArchitecture">A class to work with the PE architecture:</p> +<pre class="code"> +class PEArchitecture { +public: + string name(); // returns the name of the architecture + <a href="#PEFile">PEFile</a> file(); // returns the parent file + uint64 entryPoint(); // returns the starting address + uint64 imageBase(); // returns the base offset + <a href="#OperandSize">OperandSize</a> cpuAddressSize(); // returns bit count of the architecture + uint64 size(); // returns the size of the architecture + <a href="#PESegments">PESegments</a> segments(); // returns the list of segments + <a href="#PESections">PESections</a> sections(); // returns the list of sections + <a href="#PEDirectories">PEDirectories</a> directories(); // returns the list of directories + <a href="#PEImports">PEImports</a> imports(); // returns the list of imported libraries + <a href="#PEExports">PEExports</a> exports(); // returns the list of exported functions + <a href="#PEResources">PEResources</a> resources(); // returns the list of resources + <a href="#PEFixups">PEFixups</a> fixups(); // returns the list of relocations (fixups); + <a href="#MapFunctions">MapFunctions</a> mapFunctions(); // returns the list of functions available for protection + <a href="#IntelFunctions">IntelFunctions</a> functions(); // returns the list of protected functions + bool addressSeek(uint64 address); // sets a file position + uint64 seek(uint64 offset); // sets a file position + uint64 tell(); // returns a file position + int write(string buffer); // writes a buffer to a file +}; +</pre> + +<p id="PESegments">A class to work with the list of segments for the PE architecture:</p> +<pre class="code"> +class PESegments { +public: + <a href="#PESegment">PESegment</a> item(int index); // returns a segment with the given index + int count(); // returns the number of segments in the list + <a href="#PESegment">PESegment</a> itemByAddress(uint64 address); // returns the segment at the given address +}; +</pre> + +<p id="PESegment">A class to work with a PE architecture segment:</p> +<pre class="code"> +class PESegment { +public: + uint64 address(); // returns the address of the segment + string name(); // returns the name of the segment + uint64 size(); // returns the size of the segment + int physicalOffset(); // returns the file position (offset) of the segment + int physicalSize(); // returns the file size of the segment + int flags(); // returns flags of the segment + bool excludedFromPacking(); // returns the "Excluded from packing" property + void setName(string name); // sets the name of the segment +}; +</pre> + +<p id="PESections">A class to work with the list of PE architecture sections:</p> +<pre class="code"> +class PESections { +public: + <a href="#PESection">PESection</a> item(int index); // returns a section with the given index + int count(); // returns the number of sections in the list + <a href="#PESection">PESection</a> itemByAddress(uint64 address); // returns a section at the given address +}; +</pre> + +<p id="PESection">A class to work with a PE architecture section:</p> +<pre class="code"> +class PESection { +public: + uint64 address(); // returns the address of the section + string name(); // returns the name of the section + uint64 size(); // returns the size of the section + int offset(); // returns the file positions of the section + <a href="#PESegment">PESegment</a> segment(); // returns the parent segment +}; +</pre> + +<p id="PEDirectories">A class to work with PE architecture directories:</p> +<pre class="code"> +class PEDirectories { +public: + <a href="#PEDirectory">PEDirectory</a> item(int index); // returns a directory with the given index + int count(); // returns the number of directories in the list + <a href="#PEDirectory">PEDirectory</a> itemByType(int type); // returns a directory of the given type +}; +</pre> + +<p id="PEDirectory">A class to work with a PE architecture directory:</p> +<pre class="code"> +class PEDirectory { +public: + uint64 address(); // returns the address of the directory + string name(); // returns the name of the directory + uint64 size(); // returns the size of the directory + int type(); // returns the type of the directory + void setAddress(uint64 address); // sets the address of the directory + void setSize(int size); // sets the size of the directory + void clear(); // clears the address and the size of the directory +}; +</pre> + +<p id="PEImports">A class to work with the list of imported libraries for the PE architecture:</p> +<pre class="code"> +class PEImports { +public: + <a href="#PEImport">PEImport</a> item(int index); // returns a library with the given index + int count(); // returns the number of libraries in the list + <a href="#PEImport">PEImport</a> itemByName(string name); // returns a library with the given name +}; +</pre> + +<p id="PEImport">A class to work with an imported library for the PE architecture :</p> +<pre class="code"> +class PEImport { +public: + string name(); // returns the name of the library + <a href="#PEImportFunction">PEImportFunction</a> item(int index); // returns an imported function with the given index + int count(); // returns the number of imported functions + void setName(string name); // sets the name of the library +}; +</pre> + +<p id="PEImportFunction">A class to work with a PE architecture imported function:</p> +<pre class="code"> +class PEImportFunction { +public: + uint64 address(); // returns a memory address where the imported function address is stored + string name(); // returns the name of the imported function +}; +</pre> + +<p id="PEExports">A class to work with the list of exported functions for the PE architecture :</p> +<pre class="code"> +class PEExports { +public: + string name(); // returns the name of the library + void setName(string name); // sets the name of the library + <a href="#PEExport">PEExport</a> item(int index); // returns an exported function with the given index + int count(); // returns the number of exported functions in the list + void clear(); // clears the list + <a href="#PEExport">PEExport</a> itemByAddress(uint64 address); // returns an exported function at the given address + <a href="#PEExport">PEExport</a> itemByName(string name); // returns an exported function with the given name +}; +</pre> + +<p id="PEExport">A class to wotk with a PE architecture exported function:</p> +<pre class="code"> +class PEExport { +public: + uint64 address(); // returns the address of the exported function + string name(); // returns the name of the exported function + void setName(string name); // sets the name of the exported function + int ordinal(); // returns the ordinal of the exported function + string forwardedName(); // returns the name of the function the exported function forwards to + void destroy(); // destroys the exported function +}; +</pre> + +<p id="PEResources">A class to work with the list of PE architecture resources:</p> +<pre class="code"> +class PEResources { +public: + <a href="#PEResource">PEResource</a> item(int index); // returns a resources with the given index + int count(); // returns the number of resources in the list + void clear(); // clears the list + <a href="#PEResource">PEResource</a> itemByType(int type); // returns a resource of the given type + <a href="#PEResource">PEResource</a> itemByName(string name); // returns a resource with the given name +}; +</pre> + +<p id="PEResource">A class to work with a PE architecture resource:</p> +<pre class="code"> +class PEResource { +public: + <a href="#PEResource">PEResource</a> item(int index); // returns a resource with the given index + int count(); // returns the number of resources in the list + void clear(); // clears the list + uint64 address(); // returns the address of the resource + int size(); // returns the size of the resource + string name(); // returns the name of the resource + int type(); // returns the type of the resource + bool isDirectory(); // returns the "Directory" property + void destroy(); // destroys the resource + <a href="#PEResource">PEResource</a> itemByName(string name); // returns a resource with the given name + bool excludedFromPacking(); // returns the "Excluded from packing" property +}; +</pre> + +<p id="PEFixups">A class to work with the list of PE architecture fixups (relocations):</p> +<pre class="code"> +class PEFixups { +public: + <a href="#PEFixup">PEFixup</a> item(int index); // returns an element with the given index + int count(); // returns the number of elements in the list + <a href="#PEFixup">PEFixup</a> itemByAddress(uint64 address); // returns an element at the given address +}; +</pre> + +<p id="PEFixup">A class to work with a PE architecture fixup (relocation):</p> +<pre class="code"> +class PEFixup { +public: + uint64 address(); // returns the address of the element +}; +</pre> + +<h3>Mach-O files</h3> + +<p id="MacFormat">Constants to work with the Mach-O format:</p> +<pre class="code"> +enum MacFormat { + // Load Command Types + LC_SEGMENT, + LC_SYMTAB, + LC_SYMSEG, + LC_THREAD, + LC_UNIXTHREAD, + LC_LOADFVMLIB, + LC_IDFVMLIB, + LC_IDENT, + LC_FVMFILE, + LC_PREPAGE, + LC_DYSYMTAB, + LC_LOAD_DYLIB, + LC_ID_DYLIB, + LC_LOAD_DYLINKER, + LC_PREBOUND_DYLIB, + LC_ROUTINES, + LC_SUB_FRAMEWORK, + LC_SUB_UMBRELLA, + LC_SUB_CLIENT, + LC_SUB_LIBRARY, + LC_TWOLEVEL_HINTS, + LC_PREBIND_CKSUM, + LC_LOAD_WEAK_DYLIB, + LC_SEGMENT_64, + LC_ROUTINES_64, + LC_UUID, + LC_RPATH, + LC_CODE_SIGNATURE, + LC_SEGMENT_SPLIT_INFO, + LC_REEXPORT_DYLIB, + LC_LAZY_LOAD_DYLIB, + LC_ENCRYPTION_INFO, + LC_DYLD_INFO, + LC_DYLD_INFO_ONLY, + LC_LOAD_UPWARD_DYLIB, + LC_VERSION_MIN_MACOSX, + // Section Types + SECTION_TYPE, + SECTION_ATTRIBUTES, + S_REGULAR, + S_ZEROFILL, + S_CSTRING_LITERALS, + S_4BYTE_LITERALS, + S_8BYTE_LITERALS, + S_LITERAL_POINTERS, + S_NON_LAZY_SYMBOL_POINTERS, + S_LAZY_SYMBOL_POINTERS, + S_SYMBOL_STUBS, + S_MOD_INIT_FUNC_POINTERS, + S_MOD_TERM_FUNC_POINTERS, + S_COALESCED, + S_GB_ZEROFILL, + S_INTERPOSING, + S_16BYTE_LITERALS, + S_DTRACE_DOF, + S_LAZY_DYLIB_SYMBOL_POINTERS, + SECTION_ATTRIBUTES_USR, + S_ATTR_PURE_INSTRUCTIONS, + S_ATTR_NO_TOC, + S_ATTR_STRIP_STATIC_SYMS, + S_ATTR_NO_DEAD_STRIP, + S_ATTR_LIVE_SUPPORT, + S_ATTR_SELF_MODIFYING_CODE, + S_ATTR_DEBUG, + SECTION_ATTRIBUTES_SYS, + S_ATTR_SOME_INSTRUCTIONS, + S_ATTR_EXT_RELOC, + S_ATTR_LOC_RELOC +}; +</pre> + +<p id="MacFile">A class to work with a Mach-O file:</p> +<pre class="code"> +class MacFile { +public: + string name(); // returns the name of the file + string format(); // returns the name of the "Mach-O" format + uint64 size(); // returns the size of the file + int count(); // returns the number of architectures in the list + <a href="#MacArchitecture">MacArchitecture</a> item(int index); // returns an architecture with the given index + uint64 seek(uint64 offset); // sets the file position + uint64 tell(); // returns the file position + int write(string buffer); // writes a buffer to the file +}; +</pre> + +<p id="MacArchitecture">A class to work with the Mach-O architecture:</p> +<pre class="code"> +class MacArchitecture { +public: + string name(); // returns the name of the architecture + <a href="#MacFile">MacFile</a> file(); // returns the parent file + uint64 entryPoint(); // returns the starting address + <a href="#OperandSize">OperandSize</a> cpuAddressSize(); // returns bit count of the architecture + uint64 size(); // returns the size of the architecture + <a href="#MacSegments">MacSegments</a> segments(); // returns the list of segments + <a href="#MacSections">MacSections</a> sections(); // returns the list of sections + <a href="#MacCommands">MacCommands</a> commands(); // returns the list of load commands + <a href="#MacSymbols">MacSymbols</a> symbols(); // returns the list of symbols + <a href="#MacImports">MacImports</a> imports(); // returns the list of imported libraries + <a href="#MacExports">MacExports</a> exports(); // returns the list of exported functions + <a href="#MacFixups">MacFixups</a> fixups(); // returns the list of fixups (relocations) + <a href="#MapFunctions">MapFunctions</a> mapFunctions(); // returns the list of functions available for protection + <a href="#IntelFunctions">IntelFunctions</a> functions(); // returns the list of protected functions + bool addressSeek(uint64 address); // sets the file position + uint64 seek(uint64 offset); // sets the file position + uint64 tell(); // returns the file position + int write(string buffer); // writes a buffer to the file +}; +</pre> + +<p id="MacSegments">A class to work with the list of Mach-O architecture segments:</p> +<pre class="code"> +class MacSegments { +public: + <a href="#MacSegment">MacSegment</a> item(int index); // returns a segment with the given index + int count(); // returns the number of segments in the list + <a href="#MacSegment">MacSegment</a> itemByAddress(); // returns a segment at the given address +}; +</pre> + +<p id="MacSegment">A class to work with a Mach-O architecture segment:</p> +<pre class="code" id="MacSegment"> +class MacSegment { +public: + uint64 address(); // returns the address of the segment + string name(); // returns the name of the segment + uint64 size(); // returns the size of the segment + int physicalOffset(); // returns the file position of the segment + int physicalSize(); // returns the file size of the segment + int flags(); // returns flags of the segment + bool excludedFromPacking(); // returns the "Excluded from packing" property +}; +</pre> + +<p id="MacSections">A class to work with the list of Mach-O architecture sections:</p> +<pre class="code"> +class MacSections { +public: + <a href="#MacSection">MacSection</a> item(int index); // returns a section with the given index + int count(); // returns the number of sections in the list + <a href="#MacSection">MacSection</a> itemByAddress(uint64 address); // returns a section at the given address +}; +</pre> + +<p id="MacSection">A class to work with a Mach-O architecture section:</p> +<pre class="code"> +class MacSection { +public: + uint64 address(); // returns the address of the section + string name(); // returns the name of the section + uint64 size(); // returns the size of the section + int offset(); // returns the file position of the section + <a href="#MacSegment">MacSegment</a> segment(); // returns the parent segment +}; +</pre> + +<p id="MacCommands">A class to work with the list of Mach-O architecture load commands:</p> +<pre class="code"> +class MacCommands { +public: + <a href="#MacCommand">MacCommand</a> item(int index); // returns a command with the given index + int count(); // returns the number of command in the list + <a href="#MacCommand">MacCommand</a> itemByType(int type); // returns a command of the given type +}; +</pre> + +<p id="MacCommand">A class to work with a Mach-O architecture load command:</p> +<pre class="code"> +class MacCommand { +public: + uint64 address(); // returns the address of the command + int type(); // returns the type of the command + string name(); // returns the name of the command + int size(); // returns the size of the command +}; +</pre> + +<p id="MacSymbols">A class to work with the list of Mach-O architecture symbols:</p> +<pre class="code"> +class MacSymbols { +public: + <a href="#MacSymbol">MacSymbol</a> item(int index); // returns a symbol with the given index + int count(); // returns the number of symbols in the list +}; +</pre> + +<p id="MacSymbol">A class to work with a Mach-O architecture symbol:</p> +<pre class="code"> +class MacSymbol { +public: + uint64 value(); // returns the value of the symbol + string name(); // returns the name of the symbol +}; +</pre> + +<p id="MacImports">A class to work with the list of imported libraries for the Mach-O architecture:</p> +<pre class="code"> +class MacImports { +public: + <a href="#MacImport">MacImport</a> item(int index); // returns an imported library with the given index + int count(); // returns the number of imported libraries in the list + <a href="#MacImport">MacImport</a> itemByName(string name); // returns an imported library with the given name +}; +</pre> + +<p id="MacImport">A class to work with a Mach-O architecture imported library:</p> +<pre class="code"> +class MacImport { +public: + string name(); // returns the name of the imported library + <a href="#MacImportFunction">MacImportFunction</a> item(int index); // returns an imported function with the given index + int count(); // returns the number of imported functions in the list + void setName(string name); // sets the name of the imported library +}; +</pre> + +<p id="MacImportFunction">A class to work with a Mach-O architecture imported function:</p> +<pre class="code"> +class MacImportFunction { +public: + uint64 address(); // returns the memory address where the address of the imported function is stored + string name(); // returns the name of the imported function +}; +</pre> + +<p id="MacExports">A class to work with the list of exported functions for the Mach-O architecture:</p> +<pre class="code"> +class MacExports { +public: + string name(); // returns the name of the library + <a href="#MacExport">MacExport</a> item(); // returns an exported function with the given index + int count(); // returns the number of exported functions in the list + void clear(); // clears the list + <a href="#MacExport">MacExport</a> itemByAddress(uint64 address); // returns an exported function at the given address + <a href="#MacExport">MacExport</a> itemByName(string name); // returns an exported function with the given name +}; +</pre> + +<p id="MacExport">A class to work with a Mach-O architecture exported function:</p> +<pre class="code"> +class MacExport { +public: + uint64 address(); // returns the address of the exported function + string name(); // returns the name of the exported function + string forwardedName(); // returns the name of the function the exported function is forwarded to + void destroy(); // destroys the exported function +}; +</pre> + +<p id="MacFixups">A class to work with the list of fixups (relocations) for the Mach-O architecture:</p> +<pre class="code"> +class MacFixups { +public: + <a href="#MacFixup">MacFixup</a> item(int index); // returns an element with the given index + int count(); // returns the number of elements in the list + <a href="#MacFixup">MacFixup</a> itemByAddress(uint64 address); // returns an element at the given address +}; +</pre> + +<p id="MacFixup">A class to work with a Mach-O architecture fixup:</p> +<pre class="code"> +class MacFixup { +public: + uint64 address(); // returns the address of the element +}; +</pre> + +<h3>Functions</h3> + +<p id="MapFunctions">A class to work with the list of functions:</p> +<pre class="code"> +class MapFunctions { +public: + <a href="#MapFunction">MapFunction</a> item(int index); // returns a function with the given index + int count(); // returns the number of functions in the list + <a href="#MapFunction">MapFunction</a> itemByAddress(uint64 address); // returns a function at the given address + <a href="#MapFunction">MapFunction</a> itemByName(string name); // returns a function with the given name +}; +</pre> + +<p id="ObjectType">Types of functions:</p> +<pre class="code"> +enum ObjectType { + Unknown, + Code, + Data, + Export, + Marker, + APIMarker, + Import, + String +}; +</pre> + +<p id="MapFunction">A class to work with a function:</p> +<pre class="code"> +class MapFunction { +public: + uint64 address(); // returns the address of the function + string name(); // returns the name of the function + <a href="#ObjectType">ObjectType</a> type(); // returns the type of the function + <a href="#References">References</a> references(); // returns the list of references +}; +</pre> + +<p id="References">A class to work with the list of references:</p> +<pre class="code"> +class References { +public: + <a href="#Reference">Reference</a> item(int index); // returns a reference with the given index + int count(); // returns the number of references in the list +}; +</pre> + +<p id="Reference">A class to work with a reference:</p> +<pre class="code"> +class Reference { +public: + uint64 address(); // returns the address of the command + uint64 operandAddress(); // returns the address of the references +}; +</pre> + +<h3>Intel functions</h3> + +<p id="IntelFunctions">A class to work with the list of Intel functions:</p> +<pre class="code"> +class IntelFunctions { +public: + <a href="#IntelFunction">IntelFunction</a> item(int index); // returns a function with the given index + int count(); // returns the number of functions in the list + void clear(); // clears the list + <a href="#IntelFunction">IntelFunction</a> itemByAddress(uint64 address); // returns a function at the given address + <a href="#IntelFunction">IntelFunction</a> itemByName(string name); // returns a function with the given name + <a href="#IntelFunction">IntelFunction</a> addByAddress(uint64 address, <a href="#CompilationType">CompilationType</a> type = ctVirtualization); + // Adds a new function with the given address and compilation type +}; +</pre> + +<p id="CompilationType">Compilation types:</p> +<pre class="code"> +enum CompilationType { + None, + Virtualization, + Mutation, + Ultra +}; +</pre> + +<p id="IntelFunction">A class to work with an Intel function:</p> +<pre class="code"> +class IntelFunction { +public: + uint64 address(); // returns the address of the function + string name(); // returns the name of the function + <a href="#ObjectType">ObjectType</a> type(); // returns the type of the function + <a href="#IntelCommand">IntelCommand</a> item(int index); // returns a command with the given index + int count(); // returns the number of commands in the list + <a href="#CompilationType">CompilationType</a> compilationType(); // returns the compilation type + void setCompilationType(<a href="#CompilationType">CompilationType</a> value); // sets the compilation type + <a href="#CommandLinks">CommandLinks</a> links(); // returns the list of links + <a href="#IntelCommand">IntelCommand</a> itemByAddress(uint64 address); // returns a command at the given address + void destroy(); // destroys the function + <a href="#Folder">Folder</a> folder(); // returns the custom folder + void setFolder(<a href="#Folder">Folder</a> folder); // sets the custom folder +}; +</pre> + +<p id="IntelCommandType">Types of Intel commands:</p> +<pre class="code"> +enum IntelCommandType { + Unknown, Push, Pop, Mov, Add, Xor, Test, Lea, Ud0, Ret, Ssh, Crc, Call, Jmp, + Fstsw, Fsqrt, Fchs, Fstcw, Fldcw, Fild, Fist, Fistp, Fld, Fstp, Fst, Fadd, + Fsub, Fsubr, Fisub, Fisubr, Fdiv, Fcomp, Fmul, Repe, Repne, Rep, DB, DW, DD, DQ, + Movs, Cmps, Scas, Movzx, Movsx, Inc, Dec, Les, Lds, Lfs, Lgs, Lss, Xadd, Bswap, + Jxx, And, Sub, Stos, Lods, Nop, Xchg, Pushf, Popf, Sahf, Lahf, Shl, Shr, Sal, + Sar, Rcl, Rcr, Rol, Ror, Shld, Shrd, Loope, Loopne, Loop, Jcxz, In, Ins, Out, + Outs, Wait, Cbw, Cwde, Cdqe, Cwd, Cdq, Cqo, Clc, Stc, Cli, Sti, Cld, Std, Not, + Neg, Div, Imul, Idiv, Mul, Or, Adc, Cmp, Sbb, Pusha, Popa, Clflush, Pause, + Bound, Arpl, Daa, Das, Aaa, Aam, Aad, Aas, Enter, Leave, Int, Into, Iret, Set, + Cmov, Addpd, Addps, Addsd, Addss, Andpd, Andps, Andnpd, Andnps, Cmppd, Cmpps, + Cmpsd, Cmpss, Comisd, Comiss, Cvtdq2ps, Cvtpd2dq, Cvtdq2pd, Cvtpd2pi, Cvtps2pi, + Cvtpd2ps, Cvtps2pd, Cvtpi2pd, Cvtpi2ps, Cvtps2dq, Cvtsd2si, Cvtss2si, Cvtsd2ss, + Cvtss2sd, Cvttpd2pi, Cvttps2pi, Cvttpd2dq, Cvttps2dq, Cvttsd2si, Cvttss2si, + Divpd, Divps, Divsd, Divss, Maxpd, Maxps, Maxsd, Maxss, Minpd, Minps, Minsd, + Minss, Mulpd, Mulps, Mulsd, Mulss, Orpd, Orps, Movd, Movq, Movntq, Movapd, Movaps, + Movdqa, Movdqu, Movdq2q, Movq2dq, Movhlps, Movhpd, Movhps, Movlhps, Movlpd, + Movlps, Movmskpd, Movmskps, Movnti, Movntpd, Movntps, Movsd, Movss, Movupd, + Movups, Pmovmskb, Psadbw, Pshufw, Pshufd, Pshuflw, Pshufhw, Psubb, Psubw, Psubd, + Psubq, Psubsb, Psubsw, Psubusb, Psubusw, Paddb, Paddw, Paddd, Paddq, Paddsb, + Paddsw, Paddusb, Paddusw, Pavgb, Pavgw, Pinsrw, Pextrw, Pmaxsw, Pmaxub, Pminsw, + Pminub, Pmulhuw, Pmulhw, Pmullw, Pmuludq, Psllw, Pslld, Psllq, Pslldq, Psraw, + Psrad, Psrlw, Psrld, Psrlq, Psrldq, Punpcklbw, Punpcklwd, Punpckldq, Punpcklqdq, + Punpckhqdq, Packusdw, Pcmpgtb, Pcmpgtw, Pcmpgtd, Pcmpeqb, Pcmpeqw, Pcmpeqd, + Emms, Packsswb, Packuswb, Punpckhbw, Punpckhwd, Punpckhdq, Packssdw, Pand, + Pandn, Por, Pxor, Pmaddwd, Rcpps, Rcpss, Rsqrtss, Movsxd, Shufps, Shufpd, Sqrtpd, + Sqrtps, Sqrtsd, Sqrtss, Subpd, Subps, Subsd, Subss, Ucomisd, Ucomiss, Unpckhpd, + Unpckhps, Unpcklpd, Unpcklps, Xorpd, Xorps, Bt, Bts, Btr, Btc, Xlat, Cpuid, + Rsm, Bsf, Bsr, Cmpxchg, Cmpxchg8b, Hlt, Cmc, Lgdt, Sgdt, Lidt, Sidt, Smsw, Lmsw, + Invlpg, Lar, Lsl, Clts, Invd, Wbinvd, Ud2, Wrmsr, Rdtsc, Rdmsr, Rdpmc, Fcom, + Fdivr, Fiadd, Fimul, Ficom, Ficomp, Fidiv, Fidivr, Faddp, Fmulp, Fsubp, Fsubrp, + Fdivp, Fdivrp, Fbld, Fbstp, Ffree, Frstor, Fsave, Fucom, Fucomp, Fldenv, Fstenvm, + Fxch, Fabs, Fxam, Fld1, Fldl2t, Fldl2e, Fldpi, Fldlg2, Fldln2, Fldz, Fyl2x, + Fptan, Fpatan, Fxtract, Fprem1, Fdecstp, Fincstp, Fprem, Fyl2xp1, Fsincos, Frndint, + Fscale, Fsin, Fcos, Ftst, Fstenv, F2xm1, Fnop, Finit, Fclex, Fcompp, Sysenter, + Sysexit, Sldt, Str, Lldt, Ltr, Verr, Verw, Sfence, Lfence, Mfence, Prefetchnta, + Prefetcht0, Prefetcht1, Prefetcht2, Prefetch, Prefetchw, Fxrstor, Fxsave, Ldmxcsr, + Stmxcsr, Fcmovb, Fcmove, Fcmovbe, Fcmovu, Fcmovnb, Fcmovne, Fcmovnbe, Fcmovnu, + Fucomi, Fcomi, Fucomip, Fcomip, Fucompp, Vmcall, Vmlaunch, Vmresume, Vmxoff, + Monitor, Mwait, Xgetbv, Xsetbv, Vmrun, Vmmcall, Vmload, Vmsave, Stgi, Clgi, + Skinit, Invlpga, Swapgs, Rdtscp, Syscall, Sysret, Femms, Getsec, Pshufb, Phaddw, + Phaddd, Phaddsw, Pmaddubsw, Phsubw, Phsubd, Phsubsw, Psignb, Psignw, Psignd, + Pmulhrsw, Pabsb, Pabsw, Pabsd, Movbe, Palignr, Rsqrtps, Vmread, Vmwrite, Svldt, + Rsldt, Svts, Rsts, Xsave, Xrstor, Vmptrld, Vmptrst, Maskmovq, Fnstenv, Fnstcw, + Fstp1, Fneni, Fndisi, Fnclex, Fninit, Fsetpm, Fisttp, Fnsave, Fnstsw, Fxch4, + Fcomp5, Ffreep, Fxch7, Fstp8, Fstp9, Haddpd, Hsubpd, Addsubpd, Addsubps, Movntdq, + Fcom2, Fcomp3, Haddps, Hsubps, Movddup, Movsldup, Cvtsi2sd, Cvtsi2ss, Movntsd, + Movntss, Lddqu, Movshdup, Popcnt, Tzcnt, Lzcnt, Pblendvb, Pblendps, Pblendpd, + Ptest, Movsxbw, Movsxbd, Movsxbq, Movsxwd, Movsxwq, Movsxdq, Muldq, Pcmpeqq, + Movntdqa, Xsaveopt, Maskmovdqu, Ud1, Pcmpgtq, Movzxbw, Movzxbd, Movzxbq, Movzxwd, + Movzxwq, Movzxdq +}; +</pre> + +<p id="IntelSegment">Intel segments:</p> +<pre class="code"> +enum IntelSegment { + None, + es, + cs, + ss, + ds, + fs, + gs +}; +</pre> + +<p id="IntelFlag">Intel flags:</p> +<pre class="code"> +enum IntelFlag { + C, + P, + A, + Z, + S, + T, + I, + D, + O +}; +</pre> + +<p id="IntelRegistr">Intel registers:</p> +<pre class="code"> +enum IntelRegistr { + eax, + ecx, + edx, + ebx, + esp, + ebp, + esi, + edi, + r8, + r9, + r10, + r11, + r12, + r13, + r14, + r15 +}; +</pre> + +<p id="IntelCommand">A class to work with an Intel command:</p> +<pre class="code"> +class IntelCommand { +public: + uint64 address(); // returns the address of the command + <a href="#IntelCommandType">IntelCommandType</a> type(); // returns the type of the command + string text(); // returns the text representation + int size(); // returns the size of the command + int dump(int index); // returns data of the command with the given index + <a href="#CommandLink">CommandLink</a> link(); // returns the command link + int flags(); // returns command flags + <a href="#IntelSegment">IntelSegment</a> baseSegment(); // returns the base segment + <a href="#IntelCommandType">IntelCommandType</a> preffix(); // returns the type of the prefix command + <a href="#IntelOperand">IntelOperand</a> operand(int index); // returns an operand with the given index +}; +</pre> + +<p id="OperandType">Operand types:</p> +<pre class="code"> +enum OperandType { + None, + Value, + Registr, + Memory, + SegmentRegistr, + ControlRegistr, + DebugRegistr, + FPURegistr, + HiPartRegistr, + BaseRegistr, + MMXRegistr, + XMMRegistr +}; +</pre> + +<p id="OperandSize">Operand sizes:</p> +<pre class="code"> +enum OperandSize { + Byte, + Word, + DWord, + QWord, + TByte, + OWord, + FWord +}; +</pre> + +<p id="IntelOperand">A class to work with an operand of the Intel command:</p> +<pre class="code"> +class IntelOperand { +public: + int type(); // returns the type of the operand + <a href="#OperandSize">OperandSize</a> size(); // returns the size of the operand + int registr(); // returns the register + int baseRegistr(); // returns the base register + int scale(); // returns the scale + uint64 value(); // returns the value +}; +</pre> + +<p id="CommandLinks">A class to work with the list of command links:</p> +<pre class="code" id="CommandLinks"> +class CommandLinks { +public: + <a href="#CommandLink">CommandLink</a> item(int index); // returns a link with the given index + int count(); // returns the number of links in the list +}; +</pre> + +<p id="LinkType">Link types:</p> +<pre class="code"> +enum LinkType { + None, + SEHBlock, + FinallyBlock, + DualSEHBlock, + FilterSEHBlock, + Jmp, + JmpWithFlag, + JmpWithFlagNSFS, + JmpWithFlagNSNA, + JmpWithFlagNSNS, + Call, + Case, + Switch, + Native, + Offset, + GateOffset, + ExtSEHBlock, + MemSEHBlock, + ExtSEHHandler, + VBMemSEHBlock +}; +</pre> + +<p id="CommandLink">A class to work with a command link:</p> +<pre class="code"> +class CommandLink { +public: + uint64 toAddress(); // returns the address the link refers + <a href="#LinkType">LinkType</a> type(); // returns the type of the link + <a href="#IntelCommand">IntelCommand</a> from(); // returns the parent command +}; +</pre> + +<p id="FFILibrary">A class to work with a library:</p> +<pre class="code"> +enum ParamType { + "void", + "byte", + "char", + "short", + "ushort", + "int", + "uint", + "long", + "ulong", + "size_t", + "float", + "double", + "string", + "pointer" +}; + +enum CallType { + "default", + "cdecl", + "stdcall" +}; + +class FFILibrary { +public: + string name(); // returns the name + uint64 address(); // returns the address in the memory + void close(); + FFIFunction getFunction(string name, ParamType ret, ParamType param1, ...); // returns a function + FFIFunction getFunction(string name, table (ParamType ret, CallType abi, ParamType, ...)); // returns a function +}; +</pre> + +<p id="FFIFunction">A class to work with a foreign function:</p> +<pre class="code"> +class FFIFunction { + string name(); // returns the name + uint64 address(); // returns the address in the memory +}; +</pre> + + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html>
\ No newline at end of file diff --git a/help/en/script_events.htm b/help/en/script_events.htm new file mode 100644 index 0000000..cd94d7d --- /dev/null +++ b/help/en/script_events.htm @@ -0,0 +1,61 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Events</title> +</head> + +<body> + <h1>Events</h1> + + <p>The built in script language is an efficient way to automate creation of protected applications with VMProtect. Procedures and functions required at various stages of building the protected file are invoked in certain events processed by the VMProtect core. You can set your own handlers for 5 events that are called by the VMProtect core in the following order:</p> + + <ul> + <li><a href="#OnBeforeCompilation">OnBeforeCompilation</a></li> + <li><a href="#OnBeforeSaveFile">OnBeforeSaveFile</a></li> + <li><a href="#OnBeforePackFile">OnBeforePackFile</a></li> + <li><a href="#OnAfterSaveFile">OnAfterSaveFile</a></li> + <li><a href="#OnAfterCompilation">OnAfterCompilation</a></li> + </ul> + <a name="OnBeforeCompilation" /><pre class="code">function OnBeforeCompilation() + +end</pre> + + <p>This event is invoked when the list of protection objects is created. In the OnBeforeCompilation handler, you can add new procedures to the project, or modify or delete already existing ones.</p> + <a name="OnBeforeSaveFile" /><pre class="code">function OnBeforeSaveFile() + +end</pre> + + <p>The event is invoked before all objects created during compilation are written to the output file. In the OnBeforeSaveFile event handler you can change the file and its properties (such as the list of resources, the list of exported function, section names etc.) that are automatically written to the output file.</p> + <a name="OnBeforePackFile" /><pre class="code">function OnBeforePackFile() + +end</pre> + + <p>The event is invoked before packing the protected file of the application. With OnBeforePackFile you can modify a file that is to be packed. This event is only invoked is the "Pack output file" option is enabled.</p> + <a name="OnAfterSaveFile" /><pre class="code">function OnAfterSaveFile() + +end</pre> + + <p>This event is invoked after writing all objects created during compilation to the output file. The event handler can add new data to the output file or change previously written ones.</p> + <a name="OnAfterCompilation" /><pre class="code">function OnAfterCompilation() + +end</pre> + + <p>The even is invoked after compiling all objects of the project. At this stage a user has access to the compiled project, and can perform any actions with it, like adding a digital sign (certificate).</p><br/> + <p>When writing even handlers you can create your own procedures and functions. Event names are displayed with a bold font in the script editor.</p><br /> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html>
\ No newline at end of file diff --git a/help/en/script_functions.htm b/help/en/script_functions.htm new file mode 100644 index 0000000..3d75a65 --- /dev/null +++ b/help/en/script_functions.htm @@ -0,0 +1,46 @@ +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Built-in functions</title> +</head> + +<body> + <h1>Built-in functions</h1> + + <p>Aside from class methods and properties of the script language, VMProtect offers to a user various functions to perform basic operations. There are general system functions to work with strings, dates and numbers, process the command line of an application and display messages; and specialized functions to work with the VMProtect core and watermarks:</p> + + <ul> + <li><a href="http://www.lua.org/manual/5.2/manual.html#6.4">string</a></li> + <li><a href="http://www.lua.org/manual/5.2/manual.html#6.5">table</a></li> + <li><a href="http://www.lua.org/manual/5.2/manual.html#6.6">math</a></li> + <li><a href="http://www.lua.org/manual/5.2/manual.html#6.7">bit32</a></li> + <li><a href="http://www.lua.org/manual/5.2/manual.html#6.8">io</a></li> + <li><a href="http://www.lua.org/manual/5.2/manual.html#6.9">os</a></li> + <li><a href="#VMProtect">vmprotect</a></li> + </ul> + <a name="VMProtect"></a> + <pre class="code"> +namespace vmprotect { + <a href="script_classes.htm#Core">Core</a> core(); // returns the VMProtect core + string extractFilePath(string name); // extracts the path of a file + string extractFileName(string name); // extracts the name of a file + string extractFileExt(string name); // extracts the extension of a file + table commandLine(); // returns the command line + <a href="script_classes.htm#FFILibrary">FFILibrary</a> openLib(string name); // opens a library +}; +</pre> + + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/sdk_functions.htm b/help/en/sdk_functions.htm new file mode 100644 index 0000000..2c7857e --- /dev/null +++ b/help/en/sdk_functions.htm @@ -0,0 +1,161 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>SDK functions</title> +</head> + +<body> + <h1>SDK functions</h1> + + <p>SDK functions can be integrated to the source code of the protected application to set boundaries of the protected areas, to detect debuggers or virtualization tools.</p> + + <p><strong>Code markers</strong></p> + + <ul> + <li><a href="#VMProtectBegin">VMProtectBegin</a></li> + <li><a href="#VMProtectBeginVirtualization">VMProtectBeginVirtualization</a></li> + <li><a href="#VMProtectBeginMutation">VMProtectBeginMutation</a></li> + <li><a href="#VMProtectBeginUltra">VMProtectBeginUltra</a></li> + <li><a href="#VMProtectBeginVirtualizationLockByKey">VMProtectBeginVirtualizationLockByKey</a></li> + <li><a href="#VMProtectBeginUltraLockByKey">VMProtectBeginUltraLockByKey</a></li> + <li><a href="#VMProtectEnd">VMProtectEnd</a></li> + </ul> + + <p><strong>Service functions</strong></p> + + <ul> + <li><a href="#VMProtectIsProtected">VMProtectIsProtected</a></li> + <li><a href="#VMProtectIsDebuggerPresent">VMProtectIsDebuggerPresent</a></li> + <li><a href="#VMProtectIsVirtualMachinePresent">VMProtectIsVirtualMachinePresent</a></li> + <li><a href="#VMProtectIsValidImageCRC">VMProtectIsValidImageCRC</a></li> + <li><a href="#VMProtectDecryptStringA">VMProtectDecryptStringA</a></li> + <li><a href="#VMProtectDecryptStringW">VMProtectDecryptStringW</a></li> + <li><a href="#VMProtectFreeString">VMProtectFreeString</a></li> + </ul> + + <p><strong>Licensing functions</strong></p> + + <ul> + <li><a href="manager/usage/api.htm">VMProtectSetSerialNumber</a></li> + <li><a href="manager/usage/api.htm">VMProtectGetSerialNumberState</a></li> + <li><a href="manager/usage/api.htm">VMProtectGetSerialNumberData</a></li> + <li><a href= "manager/usage/api.htm">VMProtectGetCurrentHWID</a></li> + </ul> + + <p id="VMProtectBegin"><strong>VMProtectBegin</strong></p> + <pre class="code">void VMProtectBegin(const char *MarkerName); +</pre> + + <p>The <a href="use_markers.htm">marker</a> identifying the beginning of the protected area of the code. A call to VMProtectBegin must be placed before the first command (or procedure or function call) of the protected code block. + MarkerName defines the name of the marker that looks like "VMProtectMarker"+MarkerNamе in VMProtect. For example, a marker + VMProtectBegin('CheckRegistration') will look as + VMProtectMarker "CheckRegistration". If the name of the marker is not set, it is given a unique name in the form of "VMProtectMarker"+marker_serial_number. You can set the <a href= + "project_functions.htm#CompilationTypes">compilation type</a> of the given protected block in VMProtect.</p> + + <p id="VMProtectBeginVirtualization"><strong>VMProtectBeginVirtualization</strong></p> + <pre class="code">void VMProtectBeginVirtualization(const char *MarkerName); +</pre> + + <p>The marker identifying the beginning of the protected area of the code with the predefined "virtualization" compilation type. + MarkerName defines the <a href="#VMProtectBegin">name of the marker</a>. + The compilation type of this marker cannot be changed during further work with VMProtect.</p> + + <p id="VMProtectBeginMutation"><strong>VMProtectBeginMutation</strong></p> + <pre class="code">void VMProtectBeginMutation(const char *MarkerName); +</pre> + + <p>The marker identifying the beginning of the protected area of the code with the predefined "mutation" compilation type. MarkerName defines the <a href="#VMProtectBegin">name of the marker</a>. + The compilation type of this marker cannot be changed during further work with VMProtect.</p> + + <p id="VMProtectBeginUltra"><strong>VMProtectBeginUltra</strong></p> + <pre class="code">void VMProtectBeginUltra(const char *MarkerName); +</pre> + + <p>The marker identifying the beginning of the protected area of the code with the predefined "ultra (virtualization+mutation)" compilation type. MarkerName defines the <a href="#VMProtectBegin">name of the marker</a>. The compilation type of this marker cannot be changed during further work with VMProtect.</p> + + <p id="VMProtectBeginVirtualizationLockByKey"><strong>VMProtectBeginVirtualizationByKey</strong></p> + <pre class="code">void VMProtectBeginVirtualizationLockByKey(const char *MarkerName); +</pre> + + <p>The marker identifying the beginning of the protected area of the code with the predefined "virtualization" compilation type and the enabled <a href= + "project_functions.htm#LockToKey">"Lock to key"</a> option. + MarkerName defines the <a href="#VMProtectBegin">name of the marker</a>. The compilation type of this marker cannot be changed during further work with VMProtect.</p> + + <p id="VMProtectBeginUltraLockByKey"><strong>VMProtectBeginUltraLockByKey</strong></p> + <pre class="code">void VMProtectBeginUltraLockByKey(const char *MarkerName); +</pre> + + <p>The marker identifying the beginning of the protected area of the code with the predefined "ultra (virtualization+mutation)" compilation type and the enabled <a href= + "project_functions.htm#LockToKey">"Lock to key"</a> option. MarkerName defines the <a href="#VMProtectBegin">name of the marker</a>. The compilation type of this marker cannot be changed during further work with VMProtect.</p> + + <p id="VMProtectEnd"><strong>VMProtectEnd</strong></p> + <pre class="code">void VMProtectEnd(void); +</pre> + + <p>The marker identifying the end of the protected area of the code. The call to VMProtectEnd must be placed after the last command (procedure or function call) of the protected code block.</p> + + <p id="VMProtectIsProtected"><strong>VMProtectIsProtected</strong></p> + <pre class="code">bool VMProtectIsProtected(void); +</pre> + + <p>The VMProtectIsProtected function returns True if the file is processed by VMProtect.</p> + + <p id="VMProtectIsDebuggerPresent"><strong>VMProtectIsDebuggerPresent</strong></p> + <pre class="code">bool VMProtectIsDebuggerPresent(bool CheckKernelMode); +</pre> + + <p>The VMProtectIsDebuggerPresent function allows to detect the launch of the application under a debugger. The result + (True/False) can be processed with in-app protection mechanisms. If CheckKernelMode=False the function checks for User-mode debuggers (OllyDBG, WinDBG etc.). If CheckKernelMode=True, both User-mode and Kernel-mode debuggers (SoftICE, + Syser etc.). When protecting drivers, the value of CheckKernelMode does not make sense, because drivers always work in the kernel mode, so presence of kernel-mode debugger is always checked.</p> + + <p id="VMProtectIsVirtualMachinePresent"><strong>VMProtectIsVirtualMachinePresent</strong></p> + <pre class="code">bool VMProtectIsVirtualMachinePresent(void); +</pre> + + <p>The VMProtectIsVirtualMachinePresent function allows to detect the launch of the application under a virtual machine tool: VMware, Virtual PC, + VirtualBox, Sandboxie. The result + (True/False) can be processed with in-app protection mechanisms.</p> + + <p id="VMProtectIsValidImageCRC"><strong>VMProtectIsValidImageCRC</strong></p> + <pre class="code">bool VMProtectIsValidImageCRC(void); +</pre> + + <p>The VMProtectIsValidImageCRC function detects the fact that the executable module has been changed in the memory of the process (only unchangeable segments of code and data are checked). The result + (True/False) can be processed with in-app protection mechanisms.</p> + + <p id="VMProtectDecryptStringA"><strong>VMProtectDecryptStringA</strong></p> + <pre class="code">const char * VMProtectDecryptStringA(const char *Value); +</pre> + + <p>The VMProtectDecryptStringA function decrypts the ANSI string constant - Value. To decrypt the constant, you must <a href="project_functions.htm#AddFunction">include it to the list of protected objects + </a>.</p> + + <p id="VMProtectDecryptStringW"><strong>VMProtectDecryptStringW</strong></p> + <pre class="code">const wchar_t * VMProtectDecryptStringW(const wchar_t *Value); +</pre> + + <p>The VMProtectDecryptStringW function decrypts the Unicode string constant - Value. To decrypt the constant, you must <a href="project_functions.htm#AddFunction">include it to the list of protected objects</a>.</p> + + <p id="VMProtectFreeString"><strong>VMProtectFreeString</strong></p> + <pre class="code">bool VMProtectFreeString(const void *Value); +</pre> + + <p>The VMProtectFreeString function frees dynamic memory allocated for the decrypted string. It is not necessary to free up memory, but if you do this - you must use this function. + If VMProtectDecryptStringA/VMProtectDecryptStringW are used with the same parameters for the second time without destroying previously decrypted string, additional memory is not allocated.</p><br /> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/software_protection.htm b/help/en/software_protection.htm new file mode 100644 index 0000000..20a5640 --- /dev/null +++ b/help/en/software_protection.htm @@ -0,0 +1,52 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Analysis, cracking and protection of software</title> +</head> + +<body> + <h1>Analysis, cracking and protection of software</h1> + + <p>A software product can be analyzed by means of static or dynamic analysis. Static analysis means protection cracking algorithm is based on disassembly results analysis or on decompiling of the protected application. Dynamic analysis is required to crack encrypted or dynamically changing executables, because static analysis of such programs proved to be difficult.</p> + + <p>For dynamic analysis, the program being cracked is executed in a debugger framework. This way, everything that happens during operation of the program can be controlled by the debugger. During dynamic analysis, a cracker uses the debug mode to bypass all protection algorithms of the program one by one, in particular registration key generation and check procedures. Another tool dynamic analysis often use is tracking of files, system services, ports and external devices the cracked program queries.</p> + + <p>The main instruments to protect applications from cracking attempts are <a href= + "dictionary.htm#Protector">software protectors</a>. Protection most of protectors provide is based on + <a href="dictionary.htm#Pack">packing</a> and/or <a href= + "dictionary.htm#Crypt">encryption</a> of the original executable with great focus put on protecting unpacking/decryption procedures.</p> + + <p>Such an algorithm is often insufficient to provide reliable protection. If an application is protected by packing, a hacker can easily obtain the original unpacked file as soon as he makes the memory dump right after the unpacker finishes its work. Moreover, there are multiple automated tools to crack the most popular protectors. The same is true for encryption: after obtaining a proper license key (often purchased legally), a cracker can decrypt protected parts of the code.</p> + + <p>Some software protectors use a number of anti-debug techniques. However, each one of them significantly influences the performance of the protected program. Also, anti-debug methods are only effective against dynamic analysis and are completely inefficient against static analysis. Even more, all anti-debug methods modern protectors use are well-known and studied, and crackers have programmed many utilities to avoid or bypass them. Activity monitors are not affected by the built-in anti-debug protection at all.</p> + + <p>More efficient ways to protect an application are + <a href="dictionary.htm#Obfuscation">obfuscation</a> and <a href= + "dictionary.htm#Virtualization">virtualization</a> that complicate analysis of the protected application's code. Generally, high efficiency of these protection method is based on the human factor: the more complex the code is and the more resources the application uses, the harder it is for a cracker to understand program logic and, consequently, to crack protection.</p> + + <p>Obfuscation "entangles" the code of an application by adding excessive instructions to it. Virtualization transforms the source code to the <a href= + "dictionary.htm#ByteCode">bytecode</a> executed by a special interpreter that imitates a virtual machine with a specific set of commands. + Therefore, virtualization leads to high and irreducible level of complexity of the resulting code, and if applied properly, the code protected with such a method does not contain methods to restore the original code explicitly. + So, the main advantage of virtualization is that a virtualized fragment of the code doesn't transform to machine language commands during execution, and this in turn prevents obtaining of the original code of the application by a cracker.</p> + + <p>Reverse engineering of virtualized fragments is reduced to analysis of the architecture of a <a href= + "dictionary.htm#VirtualMachine">virtual machine</a>, building a disassembler for the corresponding architecture of a processor imitated by the virtual machine, and analysis of the disassembled code. A properly implemented virtual machine makes creating a disassembler for it quite a difficult task. The only disadvantage of virtualization is relatively low execution speed, so this method should only be applied to parts of the code that are non-critical to execution speed.</p> + + <p>Most of today's protectors do not put much attention to obfuscation and virtualization, or their implementation is poor. This allows crackers to remove such protection in automatic or semi-automatic mode. Another bottleneck of modern protectors is use of undocumented Windows functions, which leads to limited operation of the protected application in newer versions of the OS, or if DEP is enabled.</p><br /> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/terms.htm b/help/en/terms.htm new file mode 100644 index 0000000..4f039c2 --- /dev/null +++ b/help/en/terms.htm @@ -0,0 +1,56 @@ +<?xml version="1.0" encoding="utf-8"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" + "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + <meta name="AppleIcon" content="VMProtect.help/logo.png" /> + <meta name="AppleTitle" content="VMProtect 3.0 Help" /> + + <title>Introduction</title> + <style type="text/css"> +/*<![CDATA[*/ + div.c2 {align:center} + hr.c1 {height:1px;border-width:0;color:gray;background-color:gray} + /*]]>*/ + </style> +</head> + +<body> + <h1>Introduction</h1> + + <p>There is no an ideal way to protect software from unauthorized use and distribution. No existing systems can provide absolute security and prevent a potential hacker from neutralizing it. However, using quality and efficient protection can make cracking of software extremely difficult up to complete inadvisability in terms of time and efforts put into breaking the protection. While software protection can pursue different goals, the basis of any protection system is securing the application from analysis, because it is resistance to reverse engineering that shapes overall efficiency of the protection system.</p> + + <ul> + <li><a href="dictionary.htm">Glossary</a></li> + + <li><a href="software_protection.htm">Analysis, cracking and protection of software</a></li> + + <li><a href="about_vmprotect.htm">What is + VMProtect?</a></li> + + <li><a href="recommendations.htm">Recommendations on protecting your application</a></li> + </ul> + + <div class=unhide_if_no_site style="visibility:hidden"> + <h2>See also</h2> + + <ul> + <li><a href="http://vmpsoft.com/support/user-manual-v3/">The latest version of this manual on our website</a></li> + </ul> + </div> + + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/toolbar.htm b/help/en/toolbar.htm new file mode 100644 index 0000000..863c236 --- /dev/null +++ b/help/en/toolbar.htm @@ -0,0 +1,39 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Toolbar</title> + <style type="text/css"> + </style> +</head> + +<body> + <h1>Toolbar</h1> + + <p>The toolbar consists of the following elements:</p> + + <ul> + <li>Open a project or a protected file: <img src="images/button_open.png" /></li> + <li>Save the project: <img src="images/button_save.png" /></li> + <li>Name of the protected file: <br /> <img src="images/button_project.png" /></li> + <li>Compile the project: <img src="images/button_compilation.png" /></li> + <li>Execute the original/protected file (pressing the down arrow allows to specify command line parameters): <img src="images/button_execute.png" /></li> + <li>Default action (depends on the selected section): <br /><img src="images/button_action.png" /></li> + <li>Quick search box: <br /><img src="images/button_search.png" /></li> + </ul> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/use_map_file.htm b/help/en/use_map_file.htm new file mode 100644 index 0000000..cb9e1dd --- /dev/null +++ b/help/en/use_map_file.htm @@ -0,0 +1,45 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Using a MAP-file</title> + <style type="text/css"> + </style> +</head> + +<body> + <h1>Using a MAP-file</h1> + + <p>To create a MAP-file you should enable the corresponding option in the compiler settings.</p> + + <h3>Visual Studio</h3> + + <p>If you develop your application in Visual Studio, this can be done as follows: in the main menu of the IDE, open the project properties (Project - Properties), then on the "Linker - Debugging" tab set the + "Generate MAP File" option to "Yes (/MAP)":</p> + <p><img src="images/visual_studio_map.png" /></p> + + <h3>Borland Delphi</h3> + + <p>If you develop the application using Borland Delphi, + the same can be done as follows: in the main menu of the Delphi IDE open the project options(Project - Options) and on the "Linker" tab set the "MAP file" section option to "Detailed":</p> + <p><img src="images/delphi_map.png" /></p> + + <p>After you enabled MAP-file generation, the project must be rebuilt.</p> + + <p>Upon loading of a MAP-file VMProtect compares modification date and time of the MAP-file and those of the protected file. If they are different, the MAP-file is not loaded.</p><br /> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/use_markers.htm b/help/en/use_markers.htm new file mode 100644 index 0000000..cacca98 --- /dev/null +++ b/help/en/use_markers.htm @@ -0,0 +1,94 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Using markers</title> + <style type="text/css"> +/*<![CDATA[*/ + div.c2 {text-align: center} + /*]]>*/ + </style> +</head> + +<body> + <h1>Using markers</h1> + + <p>To protect individual fragments of the code and to protect string constants, you can insert special markers to the source code of your application. Markers are calls to functions imported from the external library (32-bit applications use + VMProtectSDK32.dll, and 64-bit applications use VMProtectSDK64.dll; drivers use VMProtectDDK32.sys and + VMProtectDDK64.sys respectively) - further referred to as + VMProtectSDK. Procedures and functions in VMProtectSDK do not perform any actions and are merely labels VMProtect uses to determine boundaries of the protected code. The beginning and the end of the protected block are marked as follows:</p> + + <ul> + <li><strong>Delphi</strong> + <pre class="code">uses VMProtectSDK; + +VMProtectBegin(MARKER_TITLE); +... +VMProtectEnd; +</pre> + </li> + + <li><strong>C/C++</strong> + <pre class="code">#include "VMProtectSDK.h" + +VMProtectBegin(MARKER_TITLE); +... +VMProtectEnd(); +</pre> + </li> + + <li><strong>MASM</strong> + <pre class="code">include VMProtectSDK.inc + +invoke VMProtectBegin,SADD(MARKER_TITLE) +... +invoke VMProtectEnd +</pre> + </li> + + <li><strong>Visual Basic</strong> + <pre class="code">VMProtectBegin (StrPtr(MARKER_TITLE)) +... +VMProtectEnd +</pre> + </li> + </ul> + + <p>Also, instead of VMProtectBegin you can use markers with the predefined <a href= + "project_functions.htm#CompilationTypes">compilation types</a>:</p> + + <ul> + <li>VMProtectBeginVirtualization - the marker uses the "Virtualization" compilation type.</li> + + <li>VMProtectBeginMutation - the marker uses the "Mutation" compilation type.</li> + + <li>VMProtectBeginUltra - the marker uses the "Ultra" compilation type.</li> + </ul> + + <p>Markers are processed as follows: when VMProtect analyzes the code of the protected application, it locates all calls to + VMProtectSDK procedures and functions. Boundaries of blocks to protect are defined by marker pairs + VMProtectBegin/VMProtectBeginVirtualization/VMProtectBeginMutation/VMProtectBeginUltra + and VMProtectEnd. Then, when VMProtect processes the code of the protected application, it removes both the markers and any mentions of the VMProtectSDK, so there is no need to include these libraries to your setup package. Markers are removed regardless of whether they are included to compilation or not. When named markers are used, their names are also removed.</p> + + <p>If a title for the marker is specified, it is assigned with the name like + "VMProtectMarker MARKER_TITLE". If a title of the marker is not specified, it is assigned with a unique name: + "VMProtectMarker"+marker serial number. However, using non-named markers has a significant disadvantage: if a new marker will be inserted to the code of the program, numeration of all non-named markers will change. So we recommend to always use named markers.</p> + + <p>A particularly important thing to consider when working with markers is that you shouldn't allow jumps from non-protected areas inside the marker. This can happen, for example, if you enclose a part of a cycle in markers. If the application that uses markers becomes non-functional after protection, you can detect jumps from non-protected areas and addresses by enabling the "Debug mode" option. In this mode, when the protected application works under the debugger, the latter will interrupt execution of the program if a jump from a non-protected area into the protected debugger is detected. When all such jumps are found, you should either change placement of the markers, or if this is impossible, mark those addresses as external using the GUI version of VMProtect.</p> + + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/watermarks.htm b/help/en/watermarks.htm new file mode 100644 index 0000000..df7d2bf --- /dev/null +++ b/help/en/watermarks.htm @@ -0,0 +1,38 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Watermarks</title> + <style type="text/css"> + </style> +</head> + +<body> + <h1>Watermarks</h1> + + <p>VMProtect offers a unique ability to add hidden information about the owner of the protected file to this file. A watermark is an array of bytes that should be unique to each user. If watermarks are incorporated to the protected file, you can always determine the owner of the leaked copy (for instance, if the cracked program is distributed) and act accordingly. The watermark database file is stored in "%ApplicationData%/VMProtect Software/VMProtect.dat" + for Windows and in "/Users/Shared/VMProtect Software/VMProtect.dat" + for Mac OS X.</p> + + <p>The "Watermarks" dialog window contains two tabs:</p> + + <ul> + <li><a href="watermarks_setup.htm">Setup</a></li> + <li><a href="watermarks_search.htm">Search</a></li> + </ul><br /> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/watermarks_search.htm b/help/en/watermarks_search.htm new file mode 100644 index 0000000..494ec8b --- /dev/null +++ b/help/en/watermarks_search.htm @@ -0,0 +1,47 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Searching for watermarks</title> + <style type="text/css"> + </style> +</head> + +<body> + <h1>Searching for watermarks</h1> + + <p>The "Search" tab of the watermark dialog allows you to locate watermarks in an executable or a specified process of the protected application:</p> + <p><img src="images/watermarks_search.png" /></p> + + <ul> + <li><strong>Search in file</strong> - look for watermarks in the application executable. Select a file in the "File Name" field where you want to look for watermarks in;</li> + + <li><strong>Search in module</strong> - search in a module of the selected process. Select a running process in the drop-down list, then select a module of this process to search watermarks in.</li> + </ul> + + <p>Results of the search are displayed in the list below:</p> + + <ul> + <li><strong>Name</strong> - the name of the found watermark;</li> + + <li><strong>Count</strong> - the number of copies of the found watermark.</li> + </ul> + + <p><strong>Important:</strong><br /> + When you search for watermarks in an unpacked executable, any of this modes will do. However, if an executable is <a href="dictionary.htm#Pack">packed</a>, you should search for watermarks in the running application only (the "Search in module" mode). Searching in the executable in this case is useless as watermarks (as well as the code and data) are packed and are only unpacked when the application is running.</p><br /> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> diff --git a/help/en/watermarks_setup.htm b/help/en/watermarks_setup.htm new file mode 100644 index 0000000..44b609a --- /dev/null +++ b/help/en/watermarks_setup.htm @@ -0,0 +1,41 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Watermark setup</title> + <style type="text/css"> + </style> +</head> + +<body> + <h1>Watermark setup</h1> + + <p>The "Setup" tab of the "Watermarks" dialog is for managing watermarks:</p> + <p><img src="images/watermarks_setup.png" alt="Configuring watermarks" /></p> + + <p>To add a new watermark, click the corresponding button. The following dialog will open:</p> + <p><img src="images/watermarks_add.png" alt="Add a watermark" /></p> + + <ul> + <li><strong>Name</strong> - the name of the watermark;</li> + + <li><strong>Value</strong> - the value of the watermark. You can generate a random value for the watermark by clicking the "Generate" button. The "Value" field consists of two columns: the left column allows entering a Hex value, the right column - a symbolic value. When the watermark is inserted to the protected file, each "?" symbol is replaced with a random value.</li> + </ul> + <p>To remove or rename a watermark, use the right-click menu:</p> + <p><img src="images/watermarks_menu.png" alt="Watermark menu" /></p> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html>
\ No newline at end of file diff --git a/help/en/work.htm b/help/en/work.htm new file mode 100644 index 0000000..53bbe25 --- /dev/null +++ b/help/en/work.htm @@ -0,0 +1,35 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + <link rel="Stylesheet" type="text/css" href="default.css" /> + <meta http-equiv="Content-Type" content= + "text/html; charset=utf-8" /> + + <title>Working with VMProtect</title> + <style type="text/css"> + </style> +</head> + +<body> + <h1>Working with VMProtect</h1> + + <p>Before you start working with VMProtect, please take a look at the following sections of the manual:</p> + + <ul> + <li><a href="create_project.htm">Project setup</a></li> + <li><a href="main_window.htm">Main window</a></li> + <li><a href="mode_console.htm">Console version</a></li> + </ul><br /> + <br /> + <br /> + <br /> + <br /> + <hr noshade="noshade" size="1" /> + + <div align="center"> + © 2006-2015 Copyright VMProtect Software + </div> +</body> +</html> |
