CN112241516A - Source code protection method and storage medium for project development process - Google Patents
Source code protection method and storage medium for project development process Download PDFInfo
- Publication number
- CN112241516A CN112241516A CN201910638648.4A CN201910638648A CN112241516A CN 112241516 A CN112241516 A CN 112241516A CN 201910638648 A CN201910638648 A CN 201910638648A CN 112241516 A CN112241516 A CN 112241516A
- Authority
- CN
- China
- Prior art keywords
- task
- project
- file data
- acquiring
- source code
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 55
- 238000004590 computer program Methods 0.000 claims description 6
- 238000012544 monitoring process Methods 0.000 abstract description 2
- 230000010354 integration Effects 0.000 description 11
- 101000878595 Arabidopsis thaliana Squalene synthase 1 Proteins 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 206010033557 Palpitations Diseases 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000002996 emotional effect Effects 0.000 description 1
- 230000009545 invasion Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/602—Providing cryptographic facilities or services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2107—File encryption
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Technology Law (AREA)
- Multimedia (AREA)
- Health & Medical Sciences (AREA)
- Bioethics (AREA)
- General Health & Medical Sciences (AREA)
- Storage Device Security (AREA)
Abstract
The invention provides a source code protection method and a storage medium in a project development process, wherein the method comprises the following steps: generating keys corresponding to all tasks one by one corresponding to all tasks in a project and identity information of a person in charge of the tasks; acquiring a file data stream of an accessed task by intercepting an application running the task; acquiring a key corresponding to the accessed task, and encrypting the file data stream by using the acquired key; generating an encryption identifier uniquely corresponding to the accessed task, and writing the encryption identifier into the encrypted file data stream; and storing the relationship between the key corresponding to each task in a project and the corresponding encryption identifier. Not only can the source code leakage and hacker attack be effectively prevented, and the source code security is improved; but also can efficiently and accurately trace responsibility after the source code is leaked; furthermore, the method also has the functions of monitoring the completion condition of the project and preventing misoperation, so that the safety of the source code is better protected.
Description
Technical Field
The invention relates to the field of data security, in particular to a source code protection method and a storage medium in a project development process.
Background
With the development of the internet, the development and expansion requirements of projects are rapidly increased. Meanwhile, more and more projects enter the process and specialization. Such as: project manager- > issue project- > list- > programmer/art designing- > resource arrangement (resource management) - > test- > project manager.
In the prior art, a git community (which is an open source community) or an svn intranet synchronization tool is generally used for developing projects, but the tools cannot prevent the following situations from happening:
1. accident of wrong uploading
Source code misdelivery events such as the nearest mile application; forgetting comments by the portable database, causing address leakage of the background database, and the like.
2. Newspaper-duplex uploading
Because of the complaint of company, the source code of the company, such as distance carrying and Xinjiang, is directly revealed.
3. Invasion by hacker
For example, the IOS company is hacked to directly open the source code at GIT (the company server is maliciously invaded, and the hacker directly opens the source code to GIT (guitu)) and the guitu account is blasted to cause the private key to be encrypted, so that the luxo bitcoin is obtained.
Aiming at the problems, the existing protection mode is mainly source code encryption, the 1 st type and the 3 rd type accidents can be effectively solved through layer-by-layer management, but the 2 nd type accidents cannot be prevented; for the type of accident, a special cloud server is needed for convenient management, but at the same time, the storage on the GIT/SVN is also unavailable, so that the method is not convenient enough.
Disclosure of Invention
The technical problem to be solved by the invention is as follows: the source code protection method and the storage medium in the project development process are provided, so that source code leakage and hacker attack can be effectively prevented, and the security of the source code is improved; meanwhile, the system has the function of tracing responsibility after leakage.
In order to solve the technical problems, the invention adopts the technical scheme that:
a source code protection method for a project development process comprises the following steps:
generating keys corresponding to all tasks one by one corresponding to all tasks in a project and identity information of a person in charge of the tasks;
acquiring a file data stream of an accessed task by intercepting an application running the task;
acquiring a key corresponding to the accessed task, and encrypting the file data stream by using the acquired key;
generating an encryption identifier uniquely corresponding to the accessed task, and writing the encryption identifier into the encrypted file data stream;
and storing the relationship between the key corresponding to each task in a project and the corresponding encryption identifier.
The invention provides another technical scheme as follows:
a computer-readable storage medium, on which a computer program is stored, which, when executed by a processor, is capable of implementing the steps included in the source code protection method of the project development process.
The invention has the beneficial effects that: aiming at each task in a project, the invention generates a key associated with the identity information of a task responsible person; when accessing a task, encrypting and protecting a file data stream by using a corresponding key, and writing an encryption identifier; and uniformly storing the relation between each task in the project and the key and the encryption identifier. Therefore, the hook of the specific task and the identity information of the responsible person is realized. If the task needs to be accessed, the task can be correctly decrypted according to the legal corresponding identity information, so that illegal attacks can be effectively prevented; after the task source code (file data stream) is illegally revealed, the identity information of a responsible person can be accurately locked by combining the encrypted identifier and the relation efficiently, so that the revealing party can be quickly and accurately traced, and the tracing effect is achieved.
Drawings
FIG. 1 is a flowchart illustrating a source code protection method for a project development process according to an embodiment of the present invention;
fig. 2 is a schematic connection diagram of functional modules corresponding to the method according to the first embodiment of the present invention;
fig. 3 is a flowchart illustrating a method according to a second embodiment of the present invention.
Detailed Description
In order to explain technical contents, achieved objects, and effects of the present invention in detail, the following description is made with reference to the accompanying drawings in combination with the embodiments.
The most key concept of the invention is as follows: the hook for realizing the specific task and the identity information of the responsible person is realized; encrypting the file data stream of the task by using a key corresponding to the task; and storing the relation between each task in the project and the key and the encryption identifier.
The technical terms related to the invention are explained as follows:
referring to fig. 1, the present invention provides a source code protection method in a project development process, including:
generating keys corresponding to all tasks one by one corresponding to all tasks in a project and identity information of a person in charge of the tasks;
acquiring a file data stream of an accessed task by intercepting an application running the task;
acquiring a key corresponding to the accessed task, and encrypting the file data stream by using the acquired key;
generating an encryption identifier uniquely corresponding to the accessed task, and writing the encryption identifier into the encrypted file data stream;
and storing the relationship between the key corresponding to each task in a project and the corresponding encryption identifier.
From the above description, the beneficial effects of the present invention are: the hook of the specific task and the identity information of a responsible person is realized, and illegal attacks can be effectively prevented; the leakage party can be quickly and accurately traced, and the tracing effect is achieved; it is also possible to supervise the completion of the project. The application of the invention can effectively protect the security of enterprise codes and avoid unnecessary direct economic loss caused by accidents.
Further, still include:
acquiring an encryption identifier in the leaked file data stream;
acquiring a corresponding task according to the relation; and acquiring the identity information of the responsible person of the task.
As can be seen from the above description, since the corresponding person in charge of each task is encrypted during the operation process, the task cannot be accessed by the identities other than the person in charge. Therefore, once the source code is leaked, the identity of the leaked person can be quickly and accurately locked only according to the encrypted identification of the source code.
Further, still include:
logging in by using the identity information;
confirming the consistency of the identity information of a responsible person corresponding to the task to be accessed and the currently logged-in identity information;
if the data flow is consistent with the file data flow to be accessed, acquiring an encryption identifier in the file data flow of the task to be accessed;
and acquiring a corresponding key according to the relation, and decrypting the file data stream of the task to be accessed by using the acquired key.
As can be seen from the above description, since the corresponding responsible person of each task is encrypted during the operation process, the identity other than the legal responsible person cannot access the task, thereby realizing the responsibility hook between the task and the responsible person.
Further, still include:
acquiring an encryption identifier in a file data stream of the submitted task;
judging whether the submitted task belongs to the project or not according to the relation;
if not, the submission is refused.
According to the description, the submitted tasks and the projects are corresponding, and the possibility of submitting wrong tasks is effectively eliminated.
Further, still include:
acquiring encryption identifiers in file data streams corresponding to various tasks in the project;
acquiring a key corresponding to each encrypted identifier by traversing the relationship;
calling the acquired keys one by one to decrypt the corresponding file data streams;
and merging the decrypted file data streams of all tasks to obtain the developed project.
According to the description, after all tasks of the project are completed, the tasks are unified and decrypted and then combined, the development of the project is finally completed, and the effective protection is carried out in the whole process of code development.
The invention provides another technical scheme as follows:
a computer-readable storage medium, on which a computer program is stored, which, when executed by a processor, is capable of implementing the steps included in the source code protection method of the project development process.
As can be understood from the above description, those skilled in the art can understand that all or part of the processes in the above technical solutions can be implemented by instructing related hardware through a computer program, where the program can be stored in a computer-readable storage medium, and when executed, the program can include the processes of the above methods. The program can also realize the beneficial effects that can be realized by the corresponding method after being executed.
The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like.
Example one
The embodiment provides a source code protection method in a project development process, which can effectively protect codes in a development stage aiming at various tasks in a large project and has a responsibility tracing function after source codes are leaked.
In a specific example, the functional module composition and connection relationship corresponding to the method of this embodiment are as shown in fig. 2, the master control module, the task module, the key module, the encryption module and the execution module are sequentially connected, and the integration module is respectively connected with the execution module and the task module. The task allocation (the allocation of specific tasks and corresponding responsible persons) is realized through the master control module, and the task module issues the tasks (issues the tasks to the specific responsible persons); generating keys of each task through a key module; the encryption module is used for encrypting, the execution module is used for ensuring the safety of the work content of each task and informing the integration module after the task is finally completed, the integration module is used for recording the work (content) for decrypting each encryption module in the key module and performing resource integration, and a developed project is obtained.
Referring to fig. 1, the method of the present embodiment includes:
s1: and generating a key corresponding to each task one by one corresponding to each task in a project and the identity information of a person in charge of the task.
Specifically, a project generally includes more than two specific tasks, each of which is generally assigned responsibility of a different person. In this embodiment, a key is generated for each task according to the task itself and the identity information of the task responsible person, and therefore the key of each task is associated with both the specific task and the task responsible person.
In one embodiment, the task number and the corresponding identity information of the responsible person under the project can be directly used as the encryption rule.
S2: and acquiring the file data stream of the accessed task by intercepting the application of the running task.
In a specific example, it is first determined whether a currently running device is installed with software (application) specified by a task to be accessed, if the currently running device is corresponding to a programming task, a programming tool similar to Microsoft Visual Studio is installed, and a drawing task is similar to Photoshop and the like; if not, ending the flow; if yes, acquiring and intercepting the operation flow of the task according to software (application) and acquiring the file data stream of the accessed task.
In another embodiment, the step is specifically: opening a designated project by using software, reading/opening/accessing a designated task file in the project, and acquiring a file data stream, namely a source code, corresponding to the currently read/opened/accessed task file by an encryption module by intercepting the running software; and temporarily stores it in the space designated by the cryptographic module.
S3: and acquiring a key corresponding to the accessed task, and encrypting the file data stream by using the acquired key.
In a specific example, the encryption module obtains a key corresponding to the accessed task from the key module, and then encrypts the file data stream corresponding to the task by using the key.
S4: and generating an encryption identifier uniquely corresponding to the accessed task, and writing the encryption identifier into the encrypted file data stream.
In the specific example corresponding to step S3, after encryption, a unique encryption identifier is generated for the encrypted task to identify that the task is encrypted. Preferably, the encryption identifies a 256 byte HASH value generated for the task corresponding to the item.
S5: and storing the relationship between the key corresponding to each task in a project and the corresponding encryption identifier.
Since the encrypted identifier corresponds to the task, which in turn corresponds to the key and the identity information of the person responsible for the task, the relationship actually describes the association of the "project-the specific task-the person responsible-the key-the encrypted identifier".
In one embodiment, the relationship is stored in an integration module.
According to the method, each task is subjected to encryption protection associated with the responsible person during the first operation, so that the corresponding task can be legally read/opened/accessed only by the identity of the legal responsible person, and the task is effectively protected from being illegally attacked and illegally leaked; meanwhile, due to the limitation, once the task source code is illegally leaked, the corresponding responsible person can be efficiently traced, so that the task tracing function is simultaneously realized.
Example two
Referring to fig. 3, the embodiment provides a specific operation process after completion of each task under the project, based on the first embodiment:
s6: acquiring encryption marks in a file data stream corresponding to each task under a specific project;
s7: acquiring a key corresponding to each encrypted identifier by traversing a pre-stored relationship corresponding to the item, namely the relationship stored in step S5;
s8: calling the acquired keys one by one to decrypt the corresponding file data streams;
s9: and merging the decrypted file data streams of all tasks to obtain the developed project.
In one embodiment, the integration of tasks under the project is realized through an integration module, and the integration module is respectively connected with the task module and the execution module.
Specifically, the integration module calls a project, and compares all HASH values recorded in a 'relation' corresponding to the project in the project traversal task module with encryption marks of various tasks under the project according to all HASH values, so as to further judge whether the submitted task belongs to the project, so as to eliminate task content submitted incorrectly.
And after the integration module judges through the encryption identifier, the decryption operation is started, and the file data streams of all tasks in the corresponding project are decrypted one by acquiring all keys in the relation. Specifically, the file data stream to be decrypted is copied into a space temporarily created by the integration module, keys in the 'relationship' of the items to which the file data stream belongs are obtained through traversal according to corresponding tasks (such as task names/numbers), the file data streams to be decrypted are decrypted one by one, the decrypted tasks are stored, and another HASH value is generated again to mark that the tasks are completed. After all the tasks are decrypted, the master control module is informed that the task corresponding to the project is completed, and at this moment, the corresponding decryption identification after the completion of each task is added except the original project identification of the project, the task identification of each task under the project, the key and the encryption identification of each task, so that the completion condition and the state of the project/task can be known through any one identification/key, and the project protection and supervision functions are achieved.
EXAMPLE III
In this embodiment, a detailed description is given for the task source code protection and accountability function, respectively, corresponding to the first embodiment or the second embodiment:
task source code protection
(1) Operation protection
SS 1: logging in by using the identity information and specifying a task to be accessed;
SS 2: confirming the consistency of the identity information of the responsible person corresponding to the task to be accessed and the currently logged-in identity information according to the relationship;
if not, access is refused, and the process is ended;
if the task to be accessed is consistent with the encrypted task, judging whether the task to be accessed is encrypted; if not, acquiring a key corresponding to the task, encrypting the file data stream corresponding to the task by using the acquired key, and generating a corresponding encryption key; if the task is encrypted, acquiring an encryption identifier in a file data stream of the task to be accessed; and then, acquiring a key corresponding to the encrypted identifier according to the relationship, and decrypting the file data stream of the task to be accessed by using the acquired key, thereby realizing the access to the specified task.
Therefore, only the responsible person corresponding to the task is guaranteed to have the right to read/open/access the task, and other people are limited to operate due to illegal identity, so that the source code of the task is effectively prevented from being attacked and stolen.
(II) protection against improper operation
SS 1: acquiring an encryption identifier in a file data stream of a task to be submitted to a certain project of a system;
SS 2: judging whether the submitted task belongs to the project or not according to the relation; if not, refusing to submit; if yes, the submission is completed.
Therefore, the correspondence between the submitted tasks and the projects is ensured, and the fault that the source codes of the tasks are disclosed due to misoperation is avoided.
(III) tracing responsibility after leakage of task source code
When the source code is found to be illegally leaked, tracing responsibility by the following steps:
SS 1: acquiring an encryption identifier in a leaked file data stream (source code);
SS 2: acquiring a corresponding task according to the relation; and acquiring the identity information of the responsible person of the task.
Of course, under the condition that it is known which task the leaked file data stream corresponds to, the identity information of the responsible person corresponding to the task can be directly searched through the task module, and the leakage person can be determined.
Example four
This embodiment corresponds to the first to third embodiments, and provides several specific application scenarios:
scene one
The prior art is as follows: the King is a programmer, and finds that the synchronous source code is wrong on the second day after the code is uploaded to the GitHub carelessly, immediately opens the GitHub, finds that the uploaded code is good for several times, opens the source code by other people with palpitation, and finds that the source code is just like Martian. This process, because other operations are performed in the non-task state, the stored process has been affected by the encryption module, and the displayed content is not consistent with what is actually to be presented.
After the technology of the invention is applied, when the King uploads the code to the GitHub, the GitHub does not have software for processing the task corresponding to the code, namely the task cannot correspond to the operating equipment, and then the uploading of the code, namely the reading/accessing of the code is refused, therefore, the condition of destroying the source code can not occur, and the source code synchronization error is prompted at the beginning of the uploading.
Scene two
The company computer is attacked by worm, and is permeated into the intranet to control one important server (a large amount of source codes stored in the intranet), and a hacker finds that the program codes existing in the company terminal are stolen. However, after applying the technology of the present invention, since each task is encrypted and stored corresponding to a different key, for example, the item a is developed by 4 people, and there are 4 keys corresponding to the item, so that the keys of each task are all not unique, and a hacker cannot steal the source code of the item because he cannot be the owner's 4 different keys. Therefore, the security of the original project is protected, and the security problem caused by the same task and the same key is avoided.
Scene three
The small forest is a person who is emotional, and wants to give way through the source code of the open source program due to leadership and dissatisfaction; after the company finds that the source code is leaked, the company finds that only the key of the forest can release the corresponding content through comparison of the legal department by the key of each task member recorded in the task module, and therefore the fact that the leaked person is the forest is determined.
EXAMPLE five
Corresponding to the first to fourth embodiments, the present embodiment provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor, and is capable of implementing the steps included in the source code protection method for a project development process in any one of the first to fourth embodiments. The detailed steps are not repeated here, and refer to the descriptions of the first to fourth embodiments for details.
In summary, the source code protection method and the storage medium for the project development process provided by the invention can effectively prevent source code leakage and hacker attack, and improve the security of the source code; but also can efficiently and accurately trace responsibility after the source code is leaked; furthermore, the method also has the functions of monitoring the completion condition of the project and preventing misoperation, so that the safety of the source code is better protected.
The above description is only an embodiment of the present invention, and not intended to limit the scope of the present invention, and all equivalent changes made by using the contents of the present specification and the drawings, or applied directly or indirectly to the related technical fields, are included in the scope of the present invention.
Claims (6)
1. A source code protection method for a project development process is characterized by comprising the following steps:
generating keys corresponding to all tasks one by one corresponding to all tasks in a project and identity information of a person in charge of the tasks;
acquiring a file data stream of an accessed task by intercepting an application running the task;
acquiring a key corresponding to the accessed task, and encrypting the file data stream by using the acquired key;
generating an encryption identifier uniquely corresponding to the accessed task, and writing the encryption identifier into the encrypted file data stream;
and storing the relationship between the key corresponding to each task in a project and the corresponding encryption identifier.
2. The method of claim 1, further comprising:
acquiring an encryption identifier in the leaked file data stream;
acquiring a corresponding task according to the relation; and acquiring the identity information of the responsible person of the task.
3. The method of claim 1, further comprising:
logging in by using the identity information;
confirming the consistency of the identity information of a responsible person corresponding to the task to be accessed and the currently logged-in identity information;
if the data flow is consistent with the file data flow to be accessed, acquiring an encryption identifier in the file data flow of the task to be accessed;
and acquiring a corresponding key according to the relation, and decrypting the file data stream of the task to be accessed by using the acquired key.
4. The method of claim 1, further comprising:
acquiring an encryption identifier in a file data stream of the submitted task;
judging whether the submitted task belongs to the project or not according to the relation;
if not, the submission is refused.
5. The method of claim 1, further comprising:
acquiring encryption identifiers in file data streams corresponding to various tasks in the project;
acquiring a key corresponding to each encrypted identifier by traversing the relationship;
calling the acquired keys one by one to decrypt the corresponding file data streams;
and merging the decrypted file data streams of all tasks to obtain the developed project.
6. A computer-readable storage medium having stored thereon a computer program, wherein the program is capable of implementing the steps included in a method for source code protection of a project development process as claimed in any one of claims 1 to 5 when executed by a processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910638648.4A CN112241516B (en) | 2019-07-16 | 2019-07-16 | Source code protection method and storage medium for project development process |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910638648.4A CN112241516B (en) | 2019-07-16 | 2019-07-16 | Source code protection method and storage medium for project development process |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112241516A true CN112241516A (en) | 2021-01-19 |
| CN112241516B CN112241516B (en) | 2023-11-10 |
Family
ID=74166672
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910638648.4A Active CN112241516B (en) | 2019-07-16 | 2019-07-16 | Source code protection method and storage medium for project development process |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112241516B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2015004743A (en) * | 2013-06-19 | 2015-01-08 | 大日本印刷株式会社 | Encryption processing device and information processing apparatus |
| CN106650482A (en) * | 2015-11-04 | 2017-05-10 | 阿里巴巴集团控股有限公司 | Electronic file encryption method and device, electronic file decryption method and device and electronic file encryption and decryption system |
| CN108390759A (en) * | 2018-03-21 | 2018-08-10 | 平安普惠企业管理有限公司 | Code encryption, decryption method, device, computer equipment and storage medium |
| CN109543366A (en) * | 2017-09-22 | 2019-03-29 | 中国移动通信集团浙江有限公司 | A kind of source code encryption method and its device and system |
-
2019
- 2019-07-16 CN CN201910638648.4A patent/CN112241516B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2015004743A (en) * | 2013-06-19 | 2015-01-08 | 大日本印刷株式会社 | Encryption processing device and information processing apparatus |
| CN106650482A (en) * | 2015-11-04 | 2017-05-10 | 阿里巴巴集团控股有限公司 | Electronic file encryption method and device, electronic file decryption method and device and electronic file encryption and decryption system |
| CN109543366A (en) * | 2017-09-22 | 2019-03-29 | 中国移动通信集团浙江有限公司 | A kind of source code encryption method and its device and system |
| CN108390759A (en) * | 2018-03-21 | 2018-08-10 | 平安普惠企业管理有限公司 | Code encryption, decryption method, device, computer equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112241516B (en) | 2023-11-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11126754B2 (en) | Personalized and cryptographically secure access control in operating systems | |
| US7330981B2 (en) | File locker and mechanisms for providing and using same | |
| US20040010701A1 (en) | Data protection program and data protection method | |
| CN110889130B (en) | Database-based fine-grained data encryption method, system and device | |
| CN109643356B (en) | Method and system for preventing phishing or extorting software attacks | |
| CN107508801B (en) | Method and device for preventing file from being tampered | |
| CN109347625B (en) | Password operation method, work key creation method, password service platform and equipment | |
| CN104318176B (en) | Data management method and device for terminal and terminal | |
| CN112417391B (en) | Information data security processing method, device, equipment and storage medium | |
| CN103839011A (en) | Protecting method and device of confidential files | |
| CN113468576B (en) | Role-based data security access method and device | |
| CN104778954B (en) | A kind of CD subregion encryption method and system | |
| CN111475782A (en) | API (application program interface) key protection method and system based on SGX (secure gateway) software extension instruction | |
| KR20070052073A (en) | Digital document preservation system having a share memory for user access function and document transaction method used the system | |
| CN110245464B (en) | Method and device for protecting file | |
| CN114598501A (en) | Data processing method and device based on Internet of things | |
| CN108345804B (en) | Storage method and device in trusted computing environment | |
| CN107273725B (en) | Data backup method and system for confidential information | |
| CN105897730A (en) | User name and password information encryption and verification method | |
| CN112241516A (en) | Source code protection method and storage medium for project development process | |
| CN114218593A (en) | Information security detection method based on office equipment | |
| CN111611587A (en) | Secure data processing apparatus | |
| CN111988274B (en) | Account information verification method and device | |
| CN109255207B (en) | Application program authentication system and authentication method | |
| CN116127501A (en) | User private data protection method, system and medium based on user private container |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |