CN102684877A - Method and device for carrying out user information processing - Google Patents

Abstract

The invention provides a method and device for processing user information. The method includes: receiving a request for encrypting user information; obtaining a corresponding encryption key according to the current login status of the user; encrypting the user information according to the encryption key; encoding the encrypted data, and converting the encoded The final data is saved as the first encrypted data. The invention can improve the security of user data.

Description

A method and device for processing user information

technical field

The present application relates to the field of data security, in particular to a method for processing user information and a device for processing user information.

Background technique

The Internet is an open system through which anyone can share their own resources and obtain the information they need. When people exchange information on the Internet, such as sending and receiving emails, or logging in to sites that require personal information, these information packets containing important personal data are likely to be intercepted and cracked by a third party before reaching the final destination.

Base64 is one of the most common encryption methods on the Internet. First, convert each character of the text to be encrypted into a standard ASCII decimal code, and then convert it into a binary string according to the conversion table and divide it into 6-digit groups. The corresponding conversion table is converted into an equivalent decimal number, and finally converted into Base64 encoding through the Base64 table. After Base64 encoding, the probability of the original characters appearing is changed, and the data encoding is changed into characters that cannot be recognized by the naked eye, which is unreadable, thereby ensuring the security of the transmitted data.

Base64 is often used in web servers to complete HTTP-based basic authentication. When the server wants to restrict access to certain files, these files can be password protected by using the HTTP-based basic authentication system. Basic authentication uses the Base64 encoding standard to encrypt usernames and passwords. In this way, when hackers use TCP to connect to the ESMTP server through the port, the amount of manual input will be greatly increased. Additionally, most email clients use Base64 to encode files for transmission over the network.

The problem with the above prior art is that, due to the simplicity of the Base64 encryption process, once it is identified, it can be decrypted only through a very simple reverse algorithm, that is, the Base64 encrypted data is converted into decimal, and then converted into binary code through calculation. Divide the binary code into 6-bit 1 group, get the decimal code, and finally equivalent to the corresponding ASCII code. Therefore, the security of encrypted data using Base64 cannot be reliably guaranteed.

Therefore, a technical problem that needs to be solved by those skilled in the art is to provide a mechanism for processing user information to improve the security of user data.

Contents of the invention

The technical problem to be solved in this application is to provide a method for processing user information to improve the security of user data.

The present application also provides a device for processing user information, so as to ensure the practical application and realization of the above method.

In order to solve the above problems, this application discloses a method for processing user information, including:

Receive a request to encrypt user information;

Obtain the corresponding encryption key according to the user's current login status;

encrypting the user information according to the encryption key;

The encrypted data is encoded, and the encoded data is stored as the first encrypted data.

Preferably, the method further comprises:

Generate a decryption request, and obtain a corresponding decryption key and the first encrypted data according to the current login status of the user;

decoding the first encrypted data;

Decrypt the decoded data according to the decryption key;

According to the decrypted data, automatic login or automatic registration is performed.

Preferably, the user information includes user login information or user identity information.

Preferably, the algorithm for encrypting/decrypting the user information according to the encryption/decryption key is a symmetric algorithm.

Preferably, the first encrypted data is stored locally in the browser or on the server side.

Preferably, the step of obtaining the corresponding encryption key according to the user's current login status includes:

If the user does not log in to the browser, the client extracts a local key as an encryption key, and the local key is generated according to hardware parameters corresponding to the user equipment one by one;

If the user has logged into the browser, the network key is extracted on the server side as the encryption key.

Preferably, when the user has logged into the browser, the encryption key further includes a local key, then

Before encrypting user information according to the encryption key, the method further includes:

Encrypting the user information according to the local key;

The data encrypted by the local key is encoded.

Preferably, the step of obtaining the corresponding decryption key according to the current login status of the user includes:

If the user does not log in to the browser, the client extracts the local key as the decryption key, and the local key is generated according to the hardware parameters corresponding to the user equipment one by one;

