First, we take a look at the anti-encryption Java programs, which is what is commonly known as Crack process, only to understand this process, we can effectively on our procedures for encryption. Usually, we get Java programs Crack-there are two kinds of KeyGen (registration code generator), a revision of replacement we look at the first one, when we find an application of the time, we always KeyGen KeyGen admire that made people think he was very powerful, but you carefully analyze why he can make KeyGen? He was the only one on the Java programming encryption algorithms to understand the very clear that such a person what? One is that the people inside the company is unlikely, unless conflicts, and also, that is conjecture, and anti-putt this possible? Oh, we can not, then the algorithm come from? Oh, often leaking secret secret is itself…… back and think, Java applications know how you enter the registration code is correct? Oh, you start from the application on the…… get its encryption algorithm, natural KeyGen kinds…… (but this is also out, if it is used for public key encryption key secret, there is no approach is hidden behind can only use the second method.) to deal with this approach as long as only suitable for a registered, not the other anything, classic representative Borland JBuilder & Optimizeit Suite look at the second, why should replace amended? We amended the part? Not think that is definitely part of License proven, why do we not find the above methods as encryption algorithm? There are two reasons: (1) Use of the above approach Gaobuding (2) Java programs not only to Key, there are other License configuration; encountered such a situation, if we find a test for the Class License, revise replacement on the trip. Such an approach used in any circumstances, a classic representative of BEA WebLogic above analysis, we concentrated on the issue, the key is how to find License certification for some or part of the encryption algorithm, we need three tools: One is the Sun's The standard JVM:), one of your patience and carefully:), one Jad (classic anti-Java compiler tools). The first step is positioning, this is the most crucial step, we here to Together For JBuilder Edition example, start Together, the first look at look like son? Oh, I would like to ask of License; Ok, every relationship from; find the start-up Bat Together document, it found the command: java ....., OK, in Java to a start time parameters: "-Xrunhprof : cpu = times ", preservation, in the start, we must still License, from that time, we can be found in this directory more than a" java.hprof.txt "documents, an open, I want the JVM Dump documents, many content ah, okay, it slowly. We can see this document there are many familiar things ah: java .* / com.sun .* / javax .* etc., but this is not our concern, we would like to have is some com.togethersoft .* or no packet zd.d name, and so on. (1 inserted here, and almost all the Java application will be confusion, in fact, the confusion is also very simple principle, we say behind.) To the room and have the License, a Serach, Hei hei, Sure enough, the 474 line: com.togethersoft. together.impl.ide.license.LicenseSetup.execute ([DashoPro-V2-050200]: Unknown line), Ok, Nadui classpath in the Jar packets inside to find it (recommended by WinRAR), found after anti-compiler with Jad , a look at, not to confuse this, but with a zae the class that read the names on that confusion, first ignored it, then look at the following sentence IdeLicenseAccess.setLicense (zae1), then find IdeLicenseAccess Ok, You, This repertoire, all the License certification are taking this category, object-oriented thinking good, huh:) positioning for the end, the next thing is to amend the method by guess these two categories, shielding inside execute method swap LicenseSetup the actual contents of IdeLicenseAccess amended, to allow some have returned to the true test, and then compiled to replace; not happy too early, this has not End, it must be a sense of responsibility! ! Together started, as expected, not to this License, and launched a picture into account, but a grey matter how a look at the console, a pile of wrong, okay, not frightened mistakes, find the root causes, there is a category IdeLicenseUtil a problem, then the anti-compiler, modification, replacement; get under this. Restart, test, OK. In this way, a Java application to get. Look at the fact is very simple. And then talk about confusion, we may all know that the confusion has not been the Java compiler Class-back methods and even the names of variables do not change, this is what reasons? This can be traced to the structure of the document Class, simple, Class of documents also includes a constant pool (constant pool) deposited on the inside of the variables and methods and the names of Hold Class related things, we usually refer to the confusion is a tool used to the constant pool inside the Hutu NEE Lane, in this way we can fool the anti-compiler and you, huh:) This is why sometimes anti-compiler compiler things do not come back for the past. Come back, said Java programs encryption; from the above two methods, Java programs seems to be no perfect solution for encryption, on the contrary, we must be guided by certain principles, to be effective the protection of your product. A principle, as far as possible the use of public key and secret key to encrypt; two principles, not to use encryption certification part of the object-oriented thinking:) of the proven methods in the process of writing every corner, and mark as private final void, Compiler for you within 10% of the processing methods; three principles, as far as possible, a substantial confusion:) find a good point of confusion;
First, we take a look at the anti-encryption Java programs, which is what is commonly known as Crack process, only to understand this process, we can effectively on our procedures for encryption. Usually, we get Java programs Crack-there are two kinds of KeyGen (registration code generator), a revision of replacement we look at the first one, when we find an application of the time, we always KeyGen KeyGen admire that made people think he was very powerful, but you carefully analyze why he can make KeyGen? He was the only one on the Java programming encryption algorithms to understand the very clear that such a person what? One is that the people inside the company is unlikely, unless conflicts, and also, that is conjecture, and anti-putt this possible? Oh, we can not, then the algorithm come from? Oh, often leaking secret secret is itself…… back and think, Java applications know how you enter the registration code is correct? Oh, you start from the application on the…… get its encryption algorithm, natural KeyGen kinds…… (but this is also out, if it is used for public key encryption key secret, there is no approach is hidden behind can only use the second method.) to deal with this approach as long as only suitable for a registered, not the other anything, classic representative Borland JBuilder & Optimizeit Suite look at the second, why should replace amended? We amended the part? Not think that is definitely part of License proven, why do we not find the above methods as encryption algorithm? There are two reasons: (1) Use of the above approach Gaobuding (2) Java programs not only to Key, there are other License configuration; encountered such a situation, if we find a test for the Class License, revise replacement on the trip. Such an approach used in any circumstances, a classic representative of BEA WebLogic above analysis, we concentrated on the issue, the key is how to find License certification for some or part of the encryption algorithm, we need three tools: One is the Sun's The standard JVM:), one of your patience and carefully:), one Jad (classic anti-Java compiler tools). The first step is positioning, this is the most crucial step, we here to Together For JBuilder Edition example, start Together, the first look at look like son? Oh, I would like to ask of License; Ok, every relationship from; find the start-up Bat Together document, it found the command: java ....., OK, in Java to a start time parameters: "-Xrunhprof : cpu = times ", preservation, in the start, we must still License, from that time, we can be found in this directory more than a" java.hprof.txt "documents, an open, I want the JVM Dump documents, many content ah, okay, it slowly. We can see this document there are many familiar things ah: java .* / com.sun .* / javax .* etc., but this is not our concern, we would like to have is some com.togethersoft .* or no packet zd.d name, and so on. (1 inserted here, and almost all the Java application will be confusion, in fact, the confusion is also very simple principle, we say behind.) To the room and have the License, a Serach, Hei hei, Sure enough, the 474 line: com.togethersoft. together.impl.ide.license.LicenseSetup.execute ([DashoPro-V2-050200]: Unknown line), Ok, Nadui classpath in the Jar packets inside to find it (recommended by WinRAR), found after anti-compiler with Jad , a look at, not to confuse this, but with a zae the class that read the names on that confusion, first ignored it, then look at the following sentence IdeLicenseAccess.setLicense (zae1), then find IdeLicenseAccess Ok, You, This repertoire, all the License certification are taking this category, object-oriented thinking good, huh:) positioning for the end, the next thing is to amend the method by guess these two categories, shielding inside execute method swap LicenseSetup the actual contents of IdeLicenseAccess amended, to allow some have returned to the true test, and then compiled to replace; not happy too early, this has not End, it must be a sense of responsibility! ! Together started, as expected, not to this License, and launched a picture into account, but a grey matter how a look at the console, a pile of wrong, okay, not frightened mistakes, find the root causes, there is a category IdeLicenseUtil a problem, then the anti-compiler, modification, replacement; get under this. Restart, test, OK. In this way, a Java application to get. Look at the fact is very simple. And then talk about confusion, we may all know that the confusion has not been the Java compiler Class-back methods and even the names of variables do not change, this is what reasons? This can be traced to the structure of the document Class, simple, Class of documents also includes a constant pool (constant pool) deposited on the inside of the variables and methods and the names of Hold Class related things, we usually refer to the confusion is a tool used to the constant pool inside the Hutu NEE Lane, in this way we can fool the anti-compiler and you, huh:) This is why sometimes anti-compiler compiler things do not come back for the past. Come back, said Java programs encryption; from the above two methods, Java programs seems to be no perfect solution for encryption, on the contrary, we must be guided by certain principles, to be effective the protection of your product. A principle, as far as possible the use of public key and secret key to encrypt; two principles, not to use encryption certification part of the object-oriented thinking:) of the proven methods in the process of writing every corner, and mark as private final void, Compiler for you within 10% of the processing methods; three principles, as far as possible, a substantial confusion:) find a good point of confusion; |
