Zero-code-based file encryption method, system, electronic device and storage medium

Abstract

The present disclosure relates to a zero-code-based file encryption method, system, electronic device and storage medium, the method comprising: zip compression and encryption of an original file stream; generating a first AES key using the current timestamp, machine id, system process id and natural number; storing the first AES key in the head of the generated partially encrypted file stream; obfuscating the order of the file stream; generating a file stream check code for the file stream after the obfuscated order; encrypting the first AES key to obtain a second AES key; storing the generated file stream check code and the second AES key in the head of the file stream; obfuscating the order of the file stream again; encrypting the user source information; storing the encrypted user source information in the head of the file stream; obfuscating the order of the file stream again; cutting and segmenting the entire file stream according to the specified size; and outputting after merging. The present disclosure can improve data security, reduce server pressure, and reduce customer cross-platform operation cost.

Description

Technical Field

[0001] This disclosure relates to the field of data encryption, specifically to a zero-code file encryption method, system, electronic device, and storage medium. Background Technology

[0002] In cloud platform systems, it is necessary to realize the cross-environment transfer of application function configurations. To achieve cross-environment and cross-cloud platform access, it is necessary to generate local files. These files contain important data of business partners, so a special encryption method is required to generate a special format file, MDY encrypted file, which cannot be cracked. This file is used for the implementation of digital services by business partners. Once the business partners' customers receive the MDY encrypted file, they can import it into the system and use it without having to perform repetitive application function configuration work.

[0003] Currently, the mainstream encryption methods include: using zip to compress files and setting passwords for the compressed files; processing through complex data exchange algorithms; generating the key directly in the file and "packing" the file to prevent decompilation; and purchasing commercially available dongle software.

[0004] However, the above methods have the following shortcomings: Files compressed with zip can be directly decompressed with software, and even if a password is set for the compressed file, it can be cracked by brute force; files processed through complex data exchange can be cracked by hackers through software debugging techniques to restore the algorithm logic and thus obtain the encrypted file; there are also many tools for "unpacking" files, so conventional packing methods cannot prevent data theft; using dongles for protection is costly and difficult to implement, and if a dongle from a certain brand has a vulnerability or is cracked, all software and data using that brand are at risk.

[0005] Therefore, we urgently need to provide a file encryption method, encryption system, electronic device, and storage medium to increase the difficulty of cracking files, thereby improving data security. Summary of the Invention

[0006] This disclosure provides a zero-code-based file encryption method, system, electronic device, and storage medium to at least solve one of the technical problems existing in the background art described above.

[0007] In a preferred embodiment of this disclosure, this application provides a zero-code file encryption method, the method comprising:

[0008] Encode the business data loaded in the zero-code system to obtain the original file stream;

[0009] The original file stream is compressed and encrypted using zip, resulting in a partially encrypted file stream;

[0010] Generate the first AES key using the current timestamp, machine ID, system process ID, and a natural number;

[0011] The first AES key is stored in the header of the generated partially encrypted file stream;

[0012] The order of file streams was first obfuscated;

[0013] Generate a file stream hash code for the file stream after the first obfuscation, and perform a hexadecimal conversion to obtain the file stream checksum;

[0014] Encrypt the first AES key to obtain the second AES key;

[0015] The generated file stream checksum and the second AES key are stored in the header of the file stream after the first obfuscation order;

[0016] The order of the file streams is obfuscated a second time;

[0017] Encrypt user source information;

[0018] The encrypted user source information is stored at the beginning of the file stream after the second obfuscation order;

[0019] The third obfuscation of the file stream order;

[0020] The entire file stream after the third obfuscation is divided into segments of a specified size and encrypted in segments.

[0021] The segmented encrypted file streams are merged and output to generate a complete encrypted file stream.

[0022] Furthermore, the encoding of the business data loaded in the no-code system specifically refers to encoding the business data loaded in the no-code system according to the default encoding method of Microsoft .NET.

