WO2019062015A1 - Procédé de protection de code source, serveur d'application et support d'informations lisible par ordinateur - Google Patents

Procédé de protection de code source, serveur d'application et support d'informations lisible par ordinateur Download PDF

Info

Publication number
WO2019062015A1
WO2019062015A1 PCT/CN2018/077642 CN2018077642W WO2019062015A1 WO 2019062015 A1 WO2019062015 A1 WO 2019062015A1 CN 2018077642 W CN2018077642 W CN 2018077642W WO 2019062015 A1 WO2019062015 A1 WO 2019062015A1
Authority
WO
WIPO (PCT)
Prior art keywords
jdk
program
code
file
encrypted file
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2018/077642
Other languages
English (en)
Chinese (zh)
Inventor
熊星
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ping An Technology Shenzhen Co Ltd
Original Assignee
Ping An Technology Shenzhen Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ping An Technology Shenzhen Co Ltd filed Critical Ping An Technology Shenzhen Co Ltd
Publication of WO2019062015A1 publication Critical patent/WO2019062015A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
    • G06F21/12—Protecting executable software
    • G06F21/14—Protecting executable software against software analysis or reverse engineering, e.g. by obfuscation

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a source code protection method, an application server, and a computer readable storage medium.
  • the Java language is cross-platform because the Java source code is translated into a class file by the compiler, and the class file is stored as intermediate code in a platform-independent format.
  • One disadvantage of class files is that you can use the disassembler in the JDK to disassemble the class files, and then use the decompiler to decompile the disassembled results to get the source code for the class. This is very disadvantageous for programmers who need to prevent Java source code from being plagiarized or attacked.
  • the existing methods for class file protection mainly include the following: bytecode obfuscation technology, loader encryption technology, local compilation technology, and bytecode watermarking technology.
  • the bytecode obfuscation technique uses the obfuscator tool to prevent the compilation of the decompiler.
  • the purpose is to make it difficult for the decompiler to understand the class program, so that reverse engineering will take more time and effort to translate the class file, most of the obfuscators.
  • the tool scrambles the identifier in the bytecode file, and a meaningful name is replaced with a sequence or randomly generated meaningless name.
  • this technology only achieves the ambiguity on the surface, but its internal business logic remains unchanged. If the cracker has patience, it can still be broken.
  • the loader encryption technology first encrypts the class file with a certain encryption algorithm, then transfers the file to the destination host, and then loads and parses the encrypted class file with a specific custom class loader. But because the class loader itself is written in java, it can't be encrypted by itself, so others can easily get your decryption method by decompiling your class loader.
  • Local compilation technology refers to the process of compiling a Java application to a local application, converting the text code program to a local binary file, which not only improves the running speed of the program, occupies less memory, but also makes the security reach the local executable application. Degree. But this technique makes the application lose its cross-platform features and is not suitable for large applications due to the immature native compiler.
  • Bytecode watermarking technology like embedding watermarks in picture sounds, can also embed transparent, secure, and robust information in Java programs, providing valid evidence for confirming whether certain programs are plagiarized, but not Prevent class files from being reused or decompiled.
  • the present application proposes a source code protection method and an application server, which effectively prevents the source file from being decompiled, ensures the security of the source file, and maintains the cross-platform characteristics of the program, thereby improving the user experience.
  • the present application provides an application server including a memory, a processor, and a source code protection program stored on the memory and executable on the processor, the source code
  • the protection program implements the following steps when executed by the processor:
  • the encrypted file is retrieved and decrypted by the processed JDK.
  • the present application further provides a source code protection method, where the method is applied to an application server, and the method includes:
  • the encrypted file is retrieved and decrypted by the processed JDK.
  • the present application further provides a computer readable storage medium storing an active code protection program, the source code protection program being executable by at least one processor, such that The at least one processor performs the steps of the source code protection method as described above.
  • the application server, the source code protection method, and the computer readable storage medium proposed by the present application first receive a code encryption program input by a user, and encrypt the source code by using the code encryption program. Obtaining the encrypted file; secondly, obtaining the JDK, and processing the JDK by using a code decryption program corresponding to the code encryption program to obtain the processed JDK; then, running the processed JDK; finally, The encrypted file is retrieved and decrypted by the processed JDK.
  • the disadvantages of the prior art class files being reused or decompiled can be avoided, the source files are effectively prevented from being decompiled, the security of the source files is ensured, and the cross-platform characteristics of the programs are maintained, thereby improving the user experience.
  • 1 is a schematic diagram of an optional hardware architecture of an application server of the present application
  • FIG. 2 is a block diagram showing the program of the first embodiment of the source code protection program of the present application
  • FIG. 3 is a block diagram showing a program module of a second embodiment of the source code protection program of the present application.
  • FIG. 4 is a flowchart of a first embodiment of a source code protection method according to the present application.
  • FIG. 5 is a flowchart of a second embodiment of a source code protection method according to the present application.
  • FIG. 6 is a flowchart of a third embodiment of a source code protection method according to the present application.
  • FIG. 7 is a flowchart of a fourth embodiment of a source code protection method according to the present application.
  • first, second and the like in the present application are for the purpose of description only, and are not to be construed as indicating or implying their relative importance or implicitly indicating the number of technical features indicated. .
  • features defining “first” and “second” may include at least one of the features, either explicitly or implicitly.
  • the technical solutions between the various embodiments may be combined with each other, but must be based on the realization of those skilled in the art, and when the combination of the technical solutions is contradictory or impossible to implement, it should be considered that the combination of the technical solutions does not exist. Nor is it within the scope of protection required by this application.
  • FIG. 1 it is a schematic diagram of an optional hardware architecture of the application server 1.
  • the application server 1 may be a computing device such as a rack server, a blade server, a tower server, or a rack server.
  • the application server 1 may be a stand-alone server or a server cluster composed of multiple servers.
  • the application server 1 may include, but is not limited to, the memory 11, the processor 12, and the network interface 13 being communicably connected to each other through a system bus.
  • the application server 1 connects to the network through the network interface 13 (not shown in FIG. 1) to obtain information.
  • the network 1 may be an intranet, an Internet, a Global System of Mobile communication (GSM), a Wideband Code Division Multiple Access (WCDMA), a 4G network, Wireless or wired networks such as 5G networks, Bluetooth, Wi-Fi, and call networks.
  • GSM Global System of Mobile communication
  • WCDMA Wideband Code Division Multiple Access
  • 4G network Wireless or wired networks such as 5G networks, Bluetooth, Wi-Fi, and call networks.
  • Figure 1 only shows the application server 1 with components 11-13, but it should be understood that not all illustrated components may be implemented, and more or fewer components may be implemented instead.
  • the memory 11 includes at least one type of readable storage medium including a flash memory, a hard disk, a multimedia card, a card type memory (eg, SD or DX memory, etc.), and a random access memory (RAM). , static random access memory (SRAM), read only memory (ROM), electrically erasable programmable read only memory (EEPROM), programmable read only memory (PROM), magnetic memory, magnetic disk, optical disk, and the like.
  • the memory 11 may be an internal storage unit of the application server 1, such as a hard disk or memory of the application server 1.
  • the memory 11 may also be an external storage device of the application server 1, such as a plug-in hard disk equipped with the application server 1, a smart memory card (SMC), and a secure digital ( Secure Digital, SD) cards, flash cards, etc.
  • the memory 11 can also include both the internal storage unit of the application server 1 and its external storage device.
  • the memory 11 is generally used to store an operating system installed on the application server 1 and various types of application software, such as program code of the source code protection program 200. Further, the memory 11 can also be used to temporarily store various types of data that have been output or are to be output.
  • the processor 12 may be a Central Processing Unit (CPU), controller, microcontroller, microprocessor, or other data processing chip in some embodiments.
  • the processor 12 is typically used to control the overall operation of the application server 1, such as performing data interaction or communication related control and processing, and the like.
  • the processor 12 is configured to run program code or process data stored in the memory 11, such as running the source code protection program 200 and the like.
  • the network interface 13 may comprise a wireless network interface or a wired network interface, which is typically used to establish a communication connection between the application server 1 and other electronic devices.
  • the application code server 200 installs and runs an active code protection program 200.
  • the application server 1 receives a code encryption program input by a user, and utilizes the code.
  • the encryption program encrypts the source code to obtain an encrypted file; obtains a JDK, and processes the JDK by using a code decryption program corresponding to the code encryption program to obtain a processed JDK; JDK; the encrypted file is retrieved and decrypted by the processed JDK.
  • the disadvantages of the prior art class files being reused or decompiled can be avoided, the source files are effectively prevented from being decompiled, the security of the source files is ensured, and the cross-platform characteristics of the programs are maintained, thereby improving the user experience.
  • the present application proposes a source code protection program 200.
  • the source code protection program 200 includes a series of computer program instructions stored in the memory 11, and when the computer program instructions are executed by the processor 12, the source code protection of the embodiments of the present application can be implemented. Control operation.
  • the source code protection program 200 can be divided into one or more modules based on the particular operations implemented by the various portions of the computer program instructions. For example, in FIG. 2, the source code protection program 200 can be divided into a receiving module 201, an encryption module 202, an obtaining module 203, an executing module 204, and a decrypting module 205. among them:
  • the receiving module 201 is configured to receive a code encryption program input by a user.
  • the source code refers to source code of an application that needs to be deployed externally.
  • the code encryption program input by the user is described by taking a C language code (C code for short) encryption program as an example.
  • C code encryption program By adding a C code encryption program to the source code of the application, and then compiling, the source code is encrypted at the same time as the compilation is completed.
  • the C code encryption program and the following C code decryption program are some existing C code encryption and decryption programs, which will not be described in detail herein.
  • the encryption module 202 is configured to encrypt the source code by using the code encryption program to obtain an encrypted file.
  • the obtaining module 203 is configured to obtain a JDK, and process the JDK by using a code decryption program corresponding to the code encryption program to obtain a processed JDK.
  • JDK is a Java language software development kit for Java applications on mobile devices and embedded devices.
  • the obtaining module 203 is further configured to:
  • Parsing the JDK acquiring a file processing code program of the JDK; inserting an encryption determination program before the file processing code program and inserting a call function of the code decryption program after the encryption determination program.
  • the encryption judging program is configured to determine whether the file retrieved by the JDK is encrypted, and the calling function is configured to retrieve the code decryption program after determining that the file retrieved by the JDK is encrypted.
  • the file processing code program includes: a load file program, a definition class file program, and a decompression compression package program.
  • the obtained JDK is an existing open source JDK, such as JDK1.7, JDK1.8, etc.
  • the open source JDK can parse the code program of the implementation, and can be based on the existing code.
  • the program adds a developer-defined function program.
  • the load file program, the definition class file program, and the decompression compression package program may be added to the judgment program to determine whether the received file has been encrypted, and the specific judgment method.
  • the normal parsing function can be called to parse the received file. If it can be parsed normally, it is not encrypted. Otherwise, it is encrypted.
  • the calling function of the C code decryption program may also be added to implement the call of the C code decryption program.
  • the execution module 204 is configured to run the processed JDK.
  • the decryption module 205 retrieves the encrypted file and decrypts it by using the processed JDK.
  • the decrypting module 205 is further configured to:
  • the decrypting module 205 encrypts the The file is decrypted. Otherwise, if the application corresponding to the encrypted file does not satisfy the preset identifier, the decryption module 205 does not decrypt the encrypted file.
  • JVM Java Virtual Machine
  • the source code protection program 200 proposed by the present application first receives a code encryption program input by a user, and encrypts the source code by using the code encryption program to obtain an encrypted file; Next, the JDK is obtained, and the JDK is processed by a code decryption program corresponding to the code encryption program to obtain a processed JDK; then, the processed JDK is executed; finally, the processed JDK is passed.
  • the encrypted file is retrieved and decrypted.
  • the source code protection program 200 further includes a storage module 206, and the storage module 206 is configured to:
  • the encrypted file is stored on the hard disk before the execution module 204 runs the processed JDK.
  • the decryption module 205 is further configured to:
  • the calling function in the post JDK calls the code decryption program to decrypt the encrypted file.
  • the application is stored in the hard disk in the form of a source code class file before being executed by the JDK, so that the encrypted source code can be immediately called from the hard disk through the processed JDK.
  • Decoding does not involve the subsequent processing flow of the application source code, and achieves transparency to subsequent applications.
  • the source code protection program 200 proposed by the present application can immediately decode the encrypted source code from the hard disk through the processed JDK, and does not involve subsequent processing of the application source code.
  • the process implements transparency for subsequent applications.
  • the present application also proposes a source code protection method.
  • FIG. 4 it is a flowchart of the first embodiment of the source code protection method of the present application.
  • the order of execution of the steps in the flowchart shown in FIG. 4 may be changed according to different requirements, and some steps may be omitted.
  • Step S401 receiving a code encryption program input by a user.
  • the code encryption program that the user enters at the mobile terminal refers to source code of an application that needs to be deployed externally.
  • the code encryption program input by the user is described by taking a C language code (C code for short) encryption program as an example.
  • C code encryption program and the following C code decryption program are some existing C code encryption and decryption programs, which will not be described in detail herein.
  • Step S402 encrypting the source code by using the code encryption program to obtain an encrypted file.
  • Step S403 acquiring the JDK, and processing the JDK by using a code decryption program corresponding to the code encryption program to obtain the processed JDK.
  • JDK is a Java language software development kit for Java applications on mobile devices and embedded devices. Specifically, the specific steps of processing the JDK by using a code decryption program corresponding to the code encryption program will be described in detail in the second embodiment of the source code protection method of the present application (see FIG. 5).
  • Step S404 running the processed JDK.
  • Step S405 the encrypted file is retrieved and decrypted by the processed JDK.
  • the application server 1 before the step of retrieving and decrypting the encrypted file by the processed JDK, the application server 1 further obtains an encrypted operation in a Java Virtual Machine (JVM). Whether the application corresponding to the file satisfies the preset identifier; if the application corresponding to the encrypted file satisfies the preset identifier, the application server 1 decrypts the encrypted file; otherwise, if the application corresponding to the encrypted file is not satisfied If the identifier is preset, the application server 1 does not decrypt the encrypted file.
  • JVM Java Virtual Machine
  • the source code protection method proposed by the present application first receives a code encryption program input by a user, and encrypts the source code by using the code encryption program to obtain an encrypted file; secondly, Obtaining a JDK, and processing the JDK by using a code decryption program corresponding to the code encryption program to obtain a processed JDK; then, running the processed JDK; and finally, obtaining the processed JDK
  • the encrypted file is decrypted.
  • the step of processing the JDK by using a code decryption program corresponding to the code encryption program includes:
  • Step S501 parsing the JDK, and acquiring the file processing code program of the JDK.
  • the file processing code program includes: a load file program, a definition class file program, and a decompression compression package program.
  • Step S502 inserting an encryption determination program before the file processing code program and inserting a call function of the code decryption program after the encryption determination program.
  • Step S503 determining, by the encryption determination program, whether the file retrieved by the JDK is encrypted. After the file retrieved by the JDK is encrypted, step S504 is performed; otherwise, the process ends.
  • Step S504 the code decryption program is called by the calling function.
  • the obtained JDK is an existing open source JDK, such as JDK1.7, JDK1.8, etc.
  • the open source JDK can parse the code program of the implementation, and can be based on the existing code.
  • the program adds a developer-defined function program.
  • the load file program, the definition class file program, and the decompression compression package program may be added to the judgment program to determine whether the received file has been encrypted, and the specific judgment method.
  • the normal parsing function can be called to parse the received file. If it can be parsed normally, it is not encrypted. Otherwise, it is encrypted.
  • the calling function of the C code decryption program may also be added to implement the call of the C code decryption program.
  • the source code protection method proposed by the present application can process the JDK by using a code decryption program corresponding to the code encryption program.
  • FIG. 6 it is a flowchart of a third embodiment of the source code protection method of the present application.
  • the order of execution of the steps in the flowchart shown in Fig. 6 may be changed according to different needs, and some steps may be omitted.
  • Step S601 receiving a code encryption program input by the user.
  • Step S602 encrypting the source code by using the code encryption program to obtain an encrypted file.
  • Step S603 acquiring the JDK, and processing the JDK by using a code decryption program corresponding to the code encryption program to obtain the processed JDK.
  • Step S604 storing the encrypted file on a hard disk.
  • Step S605 running the processed JDK.
  • Step S606 the encrypted file is retrieved and decrypted by the processed JDK.
  • the source code protection method proposed by the present application can immediately decode the encrypted source code by calling the processed JDK from the hard disk, and does not involve the subsequent processing flow of the application source code. , to achieve transparency of subsequent applications.
  • the step of retrieving and decrypting the encrypted file by using the processed JDK includes:
  • Step S701 reading the encrypted file from the hard disk.
  • Step S702 determining whether the read encrypted file is encrypted by using the processed JDK. If the encrypted file is encrypted, step S703 is performed, otherwise, the process ends.
  • Step S703 using the calling function in the processed JDK to call the code decryption program to decrypt the encrypted file.
  • the application is stored in the hard disk in the form of a source code class file before being executed by the JDK, so that the encrypted source code can be immediately called from the hard disk through the processed JDK.
  • Decoding does not involve the subsequent processing flow of the application source code, and achieves transparency to subsequent applications.
  • the source code protection method proposed by the present application can retrieve the encrypted file and decrypt it through the processed JDK.
  • the foregoing embodiment method can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is better.
  • Implementation Based on such understanding, the technical solution of the present application, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • the optical disc includes a number of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the methods described in various embodiments of the present application.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Multimedia (AREA)
  • Technology Law (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Storage Device Security (AREA)

Abstract

L'invention concerne un procédé de protection de code source. Le procédé consiste : à recevoir un programme de chiffrement de code entré par un utilisateur, et à utiliser le programme de chiffrement de code afin de chiffrer un code source, afin d'obtenir un fichier chiffré ; à acquérir JDK, et à utiliser un programme de déchiffrement de code correspondant au programme de chiffrement de code afin de traiter la JDK,afin d'obtenir le JDK traité ; à exécuter le JDK traité ; et à invoquer le fichier chiffré par l'intermédiaire du JDK traité et à le déchiffrer. L'invention concerne également un serveur d'application. Le procédé de protection de code source et le serveur d'application fournis dans la présente invention permettent d'arrêter efficacement un fichier source d'être décompilé, d'assurer la sécurité du fichier source, de maintenir également la propriété inter-plateforme d'un programme, et d'améliorer l'expérience utilisateur.
PCT/CN2018/077642 2017-09-30 2018-02-28 Procédé de protection de code source, serveur d'application et support d'informations lisible par ordinateur Ceased WO2019062015A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710914956.6 2017-09-30
CN201710914956.6A CN108399319B (zh) 2017-09-30 2017-09-30 源代码保护方法、应用服务器及计算机可读存储介质

Publications (1)

Publication Number Publication Date
WO2019062015A1 true WO2019062015A1 (fr) 2019-04-04

Family

ID=63094492

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/077642 Ceased WO2019062015A1 (fr) 2017-09-30 2018-02-28 Procédé de protection de code source, serveur d'application et support d'informations lisible par ordinateur

Country Status (2)

Country Link
CN (1) CN108399319B (fr)
WO (1) WO2019062015A1 (fr)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109040133A (zh) * 2018-09-27 2018-12-18 上海点融信息科技有限责任公司 在区块链网络中安装智能合约的方法、装置及存储介质
CN109409038A (zh) * 2018-09-30 2019-03-01 北京梆梆安全科技有限公司 一种动态链接库文件的破解风险检测方法及装置
CN109460640A (zh) * 2018-11-13 2019-03-12 杭州涂鸦信息技术有限公司 一种Java程序保护方法、装置、设备及可读存储介质
CN110267253B (zh) * 2019-05-13 2022-09-27 中国联合网络通信集团有限公司 eSIM管理平台、eSIM安装方法及装置
CN111274551B (zh) * 2019-12-30 2023-06-27 上海上讯信息技术股份有限公司 基于编译器的java代码保护方法、装置及电子设备
CN111367505A (zh) * 2020-03-02 2020-07-03 广州致远电子有限公司 一种JavaScript源代码保密方法、装置、设备及存储介质
CN112966227A (zh) * 2021-02-04 2021-06-15 南方电网深圳数字电网研究院有限公司 代码加密解密方法和装置、存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103745141A (zh) * 2013-12-02 2014-04-23 上海斐讯数据通信技术有限公司 智能终端android系统中防止应用程序反编译的方法
CN104462995A (zh) * 2014-11-28 2015-03-25 福建畅云安鼎信息科技有限公司 一种数字化加工安全保护系统
CN104881284A (zh) * 2015-05-22 2015-09-02 国云科技股份有限公司 一种高效的日志操作方法

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060106801A1 (en) * 2004-11-12 2006-05-18 International Business Machines Corporation Securing location of an installed middleware application and securing location of containers contained within installed middleware application
EP2980695B1 (fr) * 2010-05-09 2017-04-12 Citrix Systems, Inc. Procédés et systèmes pour forcer une application pour stocker des données dans un emplacement de stockage sécurisé
CN102708322B (zh) * 2012-05-12 2016-02-24 北京深思数盾科技有限公司 安卓系统中java应用程序的保护方法
CN103955423B (zh) * 2013-12-25 2017-01-11 中软信息系统工程有限公司 一种国产jvm的测试评估方法
CN106709286A (zh) * 2016-11-30 2017-05-24 江苏神州信源系统工程有限公司 一种对apk资源包进行安全加固的方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103745141A (zh) * 2013-12-02 2014-04-23 上海斐讯数据通信技术有限公司 智能终端android系统中防止应用程序反编译的方法
CN104462995A (zh) * 2014-11-28 2015-03-25 福建畅云安鼎信息科技有限公司 一种数字化加工安全保护系统
CN104881284A (zh) * 2015-05-22 2015-09-02 国云科技股份有限公司 一种高效的日志操作方法

Also Published As

Publication number Publication date
CN108399319A (zh) 2018-08-14
CN108399319B (zh) 2021-07-16

Similar Documents

Publication Publication Date Title
US10853270B2 (en) Cryptographic pointer address encoding
CN108399319B (zh) 源代码保护方法、应用服务器及计算机可读存储介质
CN104680039B (zh) 一种应用程序安装包的数据保护方法及装置
CN103530535A (zh) 一种Android平台应用程序保护的加脱壳方法
US20170295013A1 (en) Method for fulfilling a cryptographic request requiring a value of a private key
KR102433011B1 (ko) Apk 파일 보호 방법, 이를 수행하는 apk 파일 보호 시스템, 및 이를 저장하는 기록매체
CN106155729B (zh) Lua脚本热更新方法、装置及系统
CN106203006A (zh) 基于dex与so文件动态执行的Android应用加固方法
CN104318155A (zh) 一种防逆向apk文件的动态加载方法
EP3264265A1 (fr) Procédé, serveur et terminal de protection d'application
CN114547558A (zh) 授权方法、授权控制方法及装置、设备和介质
US8918653B2 (en) Protection of interpreted source code in virtual appliances
CN109787768B (zh) 一种身份验证配置方法、装置及计算机可读存储介质
CN108664796B (zh) 一种so文件保护方法及装置
CN113836582A (zh) 软件加密及解密方法、装置、电子设备和存储介质
CN117313046A (zh) 一种代码加固方法、代码加载方法、设备及介质
CN112115430A (zh) 一种apk的加固方法、电子设备及存储介质
CN108173906A (zh) 安装包下载方法、装置、存储介质及电子设备
CN110535642B (zh) 一种分散存储密钥的方法、智能终端及存储介质
CN104751026B (zh) 安卓系统的软件保护方法、软件应用方法及相关装置
CN114547653B (zh) 开发环境的加密方法、解密方法及装置、设备和介质
CN108696526B (zh) 网络请求响应数据的解析方法、装置、设备及存储介质
US20080301654A1 (en) Program processing apparatus, program processing method and computer readable information recording medium
CN108021790B (zh) 文件保护方法、装置、计算设备及计算机存储介质
CN114547661B (zh) 应用配置数据的加解密方法、装置、设备和存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18863039

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 28.09.2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18863039

Country of ref document: EP

Kind code of ref document: A1