CN115037455B - Data protection method and system and electronic equipment - Google Patents

Data protection method and system and electronic equipment Download PDF

Info

Publication number
CN115037455B
CN115037455B CN202111408375.8A CN202111408375A CN115037455B CN 115037455 B CN115037455 B CN 115037455B CN 202111408375 A CN202111408375 A CN 202111408375A CN 115037455 B CN115037455 B CN 115037455B
Authority
CN
China
Prior art keywords
ring
screen locking
locking code
server
account
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.)
Active
Application number
CN202111408375.8A
Other languages
Chinese (zh)
Other versions
CN115037455A (en
Inventor
丁金岩
窦伟明
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Honor Device Co Ltd
Original Assignee
Honor Device Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Honor Device Co Ltd filed Critical Honor Device Co Ltd
Priority to CN202111408375.8A priority Critical patent/CN115037455B/en
Publication of CN115037455A publication Critical patent/CN115037455A/en
Application granted granted Critical
Publication of CN115037455B publication Critical patent/CN115037455B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0816—Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
    • H04L9/0819—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s)
    • H04L9/0822—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s) using key encryption key
    • 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/45—Structures or tools for the administration of authentication
    • G06F21/46—Structures or tools for the administration of authentication by designing passwords or checking the strength of passwords
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3226—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using a predetermined code, e.g. password, passphrase or PIN
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/30—Security of mobile devices; Security of mobile applications
    • 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/2117—User registration

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Bioethics (AREA)
  • Computing Systems (AREA)
  • Telephone Function (AREA)
  • Storage Device Security (AREA)

Abstract

The embodiment of the application provides a data protection method, a data protection system and electronic equipment. The method comprises the following steps: the method comprises the steps that in the ring adding process of the electronic equipment, a first screen locking code of the ring equipment is input; when the identity verification of the on-loop electronic equipment is passed based on the first screen locking code, a first main key ciphertext of the on-loop electronic equipment is obtained through cloud measurement and decrypted to obtain a main key; encrypting the master key based on the second screen locking code to generate a second master key ciphertext of the equipment, and generating a second authentication parameter based on the second screen locking code; and sending a ring adding request to the first server, so that the first server adds the second master key ciphertext and the second authentication parameter to trust ring data of the first trust ring, and the electronic device successfully adds the ring. According to the data protection method, because the user secret such as the first screen locking code which is already in the ring device is unknown to the cloud side, and the user secret which is already in the ring device does not need to be forwarded through the cloud side, the cloud side can not decrypt the master key ciphertext, and the self-authentication can be realized.

Description