[0023] Furthermore, the step of zip-compressing and encrypting the original file stream specifically includes:

[0024] Different enumeration values ​​are generated for different business data. The enumeration values ​​are specified JSON strings generated by the business modules inside the no-code system, including worksheets, workflows, application roles, and reports.

[0025] The enumerated values ​​are mixed into the original file stream, and the original file stream is zip compressed and encrypted using the LZ77 algorithm and the Huffman algorithm to generate a partially encrypted file stream.

[0026] Furthermore, the step of generating the first AES key using the current timestamp, machine ID, system process ID, and natural number specifically refers to: adding a natural number to the current timestamp of the server operating system, the host machine ID, and the process ID of the current system program running in the server operating system to generate a string, and using the generated string as the first AES key.

[0027] Furthermore, the encryption of the first AES key specifically refers to performing one AES self-encryption and two MD5 encryptions on the first AES key.

[0028] Furthermore, the encrypted user source information specifically refers to performing AES encryption and RSA asymmetric encryption on the user source information.

[0029] Furthermore, the encrypted user source information specifically includes the following steps:

[0030] For information from different users and different sources, a string of identity information is generated, which includes system organization ID, source ID, version information, timestamp, and password for using encrypted files;

[0031] Generate public and private keys for the RSA algorithm and store them in a zero-code system;

[0032] The second AES key is encrypted using the generated RSA algorithm private key to obtain the third AES key;

[0033] The third AES key is stored in the header of the file stream after the second obfuscation order;

[0034] The generated identity information is encrypted once using a third AES key;

[0035] The generated identity information is encrypted using an RSA algorithm using the generated public and private keys.

[0036] Furthermore, the segmented encryption specifically refers to using the second AES key to encrypt each segment of the file stream using AES.

[0037] In a preferred embodiment of this disclosure, this application also provides a zero-code-based file encryption system, comprising:

[0038] The zip compression module is used to encode the business data loaded in the no-code system to obtain the original file stream; the original file stream is then compressed and encrypted using zip to obtain a partially encrypted file stream.

[0039] The first AES key generation module is used to generate a first AES key using the current timestamp, machine ID, system process ID, and natural number; and stores the first AES key generated by the first AES key generation module in the header of the file stream generated by the zip compression module.

[0040] The first obfuscation module is used to obfuscate the order of file streams for the first time;

[0041] The file stream checksum generation module is used to generate a file stream hash code for the file stream generated by the first obfuscation module, and perform hexadecimal conversion to obtain the file stream checksum; the file stream checksum is stored in the header of the file stream generated by the first obfuscation module.

[0042] The second AES key generation module is used to encrypt the first AES key to obtain the second AES key; the second AES key is stored in the header of the file stream generated by the first obfuscation module;

[0043] The second obfuscation module is used to obfuscate the order of the file streams a second time;

[0044] The user source information encryption module is used to encrypt user source information; the encrypted user source information is stored in the header of the file stream generated by the second obfuscation module.

[0045] The third obfuscation module is used to obfuscate the order of the file streams for the third time;

[0046] The segmented encryption module is used to cut the entire file stream generated by the third obfuscation module into segments of a specified size and then encrypt them.

[0047] The output module is used to merge the file streams generated by the segmented encryption module and output them as a complete encrypted file stream.

[0048] In a preferred embodiment of this disclosure, this application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the above-described zero-code-based file encryption method.

[0049] In a preferred embodiment of this disclosure, the present application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of the above-described zero-code-based file encryption method.

[0050] The beneficial effects of this disclosure are: the zero-code file encryption method provided by this disclosure combines multiple encryption methods, adds salt during the encryption process, and obfuscates the file stream to be encrypted based on the characteristics of actual business data, achieving the purpose of being unbreakable and improving data security; during the encryption process, the encrypted file stream is segmented, reducing server pressure; through the above encryption methods, application configuration data can be transferred across environments, reducing customer operating costs. Attached Figure Description

[0051] Figure 1 A flowchart for zero-code file encryption;