If the user has logged into the browser, the network key is extracted on the server side as the decryption key.

Preferably, when the user has logged into the browser, the decryption key further includes a local key, then

After decrypting the decoded data according to the network key, the method further includes:

Decoding the data decrypted according to the network key;

Decrypt according to the local key.

Preferably, when the user is logged in and when the user is not logged in, the first encrypted data is stored in the network user encrypted database and the public user encrypted database respectively.

Preferably, when the user's login status on the browser side changes from non-login to login, the method further includes:

Extract the local key, the first encrypted data of the user in the public user database and the network key, decrypt the first encrypted data with the local key, encrypt the decrypted data with the network key, and save it in the network user database.

Preferably, when the user's login status on the browser side changes from non-login to login, the method further includes:

Extracting the user's first encrypted data and the network key in the public user database, using the network key to encrypt the user's first encrypted data, and saving it in the network user database.

Preferably, the symmetric algorithm is AES64, AES128, or AES256 algorithm.

Preferably, the encoding/decoding algorithm is Base64 encoding/decoding.

The present application also provides a device for processing user information, including:

An encryption request receiving module, configured to receive a request for encrypting user information;

The encryption key acquisition module is used to obtain the corresponding encryption key according to the current login status of the user;

An encryption module, configured to encrypt the user information according to the encryption key;

The encoding module is configured to encode the encrypted data, and save the encoded data as the first encrypted data.

Preferably, the device further comprises:

A decryption request generation module, configured to generate a decryption request, and obtain a corresponding decryption key and the first encrypted data according to the current login status of the user;

a decoding module, configured to decode the first encrypted data;

A decryption module, configured to decrypt the decoded data according to the decryption key;

The automatic loading module module is used for performing automatic login or automatic registration according to the decrypted data.

Preferably, the user information includes user login information or user identity information.

Preferably, the algorithm for encrypting/decrypting the user information according to the encryption/decryption key is a symmetric algorithm.

Preferably, the first encrypted data is stored locally in the browser or on the server side.

Preferably, the encryption key acquisition module includes:

The first encryption key acquisition submodule is used to extract a local key as an encryption key at the client if the user does not log in to the browser, and the local key is generated according to hardware parameters corresponding to the user equipment one-to-one;

The second encryption key acquisition sub-module is used to extract the network key on the server side as the encryption key if the user has logged in the browser.

Preferably, when the user logs into the browser, the encryption key further includes a local key, then

Before the encryption module, the device also includes:

a local encryption module, configured to encrypt the user information according to the local key;

The local encrypted data encoding module is used to encode the data encrypted by the local key.

Preferably, the decryption request generation module includes:

The first decryption key acquisition submodule is used to extract a local key as a decryption key at the client if the user does not log in to the browser, and the local key is generated according to hardware parameters corresponding to the user equipment one-to-one;

The second decryption key acquisition submodule is used to extract the network key as the decryption key at the server side if the user has logged in the browser.

Preferably, when the user logs into the browser, the encryption key further includes a local key, then

After the decryption module, the device also includes:

The local decoding module is used to decode the data decrypted according to the network key;

The local decryption module is used for decrypting according to the local key.

Preferably, when the user is logged in and when the user is not logged in, the first encrypted data is stored in the network user encrypted database and the public user encrypted database respectively.

Preferably, when the login status of the user on the browser side changes from non-login to login, the device further includes:

The first data transfer module is used to extract the local key, the first encrypted data of the user in the public user database and the network key, decrypt the final encrypted data by the local key, and use the network key to decrypt the decrypted data Encrypted and stored in the network user database.

Preferably, when the login status of the user on the browser side changes from non-login to login, the device further includes:

The second data transfer module is used to extract the user's first encrypted data and network key in the public user database, use the network key to encrypt the user's final encrypted data, and save it in the network user database.

Preferably, the symmetric algorithm is AES64, AES128, or AES256 algorithm.

