CN112230889A - Method for making software development coding specification - Google Patents
Method for making software development coding specification Download PDFInfo
- Publication number
- CN112230889A CN112230889A CN202011110839.2A CN202011110839A CN112230889A CN 112230889 A CN112230889 A CN 112230889A CN 202011110839 A CN202011110839 A CN 202011110839A CN 112230889 A CN112230889 A CN 112230889A
- Authority
- CN
- China
- Prior art keywords
- data
- encryption
- decryption
- software development
- server
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 20
- 230000005540 biological transmission Effects 0.000 claims abstract description 32
- 238000011161 development Methods 0.000 claims abstract description 14
- 238000012423 maintenance Methods 0.000 claims abstract description 8
- 238000004519 manufacturing process Methods 0.000 claims description 13
- 230000008569 process Effects 0.000 claims description 8
- 230000008531 maintenance mechanism Effects 0.000 claims description 5
- 238000003860 storage Methods 0.000 claims description 5
- 238000012795 verification Methods 0.000 claims description 5
- 238000006243 chemical reaction Methods 0.000 abstract description 2
- 230000006870 function Effects 0.000 description 5
- 238000013461 design Methods 0.000 description 3
- 238000012360 testing method Methods 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008570 general process Effects 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/10—Requirements analysis; Specification techniques
-
- 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/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Health & Medical Sciences (AREA)
- Bioethics (AREA)
- General Health & Medical Sciences (AREA)
- Storage Device Security (AREA)
Abstract
The invention discloses a method for making a software development coding specification, which comprises the following steps: s1, configuring an environment, namely completing the configuration of the development environment and the running environment required before writing, facilitating function debugging and standardized development; s2, encryption and decryption switching: the method comprises the steps of selecting encryption, entering an encryption state, if selecting decryption, entering a decryption state, encrypting data according to a selected encryption mode, transmitting through a safe network to prevent lawless persons from obtaining plaintext of a data file, performing encryption conversion on the data in a server for multiple times, and performing reverse decryption after another client side obtains the file, so that a data transmission mode of cut-in encryption transmission and decryption acceptance is realized, data transmission is safer, better safety is achieved, the encryption modes are various, a coding specification can be formed during software development, the safety of software is higher, attack and damage of the lawless persons are prevented, and meanwhile, convenience is brought to maintenance of users.
Description
Technical Field
The invention relates to the technical field of software development safety, in particular to a method for making a software development coding specification.
Background
Software development is the process of building a software system or software parts in a system according to user requirements. Software development is a system engineering that includes requirement capture, requirement analysis, design, implementation, and testing. Software is typically implemented in a programming language. Development is typically possible using software development tools. Software is divided into system software and application software, and includes not only programs that can be run on a computer, but files related to these programs are also generally considered to be part of the software. The general process of the software design idea and method includes the algorithm and method for designing the function and implementation of the software, the overall structural design and module design of the software, programming and debugging, program joint debugging and testing, and writing and submitting the program. In the software development process, the purpose of coding specification is to unify specification, facilitate reading and maintenance, improve code quality, unify format, make code measurement more accurate, lay a good foundation for company software process system optimization, and provide a basis for subsequent handover work;
the invention is disclosed in China: CN108768684A discloses a configurable network data transmission method and system, the invention is based on the configurable network data transmission system of the configurable network data transmission method, the method firstly configures the IP and port of the local end and initializes the local configuration table; the local terminal downloads basic data and service data from the server according to the local configuration table; the local terminal operates the basic data and the service data downloaded to the local terminal; the local end uploads the service data to the server according to the uploading condition, and then updates the local service number according to the information returned by the server, however, the data transmission of the invention does not carry out encryption protection according to a standard encryption mode, the data transmission method is that the local data is directly transmitted to the server by using the client, so that the local data is easily attacked by lawbreakers and illegally obtains data, the safety is low, the information loss is easily caused, so that economic loss or other loss is caused, the code needs to be encrypted when the software is written, and the code standard is formed, so that the software can be protected in the subsequent development, therefore, the method for manufacturing the software development code standard is provided.
Disclosure of Invention
The present invention is directed to a method for creating a software development code specification, so as to solve the problems in the background art.
In order to achieve the purpose, the invention provides the following technical scheme: a method of making a software development code specification, comprising the steps of:
s1, configuring an environment, namely completing the configuration of the development environment and the running environment required before writing, facilitating function debugging and standardized development;
s2, encryption and decryption switching: selecting encryption, entering an encryption state, if selecting decryption, entering a decryption state, and encrypting data according to a selected encryption mode: converting the parameter dictionary into a json character string, converting the json character string into a character string encrypted by Base64, encrypting the character string by using a selectable encryption mode after encrypting the Base64, then encrypting the character string again by using Base64, and outputting the final encrypted character string;
s3, coding specifications including a specification private code and a controllable public code and code layering are carried out according to the naming specifications, the annotation principle and the coding style rules when encryption and decryption are switched;
s4, updating the maintenance code table, and forming a maintenance mechanism of the uncontrollable codes in the database;
s5, data transmission: data is transmitted safely by using various network protocols such as HTTP, DNS and TCP/IP; the background server decrypts and receives the data, decrypts and receives the data according to a process opposite to the encryption mode, first decrypts the data by Base64, then judges the type of cut-in encryption, decrypts the data by Base64 to convert the data into json character strings, and finally converts the data into a data dictionary to complete decryption and reception of the data.
As further preferable in the present technical solution: when the password is input and re-input, the current input position is shielded by using a mask mode, so that the password is prevented from being leaked.
As further preferable in the present technical solution: after the password is input and the password is input again, when the JS page judges that the two times of input are consistent, the client only sends the user name to the server for the first time, the server transmits the user name and the generated random number to the client for storage, the client sends data comprising the user name and the random number generated by the server for the second time, and the server verifies the user name and the random number, confirms the uniqueness of the client and finishes the login of the user.
As further preferable in the present technical solution: when data transmission is needed, the encryption state is selected, data content is input, the page converts data returned after the data content is locally encrypted through Base64 into data, and the data is transmitted to the server through verification of random numbers.
As further preferable in the present technical solution: before data transmission is carried out, a JS file of MD5 can be added to a JS folder in a front-end page, data is subjected to MD5 encryption through grammar, the data is converted into random numbers generated by MD5, and the random numbers are converted into data through reverse decryption by a receiving end through MD 5.
As further preferable in the present technical solution: the cut-in encryption mode is one of DES, 3DES, AES, DSA and ECC; DES is a block algorithm using key encryption, 3DES is a DES to AES transitional encryption algorithm that encrypts data three times using 3 keys of 56 bits, AES is an advanced encryption Standard algorithm.
As further preferable in the present technical solution: the cut-in decryption mode is one of DES, 3DES, AES, DSA and ECC cut-in encryption modes in the data correspondingly sent to the server request.
As further preferable in the present technical solution: the network protocol used in data transmission is two or more of HTTP, DNS, TCP/IP.
Compared with the prior art, the invention has the beneficial effects that: according to the invention, after data of a local client is encrypted by using MDS, plaintext acquisition of a data file by a lawless person is prevented through safe network transmission, and uniqueness of connection is ensured through random number matching of a server after encryption, data is subjected to encryption conversion for multiple times in the server, and reverse decryption is performed after another client acquires the file, so that a data transmission mode of cut-in encryption transmission and decryption acceptance is realized, data transmission is safer, better safety is achieved, and the encryption modes are various, and a code specification can be formed during software development, so that the safety of software is higher, attack and damage of the lawless person can be prevented, and convenience is brought to maintenance of a user.
Drawings
FIG. 1 is a flow chart of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Example one
Referring to fig. 1, the present invention provides a technical solution: a method of making a software development code specification, comprising the steps of:
s1, configuring an environment, namely completing the configuration of the development environment and the running environment required before writing, facilitating function debugging and standardized development;
s2, encryption and decryption switching: selecting encryption, entering an encryption state, if selecting decryption, entering a decryption state, and encrypting data according to a selected encryption mode: converting the parameter dictionary into a json character string, converting the json character string into a character string encrypted by Base64, encrypting the character string by using a selectable encryption mode after encrypting the Base64, then encrypting the character string again by using Base64, and outputting the final encrypted character string;
s3, coding specifications including a specification private code and a controllable public code and code layering are carried out according to the naming specifications, the annotation principle and the coding style rules when encryption and decryption are switched;
s4, updating the maintenance code table, and forming a maintenance mechanism of the uncontrollable codes in the database;
s5, data transmission: data is transmitted safely by using various network protocols such as HTTP, DNS and TCP/IP; the background server decrypts and receives the data, decrypts and receives the data according to a process opposite to the encryption mode, first decrypts the data by Base64, then judges the type of cut-in encryption, decrypts the data by Base64 to convert the data into json character strings, and finally converts the data into a data dictionary to complete decryption and reception of the data.
In this embodiment, specifically: when the password is input and re-input, the current input position is shielded by using a mask mode, so that the password is prevented from being leaked.
In this embodiment, specifically: after the password is input and the password is input again, when the JS page judges that the two times of input are consistent, the client only sends the user name to the server for the first time, the server transmits the user name and the generated random number to the client for storage, the client sends data comprising the user name and the random number generated by the server for the second time, and the server verifies the user name and the random number, confirms the uniqueness of the client and finishes the login of the user.
In this embodiment, specifically: when data transmission is needed, the encryption state is selected, data content is input, the page converts data returned after the data content is locally encrypted through Base64 into data, and the data is transmitted to the server through verification of random numbers.
In this embodiment, specifically: before data transmission is carried out, a JS file of MD5 can be added to a JS folder in a front-end page, data is subjected to MD5 encryption through grammar, the data is converted into random numbers generated by MD5, and the random numbers are converted into data through reverse decryption by a receiving end through MD 5.
In this embodiment, specifically: the cut-in encryption mode is preferably DES; DES is a block algorithm using key encryption, 3DES is a DES to AES transitional encryption algorithm that encrypts data three times using 3 keys of 56 bits, AES is an advanced encryption Standard algorithm.
In this embodiment, specifically: the cut-in decryption mode is preferably a corresponding AES advanced encryption Standard algorithm in the data correspondingly sent to the server request.
In this embodiment, specifically: the network protocol used for data transmission is preferably HTTP, DNS, IP.
Example two
Referring to fig. 1, the present invention provides a technical solution: a method of making a software development code specification, comprising the steps of:
s1, configuring an environment, namely completing the configuration of the development environment and the running environment required before writing, facilitating function debugging and standardized development;
s2, encryption and decryption switching: selecting encryption, entering an encryption state, if selecting decryption, entering a decryption state, and encrypting data according to a selected encryption mode: converting the parameter dictionary into a json character string, converting the json character string into a character string encrypted by Base64, encrypting the character string by using a selectable encryption mode after encrypting the Base64, then encrypting the character string again by using Base64, and outputting the final encrypted character string;
s3, coding specifications including a specification private code and a controllable public code and code layering are carried out according to the naming specifications, the annotation principle and the coding style rules when encryption and decryption are switched;
s4, updating the maintenance code table, and forming a maintenance mechanism of the uncontrollable codes in the database;
s5, data transmission: data is transmitted safely by using various network protocols such as HTTP, DNS and TCP/IP; the background server decrypts and receives the data, decrypts and receives the data according to a process opposite to the encryption mode, first decrypts the data by Base64, then judges the type of cut-in encryption, decrypts the data by Base64 to convert the data into json character strings, and finally converts the data into a data dictionary to complete decryption and reception of the data.
In this embodiment, specifically: when the password is input and re-input, the current input position is shielded by using a mask mode, so that the password is prevented from being leaked.
In this embodiment, specifically: after the password is input and the password is input again, when the JS page judges that the two times of input are consistent, the client only sends the user name to the server for the first time, the server transmits the user name and the generated random number to the client for storage, the client sends data comprising the user name and the random number generated by the server for the second time, and the server verifies the user name and the random number, confirms the uniqueness of the client and finishes the login of the user.
In this embodiment, specifically: when data transmission is needed, the encryption state is selected, data content is input, the page converts data returned after the data content is locally encrypted through Base64 into data, and the data is transmitted to the server through verification of random numbers.
In this embodiment, specifically: before data transmission is carried out, a JS file of MD5 can be added to a JS folder in a front-end page, data is subjected to MD5 encryption through grammar, the data is converted into random numbers generated by MD5, and the random numbers are converted into data through reverse decryption by a receiving end through MD 5.
In this embodiment, specifically: the cut-in encryption mode is preferably 3 DES; DES is a block algorithm using key encryption, 3DES is a DES to AES transitional encryption algorithm that encrypts data three times using 3 keys of 56 bits, AES is an advanced encryption Standard algorithm.
In this embodiment, specifically: the cut-in decryption mode is preferably a corresponding AES advanced encryption Standard algorithm in the data correspondingly sent to the server request.
In this embodiment, specifically: the network protocols used in data transmission are HTTP, DNS and TCP.
EXAMPLE III
Referring to fig. 1, the present invention provides a technical solution: a method of making a software development code specification, comprising the steps of:
s1, configuring an environment, namely completing the configuration of the development environment and the running environment required before writing, facilitating function debugging and standardized development;
s2, encryption and decryption switching: selecting encryption, entering an encryption state, if selecting decryption, entering a decryption state, and encrypting data according to a selected encryption mode: converting the parameter dictionary into a json character string, converting the json character string into a character string encrypted by Base64, encrypting the character string by using a selectable encryption mode after encrypting the Base64, then encrypting the character string again by using Base64, and outputting the final encrypted character string;
s3, coding specifications including a specification private code and a controllable public code and code layering are carried out according to the naming specifications, the annotation principle and the coding style rules when encryption and decryption are switched;
s4, updating the maintenance code table, and forming a maintenance mechanism of the uncontrollable codes in the database;
s5, data transmission: data is transmitted safely by using various network protocols such as HTTP, DNS and TCP/IP; the background server decrypts and receives the data, decrypts and receives the data according to a process opposite to the encryption mode, first decrypts the data by Base64, then judges the type of cut-in encryption, decrypts the data by Base64 to convert the data into json character strings, and finally converts the data into a data dictionary to complete decryption and reception of the data.
In this embodiment, specifically: when the password is input and re-input, the current input position is shielded by using a mask mode, so that the password is prevented from being leaked.
In this embodiment, specifically: after the password is input and the password is input again, when the JS page judges that the two times of input are consistent, the client only sends the user name to the server for the first time, the server transmits the user name and the generated random number to the client for storage, the client sends data comprising the user name and the random number generated by the server for the second time, and the server verifies the user name and the random number, confirms the uniqueness of the client and finishes the login of the user.
In this embodiment, specifically: when data transmission is needed, the encryption state is selected, data content is input, the page converts data returned after the data content is locally encrypted through Base64 into data, and the data is transmitted to the server through verification of random numbers.
In this embodiment, specifically: before data transmission is carried out, a JS file of MD5 can be added to a JS folder in a front-end page, data is subjected to MD5 encryption through grammar, the data is converted into random numbers generated by MD5, and the random numbers are converted into data through reverse decryption by a receiving end through MD 5.
In this embodiment, specifically: the cut-in encryption mode is preferably AES; DES is a block algorithm using key encryption, 3DES is a DES to AES transitional encryption algorithm that encrypts data three times using 3 keys of 56 bits, AES is an advanced encryption Standard algorithm.
In this embodiment, specifically: the cut-in decryption mode is preferably a corresponding AES advanced encryption Standard algorithm in the data correspondingly sent to the server request.
In this embodiment, specifically: the network protocol used in data transmission is HTTP and TCP/IP.
Although embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that changes, modifications, substitutions and alterations can be made in these embodiments without departing from the principles and spirit of the invention, the scope of which is defined in the appended claims and their equivalents.
Claims (8)
1. A method of making a software development code specification, comprising the steps of:
s1, configuring an environment, namely completing the configuration of the development environment and the running environment required before writing, facilitating function debugging and standardized development;
s2, encryption and decryption switching: selecting encryption, entering an encryption state, if selecting decryption, entering a decryption state, and encrypting data according to a selected encryption mode: converting the parameter dictionary into a json character string, converting the json character string into a character string encrypted by Base64, encrypting the character string by using a selectable encryption mode after encrypting the Base64, then encrypting the character string again by using Base64, and outputting the final encrypted character string;
s3, coding specifications including a specification private code and a controllable public code and code layering are carried out according to the naming specifications, the annotation principle and the coding style rules when encryption and decryption are switched;
s4, updating the maintenance code table, and forming a maintenance mechanism of the uncontrollable codes in the database;
s5, data transmission: data is transmitted safely by using various network protocols such as HTTP, DNS and TCP/IP; the background server decrypts and receives the data, decrypts and receives the data according to a process opposite to the encryption mode, first decrypts the data by Base64, then judges the type of cut-in encryption, decrypts the data by Base64 to convert the data into json character strings, and finally converts the data into a data dictionary to complete decryption and reception of the data.
2. The method of making a software development coding specification of claim 1, wherein: when the password is input and re-input, the current input position is shielded by using a mask mode, so that the password is prevented from being leaked.
3. The method of making a software development coding specification of claim 1, wherein: after the password is input and the password is input again, when the JS page judges that the two times of input are consistent, the client only sends the user name to the server for the first time, the server transmits the user name and the generated random number to the client for storage, the client sends data comprising the user name and the random number generated by the server for the second time, and the server verifies the user name and the random number, confirms the uniqueness of the client and finishes the login of the user.
4. The method of making a software development coding specification of claim 1, wherein: when data transmission is needed, the encryption state is selected, data content is input, the page converts data returned after the data content is locally encrypted through Base64 into data, and the data is transmitted to the server through verification of random numbers.
5. The method of making a software development coding specification of claim 1, wherein: before data transmission is carried out, a JS file of MD5 can be added to a JS folder in a front-end page, data is subjected to MD5 encryption through grammar, the data is converted into random numbers generated by MD5, and the random numbers are converted into data through reverse decryption by a receiving end through MD 5.
6. The method of making a software development coding specification of claim 1, wherein: the cut-in encryption mode is one of DES, 3DES, AES, DSA and ECC; DES is a block algorithm using key encryption, 3DES is a DES to AES transitional encryption algorithm that encrypts data three times using 3 keys of 56 bits, AES is an advanced encryption Standard algorithm.
7. The method of making a software development coding specification of claim 1, wherein: the cut-in decryption mode is one of DES, 3DES, AES, DSA and ECC cut-in encryption modes in the data correspondingly sent to the server request.
8. The method of making a software development coding specification of claim 1, wherein: the network protocol used in data transmission is two or more of HTTP, DNS, TCP/IP.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011110839.2A CN112230889A (en) | 2020-10-16 | 2020-10-16 | Method for making software development coding specification |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011110839.2A CN112230889A (en) | 2020-10-16 | 2020-10-16 | Method for making software development coding specification |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112230889A true CN112230889A (en) | 2021-01-15 |
Family
ID=74118805
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011110839.2A Pending CN112230889A (en) | 2020-10-16 | 2020-10-16 | Method for making software development coding specification |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112230889A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112788051A (en) * | 2021-01-25 | 2021-05-11 | 高新兴讯美科技股份有限公司 | Https dynamic encryption transmission method |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101277192A (en) * | 2008-04-25 | 2008-10-01 | 华为技术有限公司 | Method and system for checking client terminal |
| CN102202067A (en) * | 2011-07-15 | 2011-09-28 | 席勇良 | Dynamic random cipher registration method |
| CN102255914A (en) * | 2011-07-19 | 2011-11-23 | 河南大学 | Android network application program information verification method |
| CN105208024A (en) * | 2015-09-22 | 2015-12-30 | 深圳市金溢科技股份有限公司 | Safe data transmission method and system adopting no HTTPS, client and server |
| CN106095446A (en) * | 2016-06-14 | 2016-11-09 | 深圳市彬讯科技有限公司 | Software source code on-line detecting system and detection method thereof |
| CN106599702A (en) * | 2016-12-08 | 2017-04-26 | 武汉斗鱼网络科技有限公司 | File encryption/decryption method and device |
| CN109347835A (en) * | 2018-10-24 | 2019-02-15 | 苏州科达科技股份有限公司 | Information transferring method, client, server and computer readable storage medium |
| CN109508204A (en) * | 2018-11-15 | 2019-03-22 | 四川长虹电器股份有限公司 | A kind of front-end code quality determining method and device |
| CN109614079A (en) * | 2018-11-21 | 2019-04-12 | 中国航空无线电电子研究所 | A kind of coding rule inspection system towards avionics field |
| CN110198295A (en) * | 2018-04-18 | 2019-09-03 | 腾讯科技（深圳）有限公司 | Safety certifying method and device and storage medium |
| CN110750252A (en) * | 2019-09-30 | 2020-02-04 | 上海紫金信息技术有限公司 | Software development control method, software development equipment and storage medium |
| CN111625230A (en) * | 2020-05-19 | 2020-09-04 | 北京计算机技术及应用研究所 | System for unifying front-end JavaScript coding specifications |
-
2020
- 2020-10-16 CN CN202011110839.2A patent/CN112230889A/en active Pending
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101277192A (en) * | 2008-04-25 | 2008-10-01 | 华为技术有限公司 | Method and system for checking client terminal |
| CN102202067A (en) * | 2011-07-15 | 2011-09-28 | 席勇良 | Dynamic random cipher registration method |
| CN102255914A (en) * | 2011-07-19 | 2011-11-23 | 河南大学 | Android network application program information verification method |
| CN105208024A (en) * | 2015-09-22 | 2015-12-30 | 深圳市金溢科技股份有限公司 | Safe data transmission method and system adopting no HTTPS, client and server |
| CN106095446A (en) * | 2016-06-14 | 2016-11-09 | 深圳市彬讯科技有限公司 | Software source code on-line detecting system and detection method thereof |
| CN106599702A (en) * | 2016-12-08 | 2017-04-26 | 武汉斗鱼网络科技有限公司 | File encryption/decryption method and device |
| CN110198295A (en) * | 2018-04-18 | 2019-09-03 | 腾讯科技（深圳）有限公司 | Safety certifying method and device and storage medium |
| CN109347835A (en) * | 2018-10-24 | 2019-02-15 | 苏州科达科技股份有限公司 | Information transferring method, client, server and computer readable storage medium |
| CN109508204A (en) * | 2018-11-15 | 2019-03-22 | 四川长虹电器股份有限公司 | A kind of front-end code quality determining method and device |
| CN109614079A (en) * | 2018-11-21 | 2019-04-12 | 中国航空无线电电子研究所 | A kind of coding rule inspection system towards avionics field |
| CN110750252A (en) * | 2019-09-30 | 2020-02-04 | 上海紫金信息技术有限公司 | Software development control method, software development equipment and storage medium |
| CN111625230A (en) * | 2020-05-19 | 2020-09-04 | 北京计算机技术及应用研究所 | System for unifying front-end JavaScript coding specifications |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112788051A (en) * | 2021-01-25 | 2021-05-11 | 高新兴讯美科技股份有限公司 | Https dynamic encryption transmission method |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109150499B (en) | Method and device for dynamically encrypting data, computer equipment and storage medium | |
| CN100581103C (en) | Securely processing of client credentials used for WEB-based access to resources | |
| RU2506637C2 (en) | Method and device for verifying dynamic password | |
| CN103051628A (en) | Method and system for obtaining authentication token based on servers | |
| CN107872447A (en) | Electronic device, server, communication system and communication method | |
| CN103888292A (en) | Tool and method for operation and maintenance of distribution terminal | |
| JP4994752B2 (en) | Information processing system | |
| CN110912877B (en) | Data transmitting and receiving method and device based on IEC61850 model in transformer substation | |
| CN111181912B (en) | Browser identifier processing method and device, electronic equipment and storage medium | |
| CN105580312A (en) | Method and system for authenticating a user of a device | |
| CN115695051B (en) | Data center transmission management system based on remote network platform architecture | |
| CN110737884A (en) | cross-platform terminal authorization management method and system | |
| CN106603579A (en) | Remote control system and method of wireless terminal, and wireless terminal | |
| CN112560003A (en) | User authority management method and device | |
| CN103716280A (en) | Data transmission method, server and system | |
| CN104683111A (en) | Encryption method and system based on MD5 | |
| CN104869570A (en) | Speaking terminal confirmation method based on language channel | |
| CN112230889A (en) | Method for making software development coding specification | |
| KR101952641B1 (en) | Location based multi-channel login authentication method in a cloud environments | |
| CN111431935B (en) | Method for identifying data transmission security of website login password | |
| CN104994107A (en) | MMS message off-line analysis method based on IEC62351 | |
| CN111489462A (en) | Personal Bluetooth key system | |
| KR20100014995A (en) | The security technology of internet on encrypted transmission data | |
| CN110830431A (en) | SQL Server database password hosting method | |
| CN108243172B (en) | Method and system for sending verification information |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210115 |