[0052] Figure 2 Flowchart for generating the first AES key;

[0053] Figure 3 Flowchart of the first AES key encryption process;

[0054] Figure 4 Flowchart for encrypting user source information;

[0055] Figure 5 Flowchart for segmented encryption of file streams;

[0056] Figure 6 This is a diagram showing the components of a zero-code file encryption system. Detailed Implementation

[0057] The technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. Based on the embodiments of this disclosure, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this disclosure.

[0058] Example 1

[0059] Please see the appendix Figure 1 The file encryption method based on zero-code proposed according to the exemplary embodiments of this disclosure combines multiple encryption methods and is specially optimized for zero-code scenarios. It generates a file stream of information to be encrypted, processes the file stream multiple times, adds salt according to the specified business scenario, generates a special encryption key, shuffles the order of the file stream, segments the encrypted file stream, and finally merges the file streams to output the final encrypted file.

[0060] The implementation process of the no-code file encryption method, as an example, includes the following steps:

[0061] In the no-code system, the required business data is loaded, and the data is encoded according to the default encoding method of Microsoft .NET to obtain the original file stream.

[0062] Different enumeration values ​​are generated for different business data. These enumeration values ​​are specified JSON strings generated by the business modules within the no-code system, including worksheets, workflows, application roles, and reports.

[0063] The enumerated values ​​are mixed into the original file stream, and the original file stream is zip compressed and encrypted using the LZ77 algorithm and the Huffman algorithm to generate a partially encrypted file stream.

[0064] Read the current timestamp of the server operating system, the host machine ID, and the process ID of the currently running system program within the server operating system. Add these to a natural number to generate a string. This string is used as the first AES key and stored at a specified location in the current file stream to be encrypted, such as the header. Figure 2 As shown.

[0065] The initial obfuscation of file stream information, disrupting the order of the file streams, is to prevent the file streams from being cracked.

[0066] Generate a file stream hash code from the file stream after the first obfuscation, and perform a hexadecimal conversion to obtain the file stream checksum. Store the file stream checksum at a specified location in the file stream, such as the header.

[0067] Perform AES self-encryption on the first AES key to generate a special key. Then, perform MD5 encryption twice on the self-encrypted special key to obtain the second AES key. Store the second AES key at a specified location in the file stream, such as the header. Figure 3 As shown. After two MD5 encryptions, the file stream is virtually impossible to crack. MD5 is a widely used cryptographic hash function that produces a 128-bit (16-byte) hash value to ensure the integrity and consistency of the transmission.

[0068] A second obfuscation of the file stream information is performed to ensure that even if the file stream is intercepted, it is essentially unbreakable.

[0069] For information from different users and different sources, a string of identity information is generated, which includes system organization ID, source ID, version information, timestamp, and password for using encrypted files.

[0070] Using the RSA asymmetric encryption algorithm, a public and private key for the RSA algorithm is generated and stored in a zero-code system.

[0071] The second AES key is encrypted using the generated RSA algorithm private key to obtain the third AES key; the third AES key is stored in the header of the file stream after the second obfuscation order; the generated identity information is then encrypted using AES using the third AES key; finally, the generated identity information is encrypted using RSA algorithm using the generated RSA algorithm public and private keys, as follows. Figure 4 As shown. The RSA algorithm is an asymmetric encryption algorithm, theoretically unbreakable. RSA public-key cryptography uses different encryption and decryption keys; "deriving the decryption key from a known encryption key is computationally infeasible." By applying AES encryption and RSA asymmetric encryption to the user's source information, the generated user source information is theoretically unbreakable.

[0072] The encrypted user source information is stored at a specified location in the file stream after the second obfuscation order, such as the header, and the file stream information is obfuscated a third time.