Preferably, the encoding/decoding algorithm is Base64 encoding/decoding.

Compared with the prior art, the present application has the following advantages:

This application uses a local key or a network key to encrypt whether the user logs in to the browser or not. First, the data to be encrypted is converted into random data through the AES encryption method, and then the random data is encoded with Base64 to convert it into a file that cannot be recognized by the naked eye. Compared with simple Base64 encryption, hackers need to analyze the decryption sequence and perform secondary decryption, which greatly increases the difficulty. Therefore, the encryption method of the present application can enhance data security, so that hackers cannot easily decrypt data.

Since the network key is stored on the server side and downloaded locally via network request, it is more secure than the local key and avoids the leakage of the password due to the instability of the client. In this way, even if the hacker knows the order of decryption, if there is no After obtaining the network key, it still cannot be decrypted. Moreover, since the encryption methods of the logged-in user and the logged-in user are different, it is also difficult for hackers to crack.

At the same time, for logged-in users, you can first perform AES encryption and Base64 encryption with the local key, and then perform AES encryption and Base64 encryption with the network key. The encryption logic is more complicated, and it is more difficult to crack. Data will also be more secure.

In addition, this application puts the encrypted data of the logged-in user on the server side, and the encrypted data is more secure. Moreover, when the user's login status changes, the encryption method and encrypted data storage location will be changed accordingly. If the user changes from non-login to login, the network key can be used for encryption, and the encrypted data will be placed on the server side. User data is more secure.

Description of drawings

FIG. 1 is a flow chart of Embodiment 1 of a method for processing user information of the present application;

FIG. 2 is a flow chart of Embodiment 2 of a method for processing user information of the present application;

FIG. 3 is a structural block diagram of Embodiment 1 of a device for processing user information of the present application;

FIG. 4 is a structural block diagram of Embodiment 2 of an apparatus for processing user information of the present application.

Detailed ways

In order to make the above objects, features and advantages of the present application more obvious and comprehensible, the present application will be further described in detail below in conjunction with the accompanying drawings and specific implementation methods.

Referring to FIG. 1 , it shows a flow chart of Embodiment 1 of a method for processing user information of the present application, which may include the following steps:

Step 101. Receive a request for encrypting user information.

In a specific implementation, the user information may include user login information or user identity information.

Step 102. Obtain a corresponding encryption key according to the current login status of the user.

The encryption key may comprise a local key or a network key. After the user logs in, the identity information can be obtained, so different users can be distinguished. The network key is a key randomly generated on the network side and bound to the current user identity information. If the user has logged in to the browser, the server side Extract the network key as the encryption key. Since the network key is stored in the server and downloaded locally through a network request, for the logged-in user, the password is stored on the server, which reduces the risk of being uncontrollable from the client and is more secure than the local key. In a specific implementation, it can be set that the user can obtain the network key after logging in. If the key can be obtained, it will be encrypted with the network key, and if it cannot be obtained, it will be encrypted with the local key.

The identity of each user who has not logged in to the browser cannot be distinguished on the network side, and the local key can be used as the encryption key. The local key is generated according to the hardware parameters corresponding to the user equipment (such as the volume label of the local disk), and each machine has a local key corresponding to the machine, and the keys of different machines are different from each other.

Different encryption methods are adopted for logged-in users and non-logged-in users, which can increase the difficulty for hackers to crack. Even if hackers know the decryption sequence, if they do not obtain the network key, they still cannot decrypt.

Step 103, encrypting the user information according to the encryption key;

Encryption using an encryption key is a simple and effective encryption method for information exchange and transmission on the Internet. Before the information is sent, the data needs to be rearranged and combined according to the rules, which disrupts the original data sequence, so that even if the data packet is intercepted by a third party, it will not affect the security of the data. Preferably, the algorithm for encrypting the user information according to the encryption key may be a symmetric algorithm, and the symmetric algorithm may be an AES64, AES128, or AES256 algorithm.