Data protection method and system and electronic equipment
Technical Field
The embodiment of the application relates to the field of terminal equipment, in particular to a data protection method and system and electronic equipment.
Background
Currently, a terminal device may store data of a user in a cloud so that the user can upload and download the data in real time. The user's data typically corresponds to a particular user account. However, the security of user data relies entirely on account security, and the data may be obtained from the cloud side as long as the device is able to authenticate through the account. If any one of the account number and the cloud side server is attacked, user data can be leaked. Moreover, the cloud side server has the possibility of decrypting the user data, and the cloud side cannot clear the user data by self. Thus, the known solutions are less secure and do not provide support for user data protection with higher security requirements.
Disclosure of Invention
The application provides a data protection method, a system and electronic equipment, wherein in the ring adding process of the electronic equipment, a first screen locking code of the ring equipment is input; when the identity verification of the on-loop electronic equipment is passed based on the first screen locking code, a first main key ciphertext of the on-loop electronic equipment is obtained through cloud measurement and decrypted to obtain a main key; encrypting the master key based on the second screen locking code to generate a second master key ciphertext of the equipment, and generating a second authentication parameter based on the second screen locking code; and sending a ring adding request to the first server, so that the first server adds the second master key ciphertext and the second authentication parameter to trust ring data of the first trust ring, and the electronic device successfully adds the ring. According to the data protection method, because the user secret such as the first screen locking code which is already in the ring device is unknown to the cloud side, and the user secret which is already in the ring device does not need to be forwarded through the cloud side, the cloud side cannot decrypt the master key ciphertext and can self-prove and clear.
In a first aspect, an embodiment of the present application provides a data protection method applied to a second electronic device, where the method includes: the second electronic equipment receives a second screen locking code of the second electronic equipment, which is input by a user, wherein the second electronic equipment logs in the first account; when the second screen locking code passes verification, receiving a first screen locking code of first electronic equipment input by a user, wherein the first electronic equipment is equipment in ring equipment information of a first trust ring corresponding to a first account acquired from a first server; when the identity verification of the first electronic equipment based on the first screen locking code passes, receiving a first master key ciphertext of the first electronic equipment, which is sent by a first server; decrypting the first master key ciphertext based on the first screen locking code to obtain a master key; encrypting the master key based on the second screen locking code to generate a second master key ciphertext of the second electronic device, and generating a second authentication parameter based on the second screen locking code; and sending a ring adding request to the first server so that the first server second master key ciphertext and the second authentication parameter are added to the trust ring data of the first trust ring. According to the data protection method, the account-level master key MK is protected based on user secret such as a screen locking code, and the cloud side cannot decrypt a managed master key ciphertext because the user secret is unknown to the cloud side, so that the risk of master key leakage is reduced, the safety of the master key MK is improved, the cloud side can self-prove and clear, and support can be provided for data synchronization of service data with high safety requirements. It should be noted that the secret of the user is not limited to the screen locking code, and may be a birthday, a question answer, or the like.
The screen locking code in the present application may also be replaced by other user information, for example, the user information may be a user birthday, a user name, a birthday of a parent or a friend, a name, and the like. These pieces of information are unique to the user, and are known only by the user himself, and the information differs from user to user. This user information is easy for the user to remember and is not known by the cloud side. When the master key is encrypted based on the user information, the cloud side cannot decrypt, and thus the cloud side can self-certify and clarify. Except for the user, other people hardly know which user information is used by the user to encrypt the main key, so that the difficulty in cracking the ciphertext of the main key is greatly increased, the safety of the main key is improved, and the safety of user data protected by using the derivative key of the main key can be improved. Meanwhile, when the 2 nd device and the devices after the 2 nd device in the trust ring are registered, the identity of the registered device can be verified based on the user information, interaction with the registered device is not needed, and convenience is provided for the user.
According to the first aspect, after the second electronic device receives the user input of the second screen locking code of the second electronic device, the method further comprises: the second electronic device sends a ring device information acquisition request to the first server, wherein the ring device information acquisition request carries an account identifier of the first account; receiving ring-in device information of a first trust ring corresponding to a first account returned by a server, wherein the ring-in device comprises first electronic equipment; and displaying a screen locking code input interface of the first electronic equipment. Therefore, a screen locking code input interface of the default equipment is displayed, and a user can directly input a screen locking code of the verification equipment, so that the operation is convenient and fast.
According to the first aspect, or any implementation manner of the first aspect above, after the second electronic device receives the user input of the second screen locking code of the second electronic device, the method further includes: the second electronic device sends a ring device information acquisition request to the first server, wherein the ring device information acquisition request carries an account identifier of the first account; receiving ring-in-device information of a first trust ring corresponding to a first account returned by a server, wherein the ring-in-device information comprises first electronic equipment and third electronic equipment; and responding to the selected operation of the third electronic equipment in the ring equipment information, and displaying a screen locking code input interface of the third electronic equipment. The first server returns all the information of the on-ring devices, and a user can flexibly select any one on-ring device as the verification device, so that the verification is more flexible.
According to the first aspect, or any implementation manner of the first aspect, before the first electronic device passes authentication based on the first screen locking code and receives a first master key ciphertext of the first electronic device sent by the first server, the method further includes: the second electronic equipment generates a first authentication parameter based on the first screen locking code; and sending the first authentication parameter to the first server so that the first server performs identity verification on the first electronic device according to the first authentication parameter. Therefore, the authentication parameters are generated according to the user personalized information such as the screen locking code, so that the authentication parameters cannot be forged, and the authentication safety is ensured.
According to the first aspect, or any implementation manner of the first aspect, before the second screen locking code is verified, the method further includes, before receiving a first screen locking code of the first electronic device input by a user, that: comparing the second screen locking code with a locally stored screen locking code of the second electronic equipment; and when the second screen locking code is consistent with a locally stored screen locking code of the second electronic equipment, determining that the second screen locking code passes verification. By verifying the screen locking code of the equipment, the circulation adding process can be prevented from being maliciously triggered by others.
According to the first aspect or any one implementation manner of the first aspect, the encrypting, by the second electronic device, the master key based on the second screen locking code to generate a second master key ciphertext of the second electronic device includes: the second electronic equipment generates a third derivative key according to the second screen locking code; generating a fourth derivative key according to the third derivative key; and encrypting the master key according to the fourth derivative key to obtain a second master key ciphertext of the second electronic device. Therefore, the main key is encrypted according to the user personalized information such as the screen locking code, so that the cloud side which does not know the user personalized information cannot decrypt the main key, the user data encrypted by the derivative key of the main key is protected, and the safety of the user data is improved.
According to the first aspect, or any implementation manner of the first aspect, the generating, by the second electronic device, the second authentication parameter based on the second screen locking code includes: the second electronic equipment generates a third derivative key according to the second screen locking code; generating a second shared value according to the third derivative key; and encrypting the second shared value according to the HSM public key generated by the first server side to obtain a second authentication parameter. Therefore, the authentication parameters are generated according to the user personalized information such as the screen locking code, so that the authentication parameters cannot be forged, and the authentication safety is ensured.
According to the first aspect, or any one of the above implementation manners of the first aspect, the method further includes: the second electronic equipment detects the registration state of the second electronic equipment under the condition of receiving the registration request; sending a registration state comparison request to a first server under the condition that a second electronic device is not registered, wherein the registration state comparison request carries a device identifier of the second electronic device and an account identifier of a first account; and receiving a second registration state confirmation message returned by the first server, wherein the second registration state confirmation message is used for indicating that the first trust ring exists under the first account but the second electronic equipment is not on the first trust ring. According to the method, the registration state is detected at the equipment side, and when the local unregistered state is determined, the registration state is compared with the registration state at the cloud side, so that the access times to the cloud side can be reduced compared with the mode of directly requesting the cloud side to compare the registration states.
According to the first aspect, or any one of the above implementation manners of the first aspect, the method further includes: the second electronic equipment derives a first service key based on the master key, and encrypts the first service data by using the first service key to obtain a first service data ciphertext; and sending the first service data ciphertext to a second server so that the second server stores the first service data ciphertext. According to the mode that the business key derived based on the master key is synchronized to the cloud after the business data ciphertext is encrypted, the cloud end of the cloud business data ciphertext cannot be known due to the fact that the cloud end of the master key is unknown, the safety of the business data can be ensured, and the cloud end can be self-certified.
According to the first aspect, or any one of the above implementation manners of the first aspect, the method further includes: the second electronic equipment acquires a second service data ciphertext from the second server; deriving a first service key based on the master key; and decrypting the second service data ciphertext by using the first service key to obtain second service data. According to the method for obtaining the business data ciphertext from the cloud and then decrypting the business data ciphertext locally on the electronic equipment, even if the business data ciphertext transmitted between the cloud and the electronic equipment is intercepted, the business data obtained cannot be decrypted due to the fact that the rule that the main key and the main key derive the first business key cannot be obtained through interception and emulation, and the safety of the business data can be improved.
In a second aspect, an embodiment of the present application provides an electronic device, as a second electronic device, including a trust ring service module and a trust ring module, where: a trust ring service module to: receiving a second screen locking code of second electronic equipment input by a user, wherein the second electronic equipment logs in a first account; when the second screen locking code passes verification, receiving a first screen locking code of first electronic equipment input by a user, wherein the first electronic equipment is in-loop equipment information of a first trust loop corresponding to a first account acquired from a first server; when the identity verification of the first electronic equipment based on the first screen locking code passes, receiving a first master key ciphertext of the first electronic equipment, which is sent by a first server; sending a first master key ciphertext to the trust ring module; a trust ring module to: decrypting the first master key ciphertext based on the first screen locking code to obtain a master key; encrypting the master key based on the second screen locking code to generate a second master key ciphertext of the second electronic device; sending the second master key ciphertext to a trust ring service module; a trust ring service module further to: generating a second authentication parameter based on the second screen locking code; and sending a ring adding request to the first server so that the first server second master key ciphertext and the second authentication parameter are added to the trust ring data of the first trust ring.
According to a second aspect, the trust ring service module is further configured to: sending a ring device information acquisition request to a first server, wherein the ring device information acquisition request carries an account identifier of a first account; receiving ring-in device information of a first trust ring corresponding to a first account returned by a server, wherein the ring-in device comprises first electronic equipment; and displaying a screen locking code input interface of the first electronic equipment.
According to a second aspect, or any implementation manner of the second aspect above, the trust ring service module is further configured to: sending a ring device information acquisition request to a first server, wherein the ring device information acquisition request carries an account identifier of a first account; receiving ring-in device information of a first trust ring corresponding to a first account returned by a server, wherein the ring-in device comprises first electronic equipment and third electronic equipment; and responding to the selected operation of the third electronic equipment in the ring equipment information, and displaying a screen locking code input interface of the third electronic equipment.
According to a second aspect, or any implementation manner of the second aspect above, the trust ring service module is further configured to: generating a first authentication parameter based on the first screen locking code; and sending the first authentication parameter to the first server so that the first server performs identity verification on the first electronic device according to the first authentication parameter.
According to a second aspect, or any implementation manner of the second aspect above, the trust ring service module is further configured to: comparing the second screen locking code with a locally stored screen locking code of the second electronic equipment; and when the second screen locking code is consistent with the screen locking code of the second electronic equipment stored locally, determining that the second screen locking code passes verification.
According to the second aspect or any implementation manner of the second aspect, the trust ring module is specifically configured to, when encrypting the master key based on the second screen locking code and generating a second master key ciphertext of the second electronic device: receiving a third derivative key generated by the trust ring service module according to the second screen locking code; generating a fourth derivative key according to the third derivative key; and encrypting the master key according to the fourth derivative key to obtain a second master key ciphertext of the second electronic device.
According to the second aspect or any implementation manner of the second aspect, when the trust ring service module generates the second authentication parameter based on the second screen locking code, the trust ring service module is specifically configured to: generating a third derivative key according to the second screen locking code; generating a second shared value according to the third derivative key; and encrypting the second shared value according to the HSM public key generated by the first server side to obtain a second authentication parameter.
According to a second aspect, or any implementation manner of the second aspect above, the trust ring service module is further configured to: detecting a registration state of the second electronic device in case of receiving a registration request; sending a registration state comparison request to a first server under the condition that a second electronic device is not registered, wherein the registration state comparison request carries a device identifier of the second electronic device and an account identifier of a first account; and receiving a second registration state confirmation message returned by the first server, wherein the second registration state confirmation message is used for indicating that the first trust ring exists under the first account but the second electronic equipment is not on the first trust ring.
According to a second aspect, or any implementation manner of the second aspect above, the electronic device further includes: the system comprises a service data synchronization service module, a service data storage service module and a key management module; a trust ring service module further to: deriving a first service key based on the master key, and a service data storage service module, configured to: sending the first service data to a key management module; a key management module to: reading a first service key from the trust ring module, and encrypting first service data by using the first service key to obtain a first service data ciphertext; sending the first business data ciphertext to a business data storage service module;
the business data storage service module is further used for: and sending the first business data ciphertext to a second server through a business data synchronization service module so that the second server stores the first business data ciphertext.
According to the second aspect or any implementation manner of the second aspect, the service module is further configured to: acquiring a second service data ciphertext from the second server, and storing the second service data ciphertext into a service data storage service module; the business data storage service module is further used for: sending the second service data to a key management module; a key management module, further configured to: and reading the first service key from the trust ring module, decrypting the second service data by using the first service key to obtain second service data, and storing the second service data into the service data storage service module.
According to a third aspect, an embodiment of the present application provides a data protection system, including a first electronic device, a second electronic device, and a first server, wherein: a second electronic device to: receiving a second screen locking code of second electronic equipment input by a user, wherein the second electronic equipment logs in the first account; when the second screen locking code passes verification, receiving a first screen locking code of first electronic equipment input by a user, wherein the first electronic equipment is in-loop equipment information of a first trust loop corresponding to a first account acquired from a first server; when the identity verification of the first electronic equipment based on the first screen locking code passes, receiving a first master key ciphertext of the first electronic equipment, which is sent by a first server; decrypting the first master key ciphertext based on the first screen locking code to obtain a master key; encrypting the master key based on the second screen locking code to generate a second master key ciphertext of the second electronic device, and generating a second authentication parameter based on the second screen locking code; sending a ring adding request to a first server; a first server to: and responding to a ring adding request sent by the second electronic equipment, and adding the second master key ciphertext and the second authentication parameter into the trust ring data of the first trust ring. The data protection system protects the account level master key MK based on the user secret such as a screen locking code, and the cloud side cannot decrypt the managed master key ciphertext because the user secret is unknown to the cloud side, so that the risk of master key leakage is reduced, the safety of the master key MK is improved, the cloud side can self-prove and clear, and support can be provided for data synchronization of service data with high safety requirements. It should be noted that the secret of the user is not limited to the screen locking code, and may be a birthday, a question answer, or the like.
Any implementation manner of the second aspect and the second aspect corresponds to any implementation manner of the first aspect and the first aspect, respectively. For technical effects corresponding to any one implementation manner of the second aspect and the second aspect, reference may be made to the technical effects corresponding to any one implementation manner of the first aspect and the first aspect, and details are not repeated here.
In a fourth aspect, the present application provides a computer-readable medium for storing a computer program comprising instructions for performing the method of the first aspect or any possible implementation manner of the first aspect.
In a fifth aspect, the present application provides a computer program comprising instructions for carrying out the method of the first aspect or any possible implementation manner of the first aspect.
Drawings
Fig. 1 is a schematic structural diagram of an exemplary electronic device 100;
fig. 2 is a block diagram illustrating a software structure of the electronic device 100 according to the embodiment of the present application;
FIG. 3 is a diagram illustrating information interaction in creating a trust ring;
FIG. 4 is a diagram illustrating interaction of a device with a cloud side in creating a trust ring;
FIG. 5A is an exemplary interface diagram illustrating entry into the My devices application with a logged in account;
FIG. 5B is an exemplary illustration of an interface to a "my devices" application without a login account;
FIG. 6 is an exemplary interface diagram illustrating the migration of a My devices application from a device A to a password safe synchronization application;
FIG. 7A is a schematic diagram illustrating an exemplary entry process into the "combination safe" interface with device A having a lock screen code set;
FIG. 7B is a schematic diagram illustrating an exemplary entry process into the "combination safe" interface without the lock screen code set by device A;
FIG. 8 is a schematic diagram illustrating the process of opening a "password safe sync" switch in the context of creating a trust ring;
FIG. 9 is a diagram illustrating an exemplary process of turning on a "synchronize to Rough Account" switch in the context of creating a trust ring;
FIG. 10 is a schematic diagram illustrating a process for creating a trust ring;
fig. 11 is a schematic diagram illustrating an example of synchronizing a service data ciphertext with an account management server by a device a after a trust ring is created;
FIG. 12 is a schematic diagram illustrating exemplary module interactions for synchronizing business data ciphertexts;
FIG. 13 is a schematic diagram illustrating an interface of a synchronized business data ciphertext to an account management server;
FIG. 14 is a diagram illustrating information interaction during the process of joining a trust ring by device B;
FIG. 15 is an exemplary interface diagram illustrating the migration of a My devices application from device B to a password safe synchronization application;
FIG. 16A is a schematic diagram illustrating the process of entering the "combination safe" interface and opening the "combination safe synchronization" switch when device B has set the lock code;
FIG. 16B is a schematic diagram illustrating the process of entering the "combination safe" interface and opening the "combination safe synchronization" switch without the lock screen code being set by device B;
FIG. 17 is a diagram illustrating an exemplary process of turning on a "synchronize to glory account" switch in the scenario where device B joins the trust ring;
FIG. 18 is a flowchart illustrating device B joining a trust ring;
fig. 19 is a diagram illustrating synchronization of a service data ciphertext from an account management server after device B joins a trust ring;
fig. 20 is a schematic diagram illustrating an interface for synchronizing business data ciphertexts from an account management server;
FIG. 21 is a diagram illustrating information interaction during a process of joining a trust ring by device C;
fig. 22 is a flowchart illustrating an example of inputting a screen locking code of a device in a ring in a process of turning on a "synchronize to glory account" switch in a scenario where the device C joins a trust ring.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. 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 application.
The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone.
The terms "first" and "second," and the like, in the description and in the claims of the embodiments of the present application are used for distinguishing between different objects and not for describing a particular order of the objects. For example, the first target object and the second target object, etc. are specific sequences for distinguishing different target objects, rather than describing target objects.
In the embodiments of the present application, words such as "exemplary" or "for example" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "such as" is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.
In the description of the embodiments of the present application, the meaning of "a plurality" means two or more unless otherwise specified. For example, a plurality of processing units refers to two or more processing units; the plurality of systems refers to two or more systems.
Fig. 1 is a schematic structural diagram of an exemplary electronic device 100. It should be understood that the electronic device 100 shown in fig. 1 is only one example of an electronic device, and that the electronic device 100 may have more or fewer components than shown in the figures, may combine two or more components, or may have a different configuration of components. The various components shown in fig. 1 may be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and/or application specific integrated circuits.
The electronic device 100 may be a mobile phone, a tablet, or the like.
The electronic device 100 may include: the mobile terminal includes a processor 110, an external memory interface 120, an internal memory 121, a Universal Serial Bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, a Subscriber Identity Module (SIM) card interface 195, and the like. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.
The software system of the electronic device 100 may employ a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. The embodiment of the present application takes an Android system with a layered architecture as an example, and exemplarily illustrates a software structure of the electronic device 100.
The layered architecture of the electronic device 100 divides the software into several layers, each layer having a clear role and division of labor. The layers communicate with each other through a software interface. In some embodiments, the Android system is divided into three layers, namely an application layer, an application framework layer, and a kernel layer from top to bottom.
The application layer may include a series of application packages.
As shown in fig. 2, the application package may include applications such as sensors (which may also be referred to as desktop and wallpaper), HMS core, trust rings, password safes, and the like. For example, the sensor may monitor the user's sliding, pressing, etc. operation on the screen, and the HMS core provides a collection of cloud opening capabilities on the electronic device side. The trust ring application is used for creating and managing a trust ring for an account, wherein the management of the trust ring includes but is not limited to: adding equipment to the trust ring, deleting equipment from the trust ring, deleting the trust ring, freezing the trust ring, updating the master key ciphertext under the trust ring, and the like. The password safe box is used for managing service data synchronized by a user to an account management server, such as: a login account and a password for a certain service.
The application framework layer provides an Application Programming Interface (API) and a programming framework for the application program of the application layer. The application framework layer includes a number of predefined functions.
As shown in FIG. 2, the application framework layer may include a window manager, a view system, an F interface, and an explorer, among others.
The window manager is used for managing window programs. The window manager can obtain the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen, send an interface information display instruction to the view system and the like.
The view system includes visual controls such as controls to display text, controls to display pictures, and the like. The view system may be used to build applications. The display interface may be composed of one or more views. For example, the display interface including the short message notification icon may include a view for displaying text and a view for displaying pictures.
The resource manager provides various resources for the application, such as localized strings, icons, pictures, layout files, video files, and the like.
The F interface is an external service interface of the trust ring.
The application layer and the application framework layer run in a virtual machine. The virtual machine executes java files of the application layer and the application framework layer as binary files. The virtual machine is used for performing the functions of object life cycle management, stack management, thread management, safety and exception management, garbage collection and the like.
The system library may include a plurality of functional modules. For example: a two-dimensional graphics engine (e.g., SGL), a key asset trust ring CA, a surface manager, etc.
The surface manager is used to manage the display subsystem and provide fusion of 2D and 3D layers for multiple applications. A two-dimensional graphics engine is a drawing engine for two-dimensional images.
The key asset trust ring CA may also be referred to as a trust ring service module, and is mainly used for message pass-through between an upper layer trust ring application and a lower layer key asset trust ring TA.
The kernel layer is a layer between hardware and software. The kernel layer at least comprises a display driver, a sensor driver, a W-iFi driver and a key asset trust ring TA. The display driver is used to drive the display screen 194, the wi-Fi driver is used to drive the wireless communication module 160, and the sensor driver is used to drive the sensor module 180.
The key asset trust ring TA may also be referred to as a trust ring module, and is configured to implement core security logic, provide a trusted execution environment, generate a master key in the trusted execution environment, encrypt the master key to generate a master key ciphertext, and the like. For the specific functions of the key asset trust ring CA and the key asset trust ring TA, reference may be made to the related introduction in the following flow description of creating a ring, adding a ring, deleting a ring, preventing a riot, taking a device in the trust ring off line, updating a master key ciphertext, and the like.
It is to be understood that the system framework layer and the components included in the runtime layer shown in fig. 2 do not constitute a specific limitation of the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown, or combine certain components, or split certain components, or arrange different components.
When using an electronic device, a user generally needs to memorize a lot of password data, such as a password of a mailbox account, a password of a network disk account, a password of a smart home control right, and the like. When the password data is large, if the user is allowed to independently record the password data of each service, great difficulty is caused to the user to memorize. Therefore, a user wants to upload such password data to the cloud side for storage through a data synchronization function, and directly obtain the password data from the cloud side during use without memorizing the password data by the user.
However, for such password data, the user has different security requirements from general data to be synchronized, for example, data such as pictures, address lists, short messages, and the like. Such password data, once leaked, would cause a great loss to the user. Therefore, users have high security requirements for such cryptographic data. At this time, the security of the data synchronized to the cloud side is reduced due to the defect that the cloud side cannot self-certify and clarify, and the high security requirement of the password data cannot be met.
The data protection method enabling the cloud side to be self-certified and self-cleared can provide support for data synchronization of service data with high security requirements, such as password data.
The data protection method of the present application is described in detail below with reference to the accompanying drawings.
Creating a trust ring
Fig. 3 is a schematic diagram illustrating information interaction in a process of creating a trust ring. Fig. 4 is an exemplary interaction diagram of a device and a cloud side in a process of creating a trust ring. FIG. 10 is a schematic diagram illustrating a process for creating a trust ring.
The process of creating a trust ring according to the embodiment of the present application will be described in detail below with reference to fig. 3, 4 and 10.
In the embodiment of the present application, a glory account of a device a is assumed as an account 1, and a process of creating a trust ring is described by taking the device a to initiate registration to a trust ring cloud for the first time and creating the trust ring 1 of the account 1 as an example. The application that can trigger the creation of the trust ring process may be any application under the glory account, and the example of triggering the creation of the trust ring process through the application of "password safe synchronization" under the glory account is described herein.
Herein, "registration" refers to the process of adding a device to a trust ring. When the first device registers, because the account number does not have a trust ring, the trust ring needs to be created first and then the device is added to the trust ring, and the process of first device registration is referred to as creating the trust ring. The registration of a non-first device requires only adding the device to an existing trust ring, and the process of registering a non-first device is referred to herein as joining a trust ring.
It is assumed herein that account 1 includes 3 devices, namely, rough V40 (i.e., device A), rough V30 (denoted as device B), and Rough V50 (denoted as device C).
It should be noted that the actions performed by the various clouds herein should be understood as the actions performed by the servers in the respective clouds. For example, the actions performed by the trust ring cloud are performed by the trust ring cloud server.
Referring to fig. 3, in the process of creating a trust ring, a device a sends a request for logging in an account 1 to an account management server, and after the account management server verifies the request for logging in the account 1, the device a returns a verification passing message; after receiving the verification passing message, the device a generates a master key ciphertext EMK11 of the device a and an authentication parameter pawe 11 of the device a, and sends the EMK11 and the pawe 11 to the trust ring cloud, and after receiving the EMK11 and the pawe 11 sent by the device a, the trust ring cloud creates a trust ring 1 for the account 1, and adds the device a to the trust ring 1.
Referring to fig. 10, in an embodiment of the present application, a process of creating a trust ring by a device a may include the following steps:
step S1: device a logs into account 1.
The description is given here taking device a as a glory V40 handset as an example. It should be understood that device a may be any electronic device that has installed the functionality of creating a trust ring in the present application, and the present application is not limited thereto.
Device a needs to initiate registration with the trust ring cloud to create a trust ring if it has logged in to the account. If the device A does not log in the account, the account needs to be logged in first.
FIG. 5A is an exemplary illustration of an interface to the My devices application with a logged in account. Fig. 5B is an exemplary interface diagram illustrating entry into the my devices application without logging in to the account. FIG. 6 is an exemplary interface diagram illustrating the migration of a My devices application from a device A to a password safe synchronization application.
Referring to fig. 5A and 6, in a case where the device a has logged in to the account 1 (assuming that the account 1 is 1581991 xxx), the user may click on a "setting" application icon in the device a main interface (as shown in fig. 5A (a), and enter a "setting" interface shown in fig. 5A (b)). In the "setup" interface, the user clicks on account 1 (i.e., 1581991 xxx), and proceeds to the "Account center" interface shown in FIG. 5A (b). At the "Account center" interface, the user clicks on "My devices" and proceeds to the "My devices" interface shown in FIG. 6 (b). Find the current device, i.e., glory V40, in the my devices interface, click on glory V40 to enter the device information interface shown in fig. 6 (c). In the device information interface, the user continues to click the password safe synchronization application in the interface, and can enter the password safe interface. After a 'password safe box synchronization' switch is started on a 'password safe box' interface, a 'synchronization to glory account number' switch is clicked, and then a process of creating a trust ring is triggered. The process of entering the "safe deposit box" interface, turning on the "safe deposit box synchronization" switch, and turning on the "synchronization to glory account" switch will be described later.
It should be noted that if there is a trust ring under account 1, a "trusted device" is displayed under the devices that have been added to the trust ring on the "my devices" interface. The device identified as "trusted device" is a device that has joined the trust ring, i.e., a registered device, see the interface shown in subsequent fig. 15 (b). If there is no trust ring under account 1, for example, on the "my equipment" interface of equipment a shown in fig. 6 (b), none of the 3 glory equipment is a trusted equipment, which means that there is no trust ring under account 1 currently.
Referring to fig. 5A, 5B, and 6, in a case where the device a does not log in to the account 1, after clicking a "setting" application icon in the main interface of the device a (as shown in fig. 5A), the user enters a "setting" interface shown in fig. 5B (a). In the "setup" interface, the user clicks "login glory account" and proceeds to the glory account login interface shown in fig. 5B (B). In a glory account login interface, a user inputs an account 1 (1581991 xxx) and a login password (assumed to be key 1), and a device a sends a request for logging in the account 1 to an account management server, wherein the request carries the account 1 (1581991 xxx) and the login password key1.
Referring to fig. 4, a user may send a request for logging in an account 1 to an account management server through an account management module of an application layer of the device a, so as to log in the account 1.
After the device a successfully logs in the account 1, the process of creating the trust ring is triggered according to the process in the case of the logged-in account, please refer to fig. 5A (c), fig. d, and fig. 6, which are not described herein again.
Step S2: and the account management server returns a verification passing message.
The account management server pre-stores information of the account 1, which includes a login password corresponding to the account 1, and it is assumed here that the login password of the account 1 stored by the account management server is key0. After receiving the request for logging in the account 1 sent by the device a, the account management server verifies the request for logging in the account 1 according to the information of the account 1 locally stored by the account management server. If the password key1 of the login account 1 carried in the request of the login account 1 is consistent with the login password key0 of the account 1 locally stored by the account management server, the account management server determines that the login verification of the account 1 is passed. At this time, the account management server returns an authentication pass message to the device a.
If the password key1 of the login account 1 carried in the request of the login account 1 is inconsistent with the login password key0 of the account 1 locally stored by the account management server, the account management server determines that the login authentication of the account 1 fails. At this time, the account management server returns a verification failure message to the device a. At this time, the user needs to re-input the account and the login password through the diagram (B) of fig. 5B.
Referring to fig. 4 and 10, the device a receives a verification pass message or a verification fail message through the account management module.
S3: and sending a registration opening notice.
Referring to fig. 4 and 10, in a case that the account management module of the device a receives the verification passing message returned by the account management server, the account management module in the device a sends a registration opening notification to the trust ring service module of the application framework layer. The registration opening notification is used for indicating the trust ring service module to open the registration process.
Here, a process of entering a "password safe" interface and opening a "password safe synchronization" switch by the device a in the process of creating the trust ring will be described.
Fig. 7A is a schematic diagram illustrating an example process for entering a "combination safe" interface in the case where device a has set a lock screen code. Referring to fig. 7A, in a case that a user of device a has set a screen locking code (also referred to as a screen locking password) of device a, when the user clicks a "password safe synchronization" application in the interface on a "device information" interface (see fig. 7A), device a pops up a "screen locking password input" interface (see fig. 7A b). If the user enters the screen lock code on the "enter screen lock code" interface and the screen lock code is correct, the screen of device a enters the "password safe" interface (see fig. 7A (c)). At the moment, a 'password safe box synchronization' switch and a 'synchronization to glory account number' switch on the 'password safe box' interface are both in a closed state.
Fig. 7B is a schematic diagram illustrating the process of entering the "combination safe" interface without the lock screen code being set by device a. Referring to fig. 7B, in a case that the user of the device a does not set the screen locking code of the device a, when the user clicks the "password safe synchronization" application in the "device information" interface at the "device information" interface (see fig. 7B (a)), the device a pops up the "set digital screen locking code" interface (see fig. 7B (B)). After the user inputs the screen locking code on the interface "set digital screen locking code" shown in fig. 7B (B), the device a pops up an interface for confirming the code "set digital screen locking code" (please refer to fig. 7B (c)). The user re-inputs the lock screen code on the interface shown in fig. 7B (c), and if the re-input lock screen code is identical to the lock screen code input by the user on the interface shown in fig. 7B (B), the screen of the device a enters the "password safe" interface shown in fig. 7B (d), which is the same as the interface shown in fig. 7A (c).
FIG. 8 is a schematic diagram illustrating the process of opening a "password safe synchronization" switch in the context of creating a trust ring. Referring to fig. 8, when the user clicks the "password safe synchronization" switch on the "password safe" interface (see fig. 8 (a)), a reminder interface shown in fig. 8 (b) pops up on the screen of the device a, and the reminder interface is used to remind the user whether to approve the password safe synchronization service. When the user clicks the "agree" button on the reminder interface (see fig. 8 (b)), the "password safe synchronization" switch on the "password safe" interface is turned on (see fig. 8 (c)).
When receiving the registration opening notification, the trust ring service module cannot determine whether to open a process of creating a trust ring or a process of joining the trust ring, and needs to determine by detecting a registration state.
S4: the trust ring service module in device a detects the registration status of device a.
The registered state includes both unregistered and registered states. The unregistered state is used for indicating that the device is not currently registered to the trust ring, and the registered state is used for indicating that the device is currently registered to the trust ring.
S5: and when detecting that the registration state of the device A is unregistered, the device A sends a registration state comparison request to the trust ring cloud.
The registration state comparison request is used for indicating to obtain a comparison result between the registration state of the device A detected by the trust ring service module and the registration state of the device A stored in the trust ring cloud.
The registration state comparison request includes a UID (device identifier) of the device a and a UDID (account identifier) of an account to which the device a belongs.
S6: the trust ring cloud returns a first registration status confirmation message to the trust ring service module in device a.
Wherein the first registration status confirmation message is used to indicate that no trust ring exists under account 1.
After receiving a registration state comparison request of the device a, the trust ring cloud compares whether a trust ring exists under the account 1, and compares whether the device a is in the trust ring under the condition that the trust ring exists under the account 1. And when the trust ring does not exist under the account 1, the trust ring cloud generates a first registration state confirmation message and sends the first registration state confirmation message to the device A.
Based on a first registration state confirmation message returned by the trust ring cloud, the device a determines that the registration is executed to create the trust ring process.
S7: the trust ring service module in the device a receives the screen locking code pw11 of the device a input by the user.
Here, a process of turning on the "synchronize to glory account" switch in the process of creating the trust ring will be described.
Fig. 9 is a schematic diagram illustrating a process of turning on a "synchronize to glory account" switch in a scenario of creating a trust ring. Referring to fig. 9, when the user clicks the "synchronize to glory account" switch on the "password safe" interface in which the "password safe synchronization" switch is turned on (see fig. 9 (a)), the device a pops up a "enter lock screen password" interface on the screen (see fig. 9 (b)). If the user inputs the screen locking code of the device A on the screen locking password input interface, the trust ring service module in the device A receives the screen locking code of the device A input by the user. If the screen locking password of the device a input by the user is correct, after the device a executes the process of creating the trust ring, the device a enters a "password safe box" interface in which both a "password safe box synchronization" switch and a "synchronization to glory account" switch are in an open state (see fig. 9 (c)).
It should be noted that the user clicks the "synchronize to glory account" switch on the interface shown in fig. 9 (a) (see fig. 9 (a)) to trigger the device a to execute step S3 in fig. 10 and the step of creating the trust ring program after step S3.
The screen locking code of the device A belongs to the user secret of the device A, and is unknown to the cloud side.
S8: the trust ring service module of device a verifies the lock screen code pw11 of device a.
The process of verifying the screen locking code of device a may be: and the equipment A compares the screen locking code input by the user with the screen locking code pre-stored in the equipment A, if the screen locking code is consistent with the screen locking code, the verification is passed, and otherwise, the verification fails.
Here, the trust ring service module verifies the screen locking code of the device a input by the user on the interface shown in fig. 9 (b) again, and the subsequent step S9 can be continued only after the verification is passed. If the verification fails, the device A will return to the interface shown in FIG. 9 (b), and prompt the input screen locking code error at the interface.
S9: the trust ring service module derives PWUATH11 based on the screen locking code of device a.
Assuming that the screen locking code input by the user at this time is pw11, the trust ring service module derives PWUATH11 based on pw11.
Since pw11 belongs to the user secret of device a, pw11 cannot be obtained by the cloud side, so PWUATH11 derived based on pw11 cannot be obtained by the cloud side.
Pwuth 11 is unknown to the cloud side because pwuth 11 is generated based on the unknown user secret pw11 of the cloud side.
S10: the trust ring service module of device a sends PWAUTH11 to the trust ring module in the trusted execution environment of device a.
Subsequently, the trust ring module generates a master key ciphertext EMK11 and a parameter pave 11 based on PWAUTH11, and the generation modes of EMK11 and pave 11 are detailed in steps S11 to S14 of fig. 10.
S11: the trust ring module generates MK.
The device A generates MK (main key) through the trust ring module, and the MK is stored in the trusted execution environment of the device A, and even if the device A is attacked, the MK cannot be stolen, so that the safety is high.
S12: the trust ring module encrypts MK based on PWAUTH11, generating EMK11.
EMK11 is the first master key ciphertext. The trust ring module derives a key KEK11 based on PWAUTH11, and encrypts MK based on the KEK11 to generate EMK11.
S13: the trust ring module of device a sends the EMK11 to the trust ring service module of device a.
After the trust ring module generates the EMK11, the EMK11 is sent to the trust ring service module, and the salt _ enc11 is also sent to the trust ring service module while the EMK11 is sent.
S14: the trust ring service module in device a generates the parameter pave 11 based on PWAUTH11.
S15: the device A sends a ring creation request carrying the EMK11 and the PAKE11 to the trust ring cloud through the trust ring service module.
The device A sends a ring creation request to the trust ring cloud through the trust ring service module, and PAKE11 parameter registration and EMK11 hosting can be completed through the request.
In order to improve the security of the EMK11, before the trust ring service module sends the EMK11, the trust ring service module may perform secondary encryption on the EMK11 based on the public key of the trust ring cloud HSM obtained during login to obtain a two-layer ciphertext of the master key.
The escrowMsg is a two-layer ciphertext of the master key, and the trust ring service module sends the escrowMsg and the parameter PAKE11 to the trust ring cloud to request the trust ring cloud to create the trust ring 1 of the account number 1.
S16: the trust ring cloud creates a trust ring 1 for account 1 in response to the ring creation request, and adds device a to trust ring 1.
The trust ring cloud responds to a ring creation request sent by the device A, creates a trust ring 1 for the account 1, when other devices such as a device B and a device C under the account 1 send registration state comparison requests to the trust ring cloud, the trust ring cloud returns a confirmation message that the trust ring 1 exists but the device B and the device C are not in the trust ring, the device B and the device C execute a process of adding the trust ring, and the specific process of adding the trust ring can refer to a subsequent related description.
After the creation of the trust ring 1 is completed, the trust ring 1 data managed in the trust ring cloud is as shown in table 1:
TABLE 1
UID UDID Parameter PAKE Master key ciphertext
Account number
1 Device A PAKE11 EMK11
S17: the trust ring cloud returns a ring creation success message to the trust ring service module of the device A.
The trust ring cloud creates a trust ring 1 for the account number 1, and after the device a is added to the trust ring 1, returns a ring creation success message to the device a, and after the device a receives the ring creation success message, opens a switch of "synchronize to glory account number" in the password safe interface, as shown in (c) of fig. 9. After the 'synchronization to a glory account' switch is turned on, the user can sense that the device A has successfully joined the trust ring, and the service data in the password safe can be synchronized to the account management server, so that other devices in the trust ring 1 under the account 1 can share the service data.
At this point, the process of creating a trust ring is finished, and device a completes registration.
After the device a finishes registration, the trust ring service module of the device a modifies the registration state of the device a to be registered.
As can be seen from the process of creating the trust ring, the account-level master key MK is protected based on the user secret, and the user secret is unknown to the cloud side, so that the cloud side cannot decrypt the escrowed master key ciphertext, the risk of master key leakage is reduced, the security of the master key MK is improved, the cloud side can self-prove and clear, and support can be provided for data synchronization of business data with high security requirements.
It should be noted that the above-mentioned process should be understood as an illustrative example of the process of creating a trust ring in the present application, and is not intended to limit the present application.
Fig. 11 is a schematic diagram illustrating that device a synchronizes the business data ciphertext to the account management server after creating the trust ring. Fig. 12 is a schematic diagram illustrating module interaction for synchronizing service data ciphertexts. Fig. 13 is a schematic diagram illustrating an interface of a synchronized service data ciphertext to an account management server. Referring to fig. 11, 12, and 13, in a case that a trust ring 1 of an account 1 has been created and a device a has been added to the trust ring 1, the device a may encrypt sensitive service data with MK to obtain a service data ciphertext, and upload the service data ciphertext to an account management server.
After the trust ring is created, the process of synchronizing the service data ciphertext to the account management server by the device A is as follows:
referring to fig. 12, a cryptographic safe of an application layer in a device a reads a service data plaintext, and then stores the service data plaintext into a service data storage service module of an application framework layer, where the service data storage service module sends the service data plaintext to a key management module in a trusted execution environment. And the trust ring module generates a service key dkey according to the MK, the key management module reads the dkey from the trust ring module, and the dkey is used for encrypting the service data to obtain a service data ciphertext Edata. And the service data storage service module uploads the service data ciphertext Edata to the account management server through the service data synchronization service module and an account management server synchronization frame of the application program layer.
It should be noted that the service keys dkey corresponding to different services are different, and the device a may generate the service keys of different services according to MK.
For example, referring to fig. 13, when the user uses service 1 on device a, the user needs to input the account and password of service 1, as shown in fig. 13 (a). After the account number and the password of the service 1 are input, the device a pops up information prompting whether to synchronize the account number and the password of the service 1 to the password safe, as shown in fig. 13 (b). If the user agrees, the device A takes the account and the password of the service 1 as the service data1 of the service 1, and uploads the ciphertext Edata1 of the data1 to the account management server according to the same synchronization process with the service data.
Therefore, in the embodiment of the application, the business data ciphertext in the account management server does not depend on account security completely, but also depends on MK security, and even if the account is stolen, the security of data on the cloud is not affected.
The business data of the user are encrypted based on the high-security master key, and then the business data ciphertext is synchronized to the account management server, so that the risk of leakage of the business data ciphertext is reduced, and the security of data synchronous backup is improved.
Joining a trust ring
On the basis that device a has created trust ring 1 for account 1, device B under account 1 may join trust ring 1 according to the join trust ring procedure in the following embodiment. Before device B joins trust ring 1, only device a, the ring device, is in trust ring 1.
Fig. 14 is a schematic diagram illustrating information interaction during the process of joining the trust ring by the device B. Fig. 18 is a flowchart illustrating the process of device B joining a trust ring.
The process of joining a trust ring according to the embodiment of the present application will be described in detail below with reference to fig. 14 and 18.
Referring to fig. 14, after the device a registers as the first device, the process of creating the trust ring is completed, the device a has uploaded the master key cryptogram EMK11 of the device a, that is, the first master key cryptogram, and the authentication parameter pave 11 of the device a to the trust ring cloud, and thereafter, other devices, for example, the device B, register by joining the trust ring process. In the process that the device B joins the trust ring 1, the device B sends the authentication parameter PAKE12 of the device A in the trust ring 1 to the trust ring cloud, and the trust ring cloud returns the master key ciphertext EMK11 of the device A to the device B after confirming that the PAKE12 is consistent with the authentication parameter PAKE11 of the device A stored in the trust ring 1. Then, the device B decrypts MK from the EMK11, encrypts MK based on the screen locking code of the device B, generates a master key ciphertext EMK21 of the device B, that is, a second master key ciphertext, and an authentication parameter pay 21 of the device B, and sends EMK21 and pay 21 to the trust ring cloud.
Referring to fig. 18, in the embodiment of the present application, the process of joining the trust ring by the device B may include the following steps:
s1: device B logs into account 1.
Like the device a, the device B logs in to the account 1 by sending a request to the account management server to log in to the account 1. For a detailed process of logging in the account 1 by the device B, refer to the foregoing description of the process of logging in the account 1 by the device a, and are not described herein again.
And S2, the account management server returns a verification passing message to the equipment B.
For the processing procedure of the request of the account management server for the device B to log in the account 1, refer to the processing procedure of the request of the account management server for the device a to log in the account 1, which is not described herein again.
After the device B successfully logs in the account 1, the user may enter the "account center" interface through the flow indicated by the diagrams (B) and (c) in fig. 5A to find the "my device" application.
S3: and sending a registration opening notice.
Referring to fig. 4 and fig. 18, in a case that the account management module of the device B receives a verification-passed message returned by the account management server, the account management module in the device B sends a registration-opening notification to the trust ring service module of the application framework layer. The registration opening notification is used for indicating the trust ring service module of the device B to open the registration process.
Here, a process of entering the interface of the "password safe" and opening the "password safe synchronization" switch during the process of joining the trust ring by the device B will be described.
FIG. 15 is an exemplary interface diagram illustrating the migration of a My devices application from device B to a password safe synchronization application. As can be seen by comparison to FIG. 6, during the joining of the trust ring, there is a trusted device glory V40, device A, on the My devices interface of device B. This indicates that a ring of trust already exists under account 1.
FIG. 16A is a schematic diagram illustrating the process of entering the "combination safe" interface and opening the "combination safe synchronization" switch when device B has set the lock code. Referring to fig. 16A, in a case where the user of the device B has set the screen lock code of the device B, when the user clicks the "password safe synchronization" application in the "device information" interface at the "device information" interface (see fig. 16A (a)), the device B pops up the "enter screen lock code" interface (see fig. 16A (B)). If the user enters the screen lock code in the "enter screen lock code" interface and the screen lock code is correct, the screen of device B enters the "password safe" interface (see FIG. 16A (c)). At the moment, a 'password safe box synchronization' switch and a 'synchronization to glory account number' switch on the 'password safe box' interface are both in a closed state. Different from the process of creating the trust ring by the device a, in the process of joining the trust ring by the device B, when the user clicks the "password safe synchronization" switch on the "password safe" interface shown in the diagram (c) of fig. 16A, the screen of the device B is directly switched to the interface shown in the diagram (d) of fig. 16A, that is, the interface where the "password safe synchronization" switch is turned on and the "synchronization to the glory account" is not turned on.
FIG. 16B is a schematic diagram illustrating the process of entering the "combination safe" interface and opening the "combination safe synchronization" switch without the lock screen code being set by device B. Referring to fig. 16B, a process of entering the interface of the "password safe" and opening the switch of the "password safe synchronization" when the device B does not set the lock screen code is different from a process of entering the interface of the "password safe" and opening the switch of the "password safe synchronization" when the device B has set the lock screen code shown in fig. 16A in that the lock screen code needs to be set (see fig. 16B (B)) and the lock screen code needs to be confirmed (see fig. 16B (c)) when the device B does not set the lock screen code, and other processes are the same as those in the case of having set the lock screen code, and are not described again here.
S4: the trust ring service module in device B detects the registration status of device B.
For the description of this step, refer to the foregoing description of step S4 in fig. 10, and are not repeated here.
S5: and when the registration state of the device B is detected to be unregistered, sending a registration state comparison request.
For the description of this step, refer to the foregoing description of step S5 in fig. 10, and are not repeated here.
S6: and returning a second registration state confirmation message, namely the second registration state confirmation message.
Wherein the second registration status confirmation message is used to indicate that trust ring 1 exists under account 1, but device B is not on trust ring 1.
After receiving the registration state comparison request of the device B, the trust ring cloud first compares whether a trust ring exists under the account 1. At this time, since the trust ring has already created trust ring 1 for account 1 at the time of device a registration, it is confirmed that there is a trust ring under account 1. Then, the trust ring cloud confirms that the device B is not in the trust ring according to the trust ring data of the account 1 shown in table 1, and at this time, the trust ring cloud generates a second registration state confirmation message and sends the second registration state confirmation message to the device B.
Based on a second registration state confirmation message returned by the trust ring cloud, the device B determines that the registration is executed and the process of joining the trust ring is executed.
S7: the trust ring service module in the device B receives the screen locking code pw21 of the device B input by the user.
Fig. 17 is a schematic diagram illustrating a process of turning on a "synchronize to glory account" switch in a scenario where device B joins a trust ring. Referring to fig. 17, when the user clicks the "synchronize to glory account" switch on the "password safe" interface in which the "password safe synchronization" switch is turned on (see fig. 17 (a)), the device B pops up a "enter lock screen password" interface on the screen (see fig. 17 (B)). If the user inputs the screen locking code of the device B in the screen locking password input interface, the trust ring service module in the device B receives the screen locking code of the device B input by the user.
S8: the trust ring service module of the device B verifies the screen locking code pw21 of the device B, and derives PWAUTH21 based on the screen locking code pw21 of the device B.
Please refer to the aforementioned process of verifying the screen locking code pw11 of the device a for the process of verifying the screen locking code pw21 of the device B, which is not described herein again.
S9: the trust ring service module of device B obtains the list of devices in trust ring 1.
The trust ring service module of the device B may send an acquisition request of the device list in the trust ring 1 to the trust ring cloud, and after receiving the request, the trust ring cloud returns the device list in the trust ring 1 to the trust ring service module of the device B.
S10: the trust ring cloud returns the list of devices in trust ring 1 to the trust ring service module of device B.
All devices that have currently joined the trust ring 1 are included in the device list in the trust ring 1. In the embodiment of the present application, since the device a is a device that creates the trust ring 1, and the device B is a device that first joins the trust ring 1, in the process of joining the device B in the trust ring 1, the device list in the trust ring 1 returned by the trust ring cloud includes only one device of the device a.
S11: the trust ring service module of the device B displays a screen locking code input interface of the device a, receives a screen locking code pw12 of the device a input by a user, and generates a parameter pawe 12 based on the screen locking code pw 12.
Referring to fig. 17, if the screen-locking code of device B input by the user is correct in the interface shown in fig. 17 (B), the screen of device B pops up the interface "input other glory device screen-locking code" (please refer to fig. 17 (c)), and the "other glory device" in fig. 17 (c) is glory V40, i.e., device a. The user inputs the screen locking code pw12 of the device a on the interface "input other glory device screen locking password", and if the screen locking code pw12 of the device a input by the user is correct, the device B enters the interface "password safe box" in which the "password safe box synchronization" switch and the "synchronization to glory account" switch are both in the on state after the device B completes the trust loop adding process (see fig. 17 (d)).
It should be noted that the user clicks the "synchronize to glory account" switch on the interface shown in fig. 17 (a) (see fig. 17 (a)) to trigger the device a to execute step S3 in fig. 18 and the join trust ring program step after step S3.
The screen locking code of the device B belongs to the user secret of the device B, and is unknown to the cloud side.
The generation principle of the parameter pave 12 is the same as that of the parameter pave 11, and is not described herein again.
S12: the trust ring service module of device B sends the parameter park 12 to the trust ring cloud.
In the process that the device B joins the trust ring 1, the trust ring cloud needs to verify the identity of the device in the trust ring 1, when the identity passes the verification, the device is allowed to join the trust ring 1, otherwise, the trust ring cloud prohibits the device B from joining the trust ring 1.
S13: after the authentication of the trust ring cloud to the device a based on the parameter pawe 12 is passed, the EMK11 of the device a is returned to the trust ring service module of the device B.
S14, the trust ring service module of the device B sends the EMK11 and the PWAUTH21 to the trust ring module of the device B.
The trust ring module is located in the trusted execution environment of device B, which needs to decrypt EMK11 in the trusted execution environment to fetch MK, and encrypt MK based on PWAUTH21 in the trusted execution environment to obtain EMK21.
S15, the trust ring module of the device B decrypts the EMK11 to obtain MK, and encrypts the MK based on the PWAUTH21 to obtain the EMK21.
S16: the trust ring module of device B sends an EMK21 to the trust ring service module of device B.
S17: device B generates parameter park 21 based on PWAUTH21.
S18: the trust ring service module of the device B sends a ring adding request carrying the EMK21 and the parameter park 21 to the trust ring cloud.
S19: the trust ring cloud adds device B to trust ring 1 in response to the ring add request.
After device B joins trust ring 1, the trust ring 1 data managed in the trust ring cloud is shown in table 2:
TABLE 2
UID UDID Parameter PAKE Master key ciphertext
Account number
1 Device A PAKE11 EMK11
Account number
1 Device B PAKE21 EMK21
S20: and the trust ring cloud returns a ring adding success message to the trust ring service module of the device B.
After adding the device B to the trust ring 1, the trust ring cloud returns a ring addition success message to the device B, and after receiving the ring addition success message, the device B opens a switch of "synchronize to a glory account" in the password safe interface, as shown in fig. 17 (d). After the 'synchronization to a glory account' switch is turned on, the user can sense that the device B has successfully joined the trust ring, and the service data in the password safe can be synchronized to the account management server, so that other devices in the trust ring 1 under the account 1 can share the service data.
At this point, the process of joining the trust ring 1 by the device B is completed, and the device B completes registration.
After the device B completes registration, the trust ring service module of the device B modifies the registration state of the device B to be registered.
The method comprises the steps that a cloud side sends a managed master key ciphertext of a registered device to a ring-added device, the ring-added device decrypts the master key ciphertext of the registered device based on a user secret of the registered device to obtain a master key MK, and the user secret of the registered device is unknown to the cloud side and does not need to be forwarded by the cloud side, so that the cloud side cannot decrypt the master key ciphertext and can self-verify the clearness.
It should be noted that the above-mentioned process should be understood as an illustrative example of the trust ring process added in the present application, and is not intended to limit the present application.
Fig. 19 is a schematic diagram illustrating synchronization of a service data ciphertext from an account management server after device B joins a trust ring. Fig. 20 is a schematic diagram illustrating an interface for synchronizing business data ciphertext from the account management server. Referring to fig. 19, 12 and 20, in the case that the trust ring 1 of the account 1 is created, the device a has been added to the trust ring 1, and the device a has uploaded the service data ciphertext Edata to the account management server, the device B may synchronize the service data ciphertext Edata from the account management server to the device B, and decrypt the service data ciphertext Edata locally with MK to obtain the service data plaintext data.
After the trust ring is added, the process of synchronizing the service data ciphertext in the account management server by the device B is as follows:
referring to fig. 12, a service data synchronization service module in the device B obtains a service data ciphertext Edata from an account management server through an account management server synchronization framework of an application layer. Then, the service data synchronization service module in the device B sends the service data ciphertext Edata to the service data storage service module in the device B, and the service data storage service module sends the service data ciphertext Edata to the key management module in the information execution environment in the device B. The trust ring module generates a service key dkey according to MK, the key management module reads the dkey from the trust ring module, and the service data ciphertext Edata is decrypted by using the dkey to obtain the service data plaintext data. And then, the key management module returns the service data plaintext data to the service data storage service module, and the service data storage service module stores the service data plaintext data.
For example, referring to fig. 20, when the user uses service 1 on device B, the user needs to input the account and password of service 1. In the account number and password input interface of the service 1, as shown in fig. 20 (a), the device B pops up information indicating whether to use the account number and password of the service 1 with the synchronized password safe. If the user agrees, device B automatically populates the interface shown in fig. 20 (a) with the account number and password of service 1 with synchronized password safe, and then populates the interface as shown in fig. 20 (B). Therefore, the user does not need to independently record passwords for each service, and the user experience is improved.
It should be noted that, after the device B joins the trust ring 1, the service data in the device B may also be encrypted by the master key MK and then synchronized to the account management server, and for this synchronization process, reference is made to the foregoing description of synchronizing the service data to the account management server by the device a, and details are not described here again.
On the basis that the device a has created the trust ring 1 of the account 1 and the device B has joined the trust ring 1 through the join trust ring process shown in fig. 18, the device C under the account 1 may also join the trust ring 1 according to the join trust ring process shown in fig. 18. For a detailed process of joining the device C into the trust ring 1, refer to the foregoing description of the process of joining the device B into the trust ring 1, and are not described herein again.
Unlike device B, before device C joins trust ring 1, there are two ring devices, device a and device B, in trust ring 1. Thus, upon verifying that the old device (which herein refers to an on-ring device, i.e., a device that has registered with a trust ring) is locked, device C may select either one of the two on-ring devices, device a, device B, as the old device. That is, in the process of joining the trust ring 1 by the device C, the device list returned to the device C by the trust ring cloud in step S10 shown in fig. 18 includes 2 trusted devices, i.e., device a (see the glory V40 in fig. 22B) and device B (see the glory V30 in fig. 22B). In the "enter other glory device lock screen password" interface popped up by the device C, the lock screen password of the first registered device (in the embodiment of the present application, device a) is entered by default, as shown in fig. 17 (C), that is, the "other device" in this interface is the glory V40 (device a). At this time, the device C can select to input the screen locking code of the other old device, for example, the device B, through the "select authentication device" operation option on the interface shown in fig. 17 (C). The procedure for device C to change the authentication device is described below with reference to fig. 22.
Fig. 22 is a flowchart illustrating an example of inputting a screen locking code of a device in a ring in a process of turning on a "synchronize to glory account" switch in a scenario where the device C joins a trust ring. Referring to fig. 22, in the process of joining the trust ring, after entering the interface shown in fig. 17 (C), the user clicks "select verification device" on the interface, as shown in fig. 22 (a). Thus, the device C enters the interface of "select authentication device", as shown in fig. 22 (b). Since there are already 2 devices in the trust ring 1 at this time (device a and device B), the "select verification device" interface has 2 devices, namely glory V40 (device a) and glory V30 (device B). The user clicks on "glory V30", indicating that the user selected device B as the old device for authentication. After clicking, device C pops up an "enter other Rough device Lock password" interface, and the "other device" in this interface changes to Rough V30, as shown in FIG. 22 (C). When the screen locking code of the device B input by the user on the interface shown in fig. 22 (c) is correct, the "synchronize to glory account" switch is turned on.
Fig. 21 is a schematic diagram illustrating information interaction in the process of joining a trust ring by the device C. Referring to fig. 21, in the process that the device C joins the trust ring 1, the device C selects the device B as an old device, inputs a screen locking code pw22 of the device B when the screen locking code pw22 of the old device is input, generates an authentication parameter pase 22 of the device B based on the screen locking code pw22, and then sends the authentication parameter pase 22 of the device B to the trust ring cloud. After confirming that the PAKE22 is consistent with the authentication parameter PAKE21 of the device B stored in the trust ring 1, the trust ring cloud returns the master key ciphertext EMK21 of the device B to the device C. Then, the device C decrypts MK from the EMK21, encrypts MK based on the screen locking code pw31 of the device C, generates a master key ciphertext EMK31 of the device C, that is, a third master key ciphertext, and generates an authentication parameter pase 31 of the device C based on the screen locking code pw31 of the device C, and then the device C sends the EMK31 and pase 31 to the trust ring cloud, and the trust ring cloud adds the device C to the trust ring 1. At this point, the process of joining the trust ring 1 by the device C is completed, and the device C completes registration.
After device C joins trust ring 1, the trust ring 1 data managed in the trust ring cloud is shown in table 3:
TABLE 3
UID UDID Parameter PAKE Master key ciphertext
Account number
1 Device A PAKE11 EMK11
Account number
1 Device B PAKE21 EMK21
Account number
1 Device C PAKE31 EMK31
After the device C joins the trust ring 1, the service data in the device C may be encrypted by the master key MK and then synchronized to the account management server, or other data synchronized in the account management server in the ring device may be synchronized to the device C. For the process of synchronizing service data to the account management server, reference is made to the foregoing description of the process of synchronizing service data to the account management server by the device a, and for the process of synchronizing service data to the device C by the account management server, reference is made to the foregoing description of the process of synchronizing service data to the local device B by the device B from the account management server, which is not described herein again.
The electronic device, the computer storage medium, the computer program product, or the chip provided in this embodiment are all configured to execute the corresponding method provided above, so that the beneficial effects achieved by the electronic device, the computer storage medium, the computer program product, or the chip may refer to the beneficial effects in the corresponding method provided above, and are not described herein again.
Through the description of the above embodiments, those skilled in the art will understand that, for convenience and simplicity of description, only the division of the above functional modules is used as an example, and in practical applications, the above function distribution may be completed by different functional modules as needed, that is, the internal structure of the device may be divided into different functional modules to complete all or part of the above described functions.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, a module or a unit may be divided into only one logic function, and may be implemented in other ways, for example, a plurality of units or components may be combined or integrated into another apparatus, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
Units described as separate parts may or may not be physically separate, and parts displayed as units may be one physical unit or a plurality of physical units, may be located in one place, or may be distributed to a plurality of different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit may be implemented in the form of hardware, or may also be implemented in the form of a software functional unit.
Any contents of the respective embodiments of the present application, and any contents of the same embodiment, can be freely combined. Any combination of the above is within the scope of the present application.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application, or portions of the technical solutions that substantially contribute to the prior art, or all or portions of the technical solutions may be embodied in the form of a software product, where the software product is stored in a storage medium and includes several instructions to enable a device (which may be a single chip, a chip, or the like) or a processor (processor) to execute all or part of the steps of the methods of the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.