[0073] Finally, the entire file stream is segmented according to a specified size. After segmentation, each segment is encrypted using AES. Figure 5 As shown, the key used is Figure 3 The process of encrypting a file stream in segments using the generated second AES key is equivalent to modifying the length of each AES-encrypted segment, thus changing the size of the encrypted file. Segmented encryption also solves the problem of wasted server resources caused by encrypting a large file at once, thereby reducing server load.

[0074] Finally, the streams are merged to generate a complete encrypted file stream, which is then output as the final file. By encrypting the file streams in segments and then merging them, the goal of making the encrypted file unbreakable is achieved.

[0075] Example 2

[0076] like Figure 6 As shown, a zero-code-based file encryption system, as an example, includes:

[0077] The zip compression module is used to encode the business data loaded in the no-code system to obtain the original file stream; the original file stream is then compressed and encrypted using zip to obtain a partially encrypted file stream.

[0078] The first AES key generation module is used to generate a first AES key using the current timestamp, machine ID, system process ID, and natural number; and stores the first AES key generated by the first AES key generation module in the header of the file stream generated by the zip compression module.

[0079] The first obfuscation module is used to obfuscate the order of file streams for the first time;

[0080] The file stream checksum generation module is used to generate a file stream hash code for the file stream generated by the first obfuscation module, and perform hexadecimal conversion to obtain the file stream checksum; the file stream checksum is stored in the header of the file stream generated by the first obfuscation module.

[0081] The second AES key generation module is used to encrypt the first AES key to obtain the second AES key; the second AES key is stored in the header of the file stream generated by the first obfuscation module;

[0082] The second obfuscation module is used to obfuscate the order of the file streams a second time;

[0083] The user source information encryption module is used to encrypt user source information; the encrypted user source information is stored in the header of the file stream generated by the second obfuscation module.

[0084] The third obfuscation module is used to obfuscate the order of the file streams for the third time;

[0085] The segmented encryption module is used to cut the entire file stream generated by the third obfuscation module into segments of a specified size and then encrypt them.

[0086] The output module is used to merge the file streams generated by the segmented encryption module and output them as a complete encrypted file stream.

[0087] Furthermore, the zip compression module includes an original file stream generation module and a partially encrypted file stream generation module. The original file stream generation module is used to encode the business data loaded in the no-code system according to the default encoding method of Microsoft .NET to obtain the original file stream. The partially encrypted file stream generation module is used to generate different enumeration values ​​for different business data. The enumeration values ​​are specified JSON strings generated based on the business modules inside the no-code system, including worksheets, workflows, application roles, and reports. The enumeration values ​​are mixed into the original file stream, and the original file stream is zip compressed and encrypted using the LZ77 algorithm and the Huffman algorithm to generate a partially encrypted file stream.

[0088] Furthermore, the first AES key generation module is specifically used to: add a natural number to the current timestamp of the server operating system, the host machine ID, and the process ID of the current system program running in the server operating system to generate a string, and use the generated string as the first AES key; and store the first AES key generated by the first AES key generation module in the header of the file stream generated by the zip compression module.

[0089] Furthermore, the second AES key generation module is specifically used to: perform AES self-encryption once and MD5 encryption twice on the first AES key to obtain the second AES key; and store the second AES key in the header of the file stream generated by the first obfuscation module.

[0090] Furthermore, the user source information encryption module is specifically used to perform AES encryption and RSA asymmetric encryption on the user source information; and to store the encrypted user source information in the header of the file stream generated by the second obfuscation module.

[0091] Furthermore, the user source information encryption module specifically includes:

[0092] The identity information generation module is used to generate a string of identity information for different users and different sources. The identity information includes system organization ID, source ID, version information, timestamp, and password for encrypted files.

[0093] The RSA public and private key generation module is used to generate public and private keys for the RSA algorithm and store them in the zero-code system.

[0094] The third AES key generation module is used to encrypt the second AES key using the RSA algorithm private key generated by the RSA public key and private key generation module to obtain the third AES key; the third AES key is stored in the header of the file stream after the second obfuscation order.

[0095] The AES encryption module is used to encrypt the identity information generated by the identity information generation module using the third AES key generated by the third AES key generation module.