AES (Advanced Encryption Standard, Advanced Encryption Standard), also known as Rijndael encryption method, is a block encryption standard adopted by the US federal government. AES is a symmetric key algorithm that uses 128, 192, or 256-bit keys and encrypts and decrypts data in blocks of 128 bits. In this application, the AES encryption may be AES64, AES128, or AES256 encryption.

When AES encrypts, it often uses a key on the client side and uses this key for encoding. The AES encryption process operates on a 4×4 byte matrix, which is also called "state", and its initial value is a plaintext block (the size of an element in the matrix is a Byte in the plaintext block ). When encrypting, each round of AES encryption cycle (except the last round) consists of 4 steps:

Step 1. Each byte in the matrix is XORed with the round key (Round key), and each key is generated by the key generation scheme;

Step 2. Through a non-linear replacement function, each byte is replaced with the corresponding byte in the form of a lookup table, and the result of replacing the byte is equivalent to the result of misalignment;

Step 3, performing circular shift on each row in the matrix, after this step, each vertical column in the output matrix is composed of elements in each different column in the input matrix;

Step 4. In order to fully mix each column in the matrix, this step uses a linear transformation to mix the four bytes in each row, and combines the four bytes in each column with each other through a linear transformation. Each input byte will be The four bytes of output make the difference.

The above 4 steps are carried out cyclically. In the last cycle, step 4 is omitted and replaced by another step 3. After AES encryption, the data to be encrypted can be changed into a piece of random data.

Step 104, encode the encrypted data, and save the encoded data as first encrypted data.

Preferably, the encoding algorithm can be Base64 encoding. After Base64 encoding, the AES-encrypted data is first converted into ASCII decimal code, then converted into a 6-digit binary string, then converted into decimal according to the corresponding conversion table, and finally converted into Base64 code through the Base64 table. As shown in the example below.

The data to be converted is: 10101101 10111010 01110110;

Binary is: 0010101 100011011 00101001 00110110;

Decimal is: 43 27 41 54;

Base64 encoded value: r b p 2;

Therefore, the encoded Base64 value of the above 24-bit data to be encoded is rbp2, and the original data cannot be recognized by the naked eye. Moreover, compared with the simple Base64 encryption, the encryption method of the present application decrypts the data twice, and the difficulty of decryption is greatly increased. Therefore, the encryption method of the present application can enhance data security, so that hackers cannot easily decrypt data.

Preferably, the encrypted data may also be decrypted according to the user's decryption request, as shown in FIG. 1 , the method may further include step 105 .

Step 105: Generate a decryption request, and obtain a corresponding decryption key and the first encrypted data according to the current login status of the user.

When the browser needs to use the user information, it needs to decrypt the user's first encrypted data, and the decryption key is different depending on the user's current login status. Specifically, if the user does not log in to the browser, a local key is extracted at the client as a decryption key, and the local key is generated according to hardware parameters corresponding to the user equipment one-to-one. If the user has logged into the browser, the network key is extracted on the server side as the decryption key.

Step 106. Decode the first encrypted data.

According to the above encryption process, the first encrypted data needs to be decoded first, and then decrypted according to the decryption key. Preferably, the decoding algorithm can be Base64 decoding.

Step 107, decrypting the decoded data according to the decryption key;

If a symmetric algorithm is used to encrypt data, the key used for encryption needs to be used for decryption. Preferably, the symmetric algorithm is AES64, AES128, or AES256 algorithm.

Step 108, perform automatic login or automatic registration according to the decrypted data.

After decrypting the user information, it can be used for login or registration. In the specific implementation, after the user enters the password on the webpage, the user can be provided with the option of whether to log in automatically. After the user confirms that the next automatic login is performed, the user login information can be encrypted. When the user logs in to the same webpage next time, the user password The encrypted login information is decrypted, and then the decrypted login information is automatically filled in the login box to realize automatic login.