Claims (22)

1. A data protection method is applied to a second electronic device, and the method comprises the following steps:
receiving a second screen locking code of second electronic equipment input by a user, wherein the second electronic equipment logs in a first account;
when the second screen locking code passes verification, receiving a first screen locking code of first electronic equipment input by a user, wherein the first electronic equipment is equipment in ring equipment information of a first trust ring corresponding to the first account acquired from a first server;
when the identity verification of the first electronic equipment based on the first screen locking code passes, receiving a first master key ciphertext of the first electronic equipment, which is sent by the first server;
decrypting the first master key ciphertext based on the first screen locking code to obtain a master key;
encrypting the master key based on the second screen locking code to generate a second master key ciphertext of the second electronic device, and generating a second authentication parameter based on the second screen locking code;
sending a ring addition request to a first server to cause the first server to add the second master key ciphertext and a second authentication parameter to trust ring data of the first trust ring.
2. The method of claim 1, wherein after receiving the user input of the second screen locking code of the second electronic device, further comprising:
sending an on-ring device information acquisition request to the first server, wherein the on-ring device information acquisition request carries an account identification of the first account;
receiving ring-in device information of a first trust ring corresponding to the first account returned by the server, wherein the ring-in device comprises first electronic equipment;
and displaying the screen locking code input interface of the first electronic equipment.
3. The method of claim 1, wherein after receiving the user input of the second screen locking code of the second electronic device, further comprising:
sending a ring device information acquisition request to the first server, wherein the ring device information acquisition request carries an account identifier of the first account;
receiving ring-in-device information of a first trust ring corresponding to the first account returned by the server, wherein the ring-in-device information comprises first electronic equipment and third electronic equipment;
and responding to the selected operation of the first electronic equipment in the ring equipment information, and displaying a screen locking code input interface of the first electronic equipment.
4. The method of claim 1, before receiving a first master key ciphertext of the first electronic device sent by the first server when the first electronic device passes authentication based on the first lock screen code, further comprising:
generating a first authentication parameter based on the first screen locking code;
and sending the first authentication parameter to the first server so that the first server performs identity verification on the first electronic device according to the first authentication parameter.
5. The method of claim 1, further comprising, before receiving a first screen locking code of a first electronic device input by a user when the second screen locking code is verified, the method comprising:
comparing the second screen locking code with a locally stored screen locking code of the second electronic equipment;
and when the second screen locking code is consistent with the screen locking code of the second electronic equipment stored locally, determining that the second screen locking code passes verification.
6. The method of claim 1, wherein encrypting the master key based on the second screen lock code to generate a second master key ciphertext for the second electronic device comprises:
generating a third derivative key according to the second screen locking code;
generating a fourth derivative key according to the third derivative key;
and encrypting the master key according to a fourth derivative key to obtain a second master key ciphertext of the second electronic device.
7. The method of claim 1, wherein generating a second authentication parameter based on the second screen locking code comprises:
generating a third derivative key according to the second screen locking code;
generating a second shared value according to the third derivative key;
and encrypting the second shared value according to the HSM public key generated by the first server side to obtain the second authentication parameter.
8. The method of claim 1, further comprising:
detecting a registration state of the second electronic device in case of receiving a registration request;
sending a registration state comparison request to a first server under the condition that the second electronic device is not registered, wherein the registration state comparison request carries a device identifier of the second electronic device and an account identifier of the first account;
receiving a second registration state confirmation message returned by the first server, wherein the second registration state confirmation message is used for indicating that a first trust ring exists under the first account but the second electronic device is not on the first trust ring.
9. The method of claim 1, further comprising:
deriving a first service key based on the master key, and encrypting first service data by using the first service key to obtain a first service data ciphertext;
and sending the first service data ciphertext to a second server so that the second server stores the first service data ciphertext.
10. The method of claim 9, further comprising:
acquiring a second service data ciphertext from a second server;
deriving a first traffic key based on the master key;
and decrypting the second service data ciphertext by using the first service key to obtain second service data.
11. An electronic device comprising, as a second electronic device, a trust ring service module and a trust ring module, wherein:
the trust ring service module is configured to:
receiving a second screen locking code of second electronic equipment input by a user, wherein the second electronic equipment logs in a first account;
when the second screen locking code passes verification, receiving a first screen locking code of first electronic equipment input by a user, wherein the first electronic equipment is in-loop equipment information of a first trust loop corresponding to the first account acquired from a first server;
when the identity verification of the first electronic equipment based on the first screen locking code passes, receiving a first master key ciphertext of the first electronic equipment, which is sent by the first server;
sending the first master key ciphertext to the trust ring module;
the trust ring module is configured to:
decrypting the first master key ciphertext based on the first screen locking code to obtain a master key;
encrypting the master key based on the second screen locking code to generate a second master key ciphertext of the second electronic device;
sending the second master key ciphertext to the trust ring service module;
the trust ring service module is further configured to:
generating a second authentication parameter based on the second screen locking code;
sending a ring addition request to a first server to cause the first server to add the second master key ciphertext and a second authentication parameter to trust ring data of the first trust ring.
12. The electronic device of claim 11,
the trust ring service module is further configured to:
sending a ring device information acquisition request to the first server, wherein the ring device information acquisition request carries an account identifier of the first account;
receiving ring-in device information of a first trust ring corresponding to the first account returned by the server, wherein the ring-in device comprises first electronic equipment;
and displaying the screen locking code input interface of the first electronic equipment.
13. The electronic device of claim 11,
the trust ring service module is further configured to:
sending a ring device information acquisition request to the first server, wherein the ring device information acquisition request carries an account identifier of the first account;
receiving ring-in-device information of a first trust ring corresponding to the first account returned by the server, wherein the ring-in-device information comprises first electronic equipment and third electronic equipment;
and responding to the selected operation of the first electronic equipment in the ring equipment information, and displaying a screen locking code input interface of the first electronic equipment.
14. The electronic device of claim 11,
the trust ring service module is further configured to:
generating a first authentication parameter based on the first screen locking code;
and sending the first authentication parameter to the first server so that the first server performs identity verification on the first electronic device according to the first authentication parameter.
15. The electronic device of claim 11,
the trust ring service module is further configured to:
comparing the second screen locking code with a locally stored screen locking code of the second electronic equipment;
and when the second screen locking code is consistent with the screen locking code of the second electronic equipment stored locally, determining that the second screen locking code passes verification.
16. The electronic device of claim 11, wherein the trust ring module, when encrypting the master key based on the second screen locking code and generating a second master key ciphertext of the second electronic device, is specifically configured to:
receiving a third derived key generated by the trust ring service module according to the second screen locking code;
generating a fourth derivative key according to the third derivative key;
and encrypting the master key according to a fourth derivative key to obtain a second master key ciphertext of the second electronic device.
17. The electronic device of claim 11, wherein when the trust ring service module generates the second authentication parameter based on the second screen locking code, the trust ring service module is specifically configured to:
generating a third derivative key according to the second screen locking code;
generating a second shared value according to the third derivative key;
and encrypting the second shared value according to the HSM public key generated by the first server side to obtain the second authentication parameter.
18. The electronic device of claim 11, wherein:
the trust ring service module is further configured to:
detecting a registration state of the second electronic device in case of receiving a registration request;
sending a registration state comparison request to a first server under the condition that the second electronic device is not registered, wherein the registration state comparison request carries a device identifier of the second electronic device and an account identifier of the first account;
receiving a second registration state confirmation message returned by the first server, wherein the second registration state confirmation message is used for indicating that a first trust ring exists under the first account but the second electronic device is not on the first trust ring.
19. The electronic device of claim 11, further comprising: the system comprises a service data synchronization service module, a service data storage service module and a key management module;
the trust ring service module is further configured to:
deriving a first traffic key based on the master key,
the service data storage service module is used for:
sending the first service data to the key management module;
the key management module is configured to:
reading the first service key from the trust ring module, and encrypting the first service data by using the first service key to obtain a first service data ciphertext; sending the first business data cipher text to the business data storage service module;
the service data storage service module is further configured to:
and sending the first service data ciphertext to a second server through the service data synchronization service module so that the second server stores the first service data ciphertext.
20. The electronic device of claim 19,
the service data synchronization service module is further configured to:
acquiring a second service data ciphertext from the second server, and storing the second service data ciphertext to the service data storage service module;
the service data storage service module is further configured to:
sending second service data to the key management module;
the key management module is further configured to:
and reading the first service key from the trust ring module, decrypting the second service data by using the first service key to obtain second service data, and storing the second service data into the service data storage service module.
21. A data protection system, comprising a first electronic device, a second electronic device, and a first server, wherein:
the second electronic device to:
receiving a second screen locking code of second electronic equipment input by a user, wherein the second electronic equipment logs in a first account;
when the second screen locking code passes verification, receiving a first screen locking code of first electronic equipment input by a user, wherein the first electronic equipment is in-loop equipment information of a first trust loop corresponding to the first account acquired from a first server;
when the identity verification of the first electronic equipment based on the first screen locking code passes, receiving a first master key ciphertext of the first electronic equipment, which is sent by the first server;
decrypting the first master key ciphertext based on the first screen locking code to obtain a master key;
encrypting the master key based on the second screen locking code to generate a second master key ciphertext of the second electronic device, and generating a second authentication parameter based on the second screen locking code;
sending a ring-adding request to the first server;
the first server is configured to:
and responding to a ring adding request sent by the second electronic equipment, and adding the second master key ciphertext and a second authentication parameter into the trust ring data of the first trust ring.
22. A computer-readable storage medium, characterized by comprising a computer program which, when run on an electronic device, causes the electronic device to perform the data protection method according to any one of claims 1-10.
CN202111408375.8A 2021-11-19 2021-11-19 Data protection method and system and electronic equipment Active CN115037455B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111408375.8A CN115037455B (en) 2021-11-19 2021-11-19 Data protection method and system and electronic equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111408375.8A CN115037455B (en) 2021-11-19 2021-11-19 Data protection method and system and electronic equipment