[0096] The RSA encryption module is used to encrypt the identity information generated by the identity information generation module using the RSA algorithm public and private keys generated by the RSA public and private key generation module.

[0097] Furthermore, the segmented encryption module is specifically used to encrypt each segment of the file stream using the second AES key.

[0098] Example 3

[0099] An electronic device includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the zero-code-based file encryption method of Embodiment 1.

[0100] Embodiment 1 of this disclosure is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this disclosure.

[0101] Electronic devices can take the form of general-purpose computing devices, such as server devices. Components of an electronic device may include, but are not limited to: at least one processor, at least one memory, and buses connecting different system components (including memory and processor).

[0102] The bus includes a data bus, an address bus, and a control bus.

[0103] The memory may include volatile memory, such as random access memory (RAM) and / or cache memory, and may further include read-only memory (ROM).

[0104] The memory may also include program tools having a set (at least one) of program modules, including but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of these examples may include an implementation of a network environment.

[0105] The processor performs various functional applications and data processing by running computer programs stored in memory.

[0106] Electronic devices can also communicate with one or more external devices (such as keyboards, pointing devices, etc.). This communication can be achieved through input / output (I / O) interfaces. Furthermore, electronic devices can communicate with one or more networks (such as local area networks (LANs), wide area networks (WANs), and / or public networks, such as the Internet) via network adapters. The network adapter communicates with other modules of the electronic device via a bus. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with the electronic device, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID (disk array) systems, tape drives, and data backup storage systems.

[0107] It should be noted that although several units / modules or sub-units / modules of the electronic device have been mentioned in the detailed description above, this division is merely exemplary and not mandatory. In fact, according to the embodiments of this application, the features and functions of two or more units / modules described above can be embodied in one unit / module. Conversely, the features and functions of one unit / module described above can be further divided and embodied by multiple units / modules.

[0108] Example 4

[0109] A computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the zero-code-based file encryption method of Embodiment 1.

[0110] The readable storage medium may be more specifically adopted, including but not limited to: portable disk, hard disk, random access memory, read-only memory, erasable programmable read-only memory, optical storage device, magnetic storage device, or any suitable combination thereof.

[0111] In a possible implementation, this disclosure can also be implemented as a program product comprising program code that, when the program product is run on a terminal device, causes the terminal device to perform the steps of implementing the zero-code-based file encryption method described in Embodiment 1.

[0112] The program code for executing this disclosure can be written in any combination of one or more programming languages, and the program code can be executed entirely on a user device, partially on a user device, as a stand-alone software package, partially on a user device and partially on a remote device, or entirely on a remote device.

[0113] Although embodiments of the present disclosure have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the present disclosure, the scope of which is defined by the appended claims and their equivalents.

Claims

1. A no-code file encryption method, characterized in that, The steps include the following: Encode the business data loaded in the zero-code system to obtain the original file stream; The original file stream is compressed and encrypted using zip, resulting in a partially encrypted file stream; Generate the first AES key using the current timestamp, machine ID, system process ID, and a natural number; The first AES key is stored in the header of the generated partially encrypted file stream; The order of file streams was first obfuscated; Generate a file stream hash code for the file stream after the first obfuscation, and perform a hexadecimal conversion to obtain the file stream checksum; The first AES key is subjected to one AES self-encryption and two MD5 encryptions to obtain the second AES key; The generated file stream checksum and the second AES key are stored in the header of the file stream after the first obfuscation order; The order of the file streams is obfuscated a second time; Encrypt user source information; The encrypted user source information is stored at the beginning of the file stream after the second obfuscation order; The third obfuscation of the file stream order; The entire file stream after the third obfuscation is divided into segments of a specified size and encrypted in segments. The segmented encrypted file streams are merged to generate a complete encrypted file stream, which is then output. The segmented encryption includes: using a second AES key to encrypt each segment of the file stream with AES, thereby modifying the length of each segment of the file stream; The encrypted user source information specifically refers to performing AES encryption and RSA asymmetric encryption on the user source information, including the following steps: For information from different users and different sources, a string of identity information is generated, which includes one or more of the following: system organization ID, source ID, version information, timestamp, and password for using encrypted files; Generate public and private keys for the RSA algorithm and store them in a zero-code system; The second AES key is encrypted using the generated RSA algorithm private key to obtain the third AES key; The third AES key is stored in the header of the file stream after the second obfuscation order; The generated identity information is encrypted once using a third AES key; The generated identity information is encrypted using an RSA algorithm using the generated public and private keys.