Similarly, when a user registers with multiple websites, they may need to fill in multiple identity information, which is troublesome. After the user fills in the identity information on a website or browser, the identity information can be encrypted, and the user needs to fill in the identity information next time. When sending information, the encrypted identity letter can be taken out and decrypted, and the decrypted identity information can be automatically filled in the registration box to realize automatic registration.

Preferably, the first encrypted data can be stored locally in the browser or on the server side. When the user is logged in and not logged in, the first encrypted data may be stored in a preset network user encrypted database and a public user encrypted database respectively. After the encryption process is completed, the final encrypted data of the logged-in user can be placed in the network user encryption database, which is used by the logged-in user, and the password is stored in the exclusive folder of each network user; the final encrypted data of the non-logged-in user The data can be placed in the public user encrypted database, which is used by non-login users, and the password is stored in the private folder of the local public user.

When the user's login status on the browser side changes from non-login to login, the user's encryption method can also be changed accordingly, and the database in which the final encrypted data is stored can also be changed. Specifically, the local key, the first encrypted data of the user in the public user database and the network key may be extracted, the first encrypted data is decrypted by the local key, and the decrypted data is encrypted using the network key, And save in the network user database.

Referring to FIG. 2 , it shows a flow chart of Embodiment 2 of a method for processing user information of the present application, which may specifically include the following steps:

In this embodiment, the user has logged into the browser, and the encryption key includes a local key and a network key, and encryption may also be performed based on the local key before encryption based on the network key.

Step 201, receiving a request for encrypting user information;

Step 202. Obtain a corresponding encryption key according to the current login status of the user, and the encryption key includes a local key and a network key;

Step 203, encrypt user information according to the local key.

Step 204, encode the data encrypted by the local key.

Step 205, encrypting according to the network key;

Step 206: Encode the data encrypted by the network key, and store the encoded data as first encrypted data.

According to this embodiment, for logged-in users, AES encryption can be performed with a local key first, and then encryption and encoding can be performed with a network key. After the local encryption, another encryption can be performed. Compared with the original encryption method based on the network key, the encryption logic is more complicated, it is more difficult to crack, and the user's data will be more secure.

Step 207: Generate a decryption request, and obtain a corresponding decryption key and the first encrypted data according to the current login status of the user, where the decryption key includes a local key and a network key.

In this embodiment, when decrypting the first encrypted data, if the user has logged into the browser, the decryption key may include a local key and a network key, and the network key may be used to decrypt first, and then the local key may be used to decrypt key to decrypt, and before local decryption, it can also be decoded first.

Step 208: Decode the first encrypted data.

Step 209, decrypting the decoded data according to the network key;

Step 210, decoding the data decrypted according to the network key;

Step 211, decrypt according to the local key.

Step 212, perform automatic login or automatic registration according to the decrypted data.

To sum up, this application uses a local key or a network key to encrypt whether the user logs in to the browser or not. First, the data to be encrypted is converted into random data through the AES encryption method, and then the random data is encoded with Base64. Converted to data that cannot be recognized by the naked eye. Compared with simple Base64 encryption, hackers need to analyze the decryption sequence and perform secondary decryption, which greatly increases the difficulty. Therefore, the encryption method of the present application can enhance data security, so that hackers cannot easily decrypt data.

Since the network key is stored on the server side and downloaded locally via network request, it is more secure than the local key and avoids the leakage of the password due to the instability of the client. In this way, even if the hacker knows the order of decryption, if there is no After obtaining the network key, it still cannot be decrypted. Moreover, since the encryption methods of the logged-in user and the logged-in user are different, it is also difficult for hackers to crack.

At the same time, for logged-in users, you can first perform AES encryption and Base64 encryption with the local key, and then perform AES encryption and Base64 encryption with the network key. The encryption logic is more complicated, and it is more difficult to crack. Data will also be more secure.

In addition, this application puts the encrypted data of the logged-in user on the server side, and the encrypted data is more secure. Moreover, when the user's login status changes, the encryption method and encrypted data storage location will be changed accordingly. If the user changes from non-login to login, the network key can be used for encryption, and the encrypted data will be placed on the server side. User data is more secure.

