处理PB编译后的pbd,exe,dll文件。

pbobfuscator v2010.05.4 (Powerbuilder-pbd text to remove confusion with the code encryption device) build 2010-05-27, 00:52:29 size: 5.61 MB (5,892,608 bytes) Contact: blog: http://blog.csdn.net/chengg0769 download: http://www.newhua.com/soft/15463.htm (onlinedown) http://chengg0769.download.csdn.net (csdn) email: chengang0769@gmail.com Support version: pkb2.5 pb5, 6,7,8,9,10,10.5,11,11.5,12 The version is pbvm.dll's version, such as pbvm115.dll. Not the version of development tools. Because multiple minor versions of a vm. Powerbuilder5-12 code for the confusion and encryption. Since the beginning of 2009.6 pbd file format. Over the same period began developing anti-compiler is now ripe, because there are some concerns (did not know how to authorize and to require that only authorized users), So yet released. 2010.3 months of PowerShield1.0 simple version of the successful anti-aliasing (estimate is a simple version of the reason, otherwise I would not sigh too easy for anti-aliasing) is also the author mentioned PowerShield1.0 simple version could leave the back door, and the safety factor is not high. PowerShield a bit like a three-Village of the Family in the poplar, a program once the testing of different encryption Strength, its turning logo clearly visible. If you set a check in the analysis stack, and fit the law of false jump can anti-aliasing. Particularly in areas with the line between branches is an important skill within, can be the perfect anti-aliasing. I can see the specific text describing the blog. Part of the code which confused the thinking of PowerShield1.0 reference LJTT simple version, to express admiration and gratitude. In view of the following procedures pbkiller on pb9 cause great harm, Not that pbkiller what's wrong, the key is that it is authorized to flooding. So also gave high attention and time to find ways to increase the confusion in the restraint. And kivens expressed admiration. As long as the use of Confusion over device, pbkiller should not work. There he longlong types do not support, on the unicode version does not support basic sound, not because of specific development. I would also like to pb kill off They do? Features: 1. Modify some of the key parameters of the early induction of some anti-compiler crash. No one safeguard against the compiler let him out of applications to break it. The project to restore, if it is another. 2. Code to confuse the part of the principle of reference LJTT the PowerShield1.0 simple version, based on its expansion in some new way. Also some things in mind, yet to achieve. 2.1 by adding random variation factor, which makes the algorithms more difficult against confusion; 2.2 increase in deception and logic traps, these traps can be analyzed by the human eye and discovery, but because the human brain is the logical thinking ability, and rely on programming to understand I can not fake fake code logical. So that it will fall into the trap of my default logic. After Beta will expand: 2.3 based on the current work (9) increased to 36 species (or 100 species) confusion about methods and limits in the single way to test all confused, so anti-development because of the compiler can not Testing to all possibilities, thereby increasing the difficulty of anti-aliasing. Most important thing is intermixed with the code appears to leave the normal jump, (including the direct participation of the local variable expression false, makes it difficult to distinguish the authenticity of) similar to Nature, the more is not always easy to determine, leading anti-aliasing can not be identified using the procedures summarized. 2.4 confusion before, view the variable list has a number of available variables, such as int, long type, can be forged fake code and add the real code comes with the mixed, or real code Package with the formation of mixed higher similarity. 2.5 will be a variety of ways in a number of discrete release. So that a loss against the compiler. Discrete but also by the machine characteristics, time, version, license type and so on. Spread as far as possible. 2.6 Other dynamic languages not to confuse the reference device, as would like to have basically realized. java, c #, etc. Obfuscator should have been very mature, and can learn from. 2.7 will also be forged more data segments. One advantage of forging is that first you want to decompile to straighten out and return home to the false front. This bit difficult. Another axiom is: pb implementation is dynamic, He will be used to call and call memory. The forged will not be called. But, but, against the compiler does not know, so any stuff will go Pidianpidian analysis. 2.8 The equivalent figures and text replacement, to prevent the pj to directly search for sensitive locations. 2.9 Taking into account the length of my realization subject to the code, the code can be used too few factors such as different versions, the programmer can think of aside trap flag (Obfuscator behalf disturb), programmers write the code on the initiative Defense, then the confusion after the doubtful authenticity, blurring better and better hidden traps. 3. Erase all the unnecessary visible text, such as RefListObject text, var variable names, function names and parameters of the text. The case against the compiler can only rename and thus can not restore readability. Code function Note reading is not the case in a large extent, dependent variable names, function names. We are all programmers understand about the truth. For function and time may be the global call or dynamic calls (written in quotes), so The current functions and events on the name yet to take measures. Treatment should also be quite troublesome. 4. Increased the deception object or function. Although the repeated use of this software debugging, anti-aliasing device can be found on the law, but because the object with a random factor to deceive, in the absence of reference material circumstances, to verify an Completeness and correctness, as the format, yet people have the ability now. Unless it is to use assertions everywhere sooner or difficult to determine. As with visual identification of a bottle of purified water and a bottle of gasoline that. Anti-aliasing device will not care depression Into one. 5. Increase the false object functions within the function or event. Having regard to the anti-compiler compilation will provide a single point of anti-debugging switch, so as far as possible to the individual pbd file, each object, each function event, each code may Appears to prevent anti-effective means of compiler. If you can easily bypass it Qibushibai take. The 2.9 is living in this consideration. In addition to anti-aliasing and anti-compiler developers, some ordinary people to use anti-compiler compiler does not know why the anti-abnormal way out, because they have no anti-compiler source code, can not single-step debugging. Such a situation they can not do anything (to this effect is). Anti-compiler developers will not go for an uncertain law and modify the program. 6. For some non-essential, but the visual format of the pbd help in the analysis of places give all erased, so as to increase the illusion of a sense of artificial eyes. My principle is to erase all the bytes can be erased, disrupting everything can disrupt Bytes. Determine the format of the current basic framework of analysis and error-free. But the code table is still not complete (as of 2010.5.12 were less than 30), if the test to an error (unknown pcode), please advise. Note, however, please use the full compile the program testing, do not use that compiler error, or compiled into the pbd half to test abnormal exit, which is itself a problem (which the compiler development time in the anti-met) There are kinds of errors such as t