Publications (2)

Publication Number Publication Date
CN115037455A CN115037455A (en) 2022-09-09
CN115037455B true CN115037455B (en) 2023-04-14

Family

ID=83117886

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111408375.8A Active CN115037455B (en) 2021-11-19 2021-11-19 Data protection method and system and electronic equipment

Country Status (1)

Country Link
CN (1) CN115037455B (en)

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170288866A1 (en) * 2016-03-30 2017-10-05 AVAST Software s.r.o. Systems and methods of creating a distributed ring of trust
US20190342301A1 (en) * 2018-05-02 2019-11-07 Seagate Technology Llc Local Authentication of Devices Arranged as a Trust Family
CN113609498B (en) * 2021-07-15 2022-09-30 荣耀终端有限公司 Data protection method and electronic equipment

Also Published As

Publication number Publication date
CN115037455A (en) 2022-09-09

Similar Documents

Publication Publication Date Title
US20220247739A1 (en) Multifactor Contextual Authentication and Entropy from Device or Device Input or Gesture Authentication
US10223520B2 (en) System and method for integrating two-factor authentication in a device
US10826882B2 (en) Network-based key distribution system, method, and apparatus
CN107251035B (en) Account recovery protocol
WO2020143414A1 (en) Wireless network access method, device, equipment and system
CN108111473B (en) Unified management method, device and system for hybrid cloud
KR102202547B1 (en) Method and system for verifying an access request
US20100043056A1 (en) Portable device association
US11233647B1 (en) Digital identity authentication system
CN110719203B (en) Operation control method, device and equipment of intelligent household equipment and storage medium
US11831753B2 (en) Secure distributed key management system
WO2010019370A2 (en) Protocol for device to station association
CN110247758B (en) Password management method and device and password manager
JP2017152880A (en) Authentication system, key processing coordination method, and key processing coordination program
CN114760112B (en) Wireless local area network-oriented intelligent home equipment networking method, system, equipment and storage medium
CN115037451B (en) Data protection method and electronic equipment
CN115037453B (en) Data protection method and system and electronic equipment
CN115021894B (en) Data protection method, system and electronic equipment
CN115037455B (en) Data protection method and system and electronic equipment
CN115037450B (en) Data protection method and electronic equipment
CN115037454B (en) Data protection method and electronic equipment
CN115021895B (en) Data protection method and system and electronic equipment
CN115037456B (en) Data protection method, system and electronic equipment
CN115037452B (en) Data protection method, system and electronic equipment
CN117879819B (en) Key management method, device, storage medium, equipment and computing power service system

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