For the method embodiment, for the sake of simple description, it is expressed as a series of action combinations, but those skilled in the art should know that the application is not limited by the described action sequence, because according to the application, certain steps Other sequences or concurrently may be used. Secondly, those skilled in the art should also know that the embodiments described in the specification belong to preferred embodiments, and the actions and modules involved are not necessarily required by this application.

Referring to FIG. 3 , it shows a structural block diagram of Embodiment 1 of an apparatus for processing user information of the present application, which may specifically include the following modules:

An encryption request receiving module 301, configured to receive a request for encrypting user information;

An encryption key acquisition module 302, configured to acquire a corresponding encryption key according to the current login status of the user;

An encryption module 303, configured to encrypt the user information according to the encryption key;

The encoding module 304 is configured to encode the encrypted data, and save the encoded data as first encrypted data.

Preferably, the encrypted data may also be decrypted according to the user's decryption request. As shown in FIG. 3 , the device may further include a module 305 .

A decryption request generating module 305, configured to generate a decryption request, and obtain a corresponding decryption key and the first encrypted data according to the current login status of the user;

a decoding module 306, configured to decode the first encrypted data;

Decryption module 307, configured to decrypt the decoded data according to the decryption key;

The automatic loading module module 308 is used for performing automatic login or automatic registration according to the decrypted data.

Preferably, the user information may include user login information or user identity information.

Preferably, the algorithm for encrypting/decrypting the user information according to the encryption/decryption key may be a symmetric algorithm.

Further, the first encrypted data may be stored locally in the browser or on the server side.

In a preferred embodiment of the present application, the encryption key acquisition module may include:

The first encryption key acquisition submodule is used to extract a local key as an encryption key at the client if the user does not log in to the browser, and the local key is generated according to hardware parameters corresponding to the user equipment one-to-one;

The second encryption key acquisition sub-module is used to extract the network key on the server side as the encryption key if the user has logged in the browser.

In a preferred embodiment of the present application, the decryption request generating module may include:

The first decryption key acquisition submodule is used to extract a local key as a decryption key at the client if the user does not log in to the browser, and the local key is generated according to hardware parameters corresponding to the user equipment one-to-one;

The second decryption key acquisition submodule is used to extract the network key as the decryption key at the server side if the user has logged in the browser.

In a preferred embodiment of the present application, when the user is logged in and when the user is not logged in, the first encrypted data can be stored in the network user encrypted database and the public user encrypted database respectively.

Preferably, when the user's login status on the browser changes from non-login to login, the device may further include:

The first data transfer module is used to extract the local key, the first encrypted data of the user in the public user database and the network key, decrypt the final encrypted data by the local key, and use the network key to decrypt the decrypted data Encrypted and stored in the network user database.

Preferably, the symmetric algorithm may be AES64, AES128, or AES256 algorithm. The encoding/decoding algorithm may be Base64 encoding/decoding.

Referring to FIG. 4 , it shows a structural block diagram of Embodiment 2 of an apparatus for processing user information of the present application, which may specifically include the following modules:

In this embodiment, the user has logged into the browser, and the encryption key includes a local key and an encryption key. The local key may be used for encryption first, and then the network key for encryption.

An encryption request receiving module 401, configured to receive a request for encrypting user information;

An encryption key acquisition module 402, configured to acquire a corresponding encryption key according to the current login status of the user;

A local encryption module 403, configured to encrypt the user information according to the local key;

The local encrypted data encoding module 404 is configured to encode the data encrypted by the local key.

A network encryption module 405, configured to encrypt the user information according to the network key;

The network encrypted data encoding module 406 is configured to encode the network encrypted data, and save the encoded data as the first encrypted data.

In this embodiment, when decrypting the first encrypted data, if the user has logged into the browser, the decryption key may include a local key and a network key, and the network key may be used to decrypt first, and then the local key may be used to decrypt key to decrypt, and before local decryption, it can also be decoded first.