2. The file encryption method based on zero-code as described in claim 1, characterized in that, The encoding of the business data loaded in the no-code system includes: Encode the business data loaded in the no-code system according to the default encoding method of Microsoft .NET.

3. The file encryption method based on zero-code as described in claim 1, characterized in that, The process of zip-compressing and encrypting the original file stream includes: For different business data, different enumeration values ​​are generated. The enumeration values ​​are specified JSON strings generated by the business modules inside the no-code system, including one or more of the following: worksheet, workflow, application role, and report; The enumerated values ​​are mixed into the original file stream, and the original file stream is zip compressed and encrypted using the LZ77 algorithm and the Huffman algorithm to generate a partially encrypted file stream.

4. The file encryption method based on zero-code as described in claim 1, characterized in that, The process of generating the first AES key using the current timestamp, machine ID, system process ID, and natural number includes: The current timestamp of the server operating system, the host machine ID, and the process ID of the current system program running in the server operating system are read and added to a natural number to generate a string. This string is used as the first AES key.

5. A no-code file encryption system, characterized in that, include: The zip compression module is used to encode the business data loaded in the no-code system to obtain the original file stream; The original file stream is compressed and encrypted using zip, resulting in a partially encrypted file stream; The first AES key generation module is used to generate the first AES key using the current timestamp, machine ID, system process ID, and natural number. The first AES key generated by the first AES key generation module is stored in the header of the file stream generated by the zip compression module; The first obfuscation module is used to obfuscate the order of file streams for the first time; The file stream checksum generation module is used to generate a file stream hash code for the file stream generated by the first obfuscation module, and then perform hexadecimal conversion to obtain the file stream checksum. The file stream checksum is stored in the header of the file stream generated by the first obfuscation module; The second AES key generation module is used to perform one AES self-encryption and two MD5 encryptions on the first AES key to obtain the second AES key; the second AES key is stored in the header of the file stream generated by the first obfuscation module; The second obfuscation module is used to obfuscate the order of the file streams a second time; The user source information encryption module is used to encrypt user source information; the encrypted user source information is stored in the header of the file stream generated by the second obfuscation module. Specifically, encrypting the user source information involves performing AES encryption and RSA asymmetric encryption on the user source information. Includes the following steps: For information from different users and different sources, a string of identity information is generated, which includes one or more of the following: system organization ID, source ID, version information, timestamp, and password for using encrypted files; Generate public and private keys for the RSA algorithm and store them in a zero-code system; The second AES key is encrypted using the generated RSA algorithm private key to obtain the third AES key; The third AES key is stored in the header of the file stream after the second obfuscation order; The generated identity information is encrypted once using a third AES key; The generated identity information is encrypted using an RSA algorithm using the generated public and private keys of the RSA algorithm; The third obfuscation module is used to obfuscate the order of the file streams for the third time; The segmented encryption module is used to cut the entire file stream generated by the third obfuscation module into segments according to a specified size and encrypt them in segments. The segmented encryption includes: using a second AES key to encrypt each segment of the file stream with AES to modify the length of each segment. The output module is used to merge the file streams generated by the segmented encryption module and output them as a complete encrypted file stream.

6. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the zero-code-based file encryption method according to any one of claims 1 to 4.

7. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the steps of the zero-code-based file encryption method according to any one of claims 1 to 4.

Images