A decryption request generating module 407, configured to generate a decryption request, and obtain a corresponding decryption key and the first encrypted data according to the current login status of the user;

A network decoding module 408, configured to decode the first encrypted data;

A network decryption module 409, configured to decrypt the decoded data according to the network key;

The local decoding module 410 is used to decode the data decrypted according to the network key;

The local decryption module 411 is configured to decrypt according to the local key.

The automatic loading module module 412 is used for performing automatic login or automatic registration according to the decrypted data.

Preferably, when the user's login status on the browser side changes from non-login to login, the device may further include:

The second data transfer module is used to extract the user's first encrypted data and network key in the public user database, use the network key to encrypt the user's final encrypted data, and save it in the network user database.

Since the device embodiment basically corresponds to the method embodiment shown in Figure 1 and Figure 2 above, for details not described in this embodiment, you can refer to the relevant description in the previous embodiment, and will not go into details here .

The application can be used in numerous general purpose or special purpose computing system environments or configurations. Examples: personal computers, server computers, handheld or portable devices, tablet-type devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, including A distributed computing environment for any of the above systems or devices, etc.

This application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including storage devices.

As used herein, the terms "comprises," "comprises," or any other variation thereof are intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus that includes a set of elements includes not only those elements, but also includes not expressly included other elements listed, or also include elements inherent in such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article or apparatus comprising said element.

A method for processing user information and a device for processing user information provided by this application have been introduced in detail above. This article uses specific examples to illustrate the principle and implementation of this application. The above examples The description is only used to help understand the method of the present application and its core idea; at the same time, for those of ordinary skill in the art, according to the idea of the present application, there will be changes in the specific implementation and application scope. In summary, As stated above, the contents of this specification should not be construed as limiting the application.

Claims (28)

1. A method for processing user information, comprising: Receive a request to encrypt user information; Obtain the corresponding encryption key according to the user's current login status; encrypting the user information according to the encryption key; The encrypted data is encoded, and the encoded data is stored as the first encrypted data. 2. The method of claim 1, further comprising: Generate a decryption request, and obtain a corresponding decryption key and the first encrypted data according to the current login status of the user; decoding the first encrypted data; Decrypt the decoded data according to the decryption key; According to the decrypted data, automatic login or automatic registration is performed. 3. The method according to claim 1, wherein the user information comprises user login information or user identity information. 4. The method according to claim 2, wherein the algorithm for encrypting/decrypting the user information according to the encryption/decryption key is a symmetric algorithm. 5. The method according to claim 1, characterized in that, further, the first encrypted data is stored locally in the browser or on the server side. 6. The method according to claim 1, wherein the step of obtaining the corresponding encryption key according to the current login status of the user comprises: If the user does not log in to the browser, the client extracts a local key as an encryption key, and the local key is generated according to hardware parameters corresponding to the user equipment one by one; If the user has logged into the browser, the network key is extracted on the server side as the encryption key. 7. The method according to claim 6, wherein when the user has logged into the browser, the encryption key further includes a local key, then Before encrypting user information according to the encryption key, the method further includes: Encrypting the user information according to the local key; The data encrypted by the local key is encoded. 8. The method according to claim 2, wherein the step of obtaining the corresponding decryption key according to the current login status of the user comprises: If the user does not log in to the browser, the client extracts the local key as the decryption key, and the local key is generated according to the hardware parameters corresponding to the user equipment one by one; If the user has logged into the browser, the network key is extracted on the server side as the decryption key. 9. The method according to claim 8, wherein when the user has logged into the browser, the decryption key further comprises a local key, then After decrypting the decoded data according to the network key, the method further includes: Decoding the data decrypted according to the network key; Decrypt according to the local key. 10. The method according to claim 6 or 8, wherein when the user is logged in and when the user is not logged in, the first encrypted data is stored in the network user encrypted database and the public user encrypted database respectively. 11. The method according to claim 10, characterized in that, when the user's login status at the browser end changes from non-login to login, the method further comprises: Extract the local key, the first encrypted data of the user in the public user database and the network key, decrypt the first encrypted data with the local key, encrypt the decrypted data with the network key, and save it in the network user database. 12. The method according to claim 10, wherein when the login status of the user on the browser side changes from non-login to login, the method further comprises: Extracting the user's first encrypted data and the network key in the public user database, using the network key to encrypt the user's first encrypted data, and saving it in the network user database. 13. The method according to claim 4, wherein the symmetric algorithm is an AES64, AES128, or AES256 algorithm. 14. The method according to claim 2, wherein the encoding/decoding algorithm is Base64 encoding/decoding. 15. A device for processing user information, comprising: An encryption request receiving module, configured to receive a request for encrypting user information; The encryption key acquisition module is used to obtain the corresponding encryption key according to the current login status of the user; An encryption module, configured to encrypt the user information according to the encryption key; The encoding module is configured to encode the encrypted data, and save the encoded data as the first encrypted data. 16. The apparatus of claim 15, further comprising: A decryption request generation module, configured to generate a decryption request, and obtain a corresponding decryption key and the first encrypted data according to the current login status of the user; a decoding module, configured to decode the first encrypted data; A decryption module, configured to decrypt the decoded data according to the decryption key; The automatic loading module module is used for performing automatic login or automatic registration according to the decrypted data. 17. The device according to claim 15, wherein the user information comprises user login information or user identity information. 18. The device according to claim 16, wherein the algorithm for encrypting/decrypting the user information according to the encryption/decryption key is a symmetric algorithm. 19. The device according to claim 15, wherein further the first encrypted data is stored locally in the browser or on the server side. 20. The device according to claim 15, wherein the encryption key acquisition module comprises: The first encryption key acquisition submodule is used to extract a local key as an encryption key at the client if the user does not log in to the browser, and the local key is generated according to hardware parameters corresponding to the user equipment one-to-one; The second encryption key acquisition sub-module is used to extract the network key on the server side as the encryption key if the user has logged in the browser. 21. The device according to claim 20, wherein when the user logs into the browser, the encryption key further includes a local key, then Before the encryption module, the device also includes: a local encryption module, configured to encrypt the user information according to the local key; The local encrypted data encoding module is used to encode the data encrypted by the local key. 22. The device according to claim 16, wherein the decryption request generation module comprises: The first decryption key acquisition submodule is used to extract a local key as a decryption key at the client if the user does not log in to the browser, and the local key is generated according to hardware parameters corresponding to the user equipment one-to-one; The second decryption key acquisition submodule is used to extract the network key as the decryption key at the server side if the user has logged in the browser. 23. The device according to claim 22, wherein when the user logs into the browser, the encryption key further includes a local key, then After the decryption module, the device also includes: The local decoding module is used to decode the data decrypted according to the network key; The local decryption module is used for decrypting according to the local key. 24. The device according to claim 20 or 22, wherein when the user is logged in and when the user is not logged in, the first encrypted data is stored in the network user encrypted database and the public user encrypted database respectively. 25. The device according to claim 24, wherein when the user's login status on the browser changes from unlogged to logged in, the device further comprises: The first data transfer module is used to extract the local key, the first encrypted data of the user in the public user database and the network key, decrypt the final encrypted data by the local key, and use the network key to decrypt the decrypted data Encrypted and stored in the network user database. 26. The device according to claim 24, wherein when the user's login status on the browser changes from non-login to login, the device further comprises: The second data transfer module is used to extract the user's first encrypted data and network key in the public user database, use the network key to encrypt the user's final encrypted data, and save it in the network user database. 27. The device according to claim 18, wherein the symmetric algorithm is an AES64, AES128, or AES256 algorithm. 28. The device according to claim 16, wherein the encoding/decoding algorithm is Base64 encoding/decoding.

Images