System for implementing multi-application authorization password based on trusted device hierarchy
By generating a unique authorization password for each application in the trusted device hierarchy authorization password system, the risk of data tampering caused by multiple applications sharing the same password is resolved, achieving higher security and isolation.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- KYLIN CORP
- Filing Date
- 2025-12-23
- Publication Date
- 2026-05-12
AI Technical Summary
In existing technologies, multiple applications share the same trusted device hierarchy authorization password, which makes the authorization password easy to be abused and poses a risk of data tampering.
Design a system for implementing multi-application authorization passwords based on trusted device hierarchy. Through an interface service module, a hierarchy authorization management program, a trusted device management service module, and a hierarchy authorization password ciphertext storage module, generate and manage unique authorization passwords for different applications, encrypt and store them, and decrypt and verify them to ensure that each application has a unique hierarchy authorization password.
It achieves authorization verification isolation between different applications, prevents abuse of authorization passwords, improves the security of hierarchy authorization passwords, and prevents data tampering.
Smart Images
Figure CN121365418B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of trusted security technology, and more specifically to an implementation system for multi-application authorization passwords based on trusted device hierarchy. Background Technology
[0002] The Trusted Platform Module (TPM) is a security coprocessor with cryptographic algorithm capabilities, providing a protected cryptographic engine, secure key management, platform integrity measurement, storage and reporting, hierarchical structure, and access control.
[0003] The Trusted Cryptography Module (TCM) is a set of secure chip standards for trusted computing independently developed in my country. Functionally, it is comparable to the international TPM, and features a protected cryptographic engine, secure key management, platform integrity measurement, storage and reporting, hierarchical structure, and access control.
[0004] TPM 2.0 / TCM2.0 uses multiple independent hierarchies (such as platform hierarchy, owner hierarchy, endorsement hierarchy) to isolate and manage keys and data for different purposes.
[0005] Hierarchy authorization passwords are an independent authorization mechanism at each level, enabling fine-grained access control.
[0006] A trusted hierarchy can only be configured with one authorization password. When multiple applications request access to the hierarchy, they all use the same password to authenticate and obtain authorization. If the hierarchy authorization data is leaked, malicious users can exploit the hierarchy authorization password to arbitrarily modify keys and data within the hierarchy. For example... Figure 1 As shown: When a trusted device sets a hierarchy authorization password, if user 1 has permission to execute application 1, and user 2 has permission to execute application 2 and application 3, and applications 1, 2, and 3 create NV indexes on the same hierarchy, then when user 2 knows the hierarchy authorization password, they can maliciously delete the NV index space created by application 1 and re-initialize it, causing data tampering. Summary of the Invention
[0007] To address the shortcomings of existing technologies, this invention provides a system for implementing multi-application authorization passwords based on trusted device hierarchy, including an interface service module, a hierarchy authorization management program, a trusted device management service module, and a hierarchy authorization password ciphertext storage module.
[0008] The interface service module is connected to the trusted device management service module. It is oriented towards different applications and provides application authorization passwords through the unique ID of the application to realize the service call of multiple authorization passwords of trusted device hierarchy. This allows different applications to obtain a unique trusted device hierarchy authorization password through different application authorization passwords.
[0009] The hierarchy authorization management program connects to the trusted device management service module to receive the administrator authorization password entered by the authorization administrator and / or the application authorization password transmitted from the interface service module to the trusted device management service module. It manages the trusted device hierarchy authorization password, thereby generating a trusted device hierarchy authorization password encrypted with the administrator authorization password, generating or destroying the ciphertext of the trusted device hierarchy authorization password encrypted with the application authorization password. The ciphertext of the generated trusted device hierarchy authorization password encrypted with the application authorization password is stored in the hierarchy authorization password ciphertext storage module.
[0010] The Trusted Device Management Service Module is connected to the Interface Service Module and the Hierarchy Authorization Password Ciphertext Storage Module. It is used to decrypt the ciphertext of the Trusted Device Hierarchy Authorization Password, which is encrypted by the application authorization password received by the Interface Service Module, to obtain the Trusted Device Hierarchy Authorization Password.
[0011] This includes a trusted software stack and a trusted device. The trusted device management service module, the trusted software stack, and the trusted device are connected sequentially. When an application needs to access a trusted device, the trusted device management service module uses the application's unique ID as an index to find the application's authorization password. It then decrypts the encrypted trusted device hierarchy authorization password stored in the hierarchy authorization password ciphertext storage module using the application's authorization password to obtain the trusted device hierarchy authorization password. Based on the plaintext of the trusted device hierarchy authorization password, authentication is performed to determine the application's access rights to the trusted device.
[0012] The hierarchy authorization management program manages the trusted device hierarchy authorization passwords and generates encrypted trusted device hierarchy authorization passwords, including:
[0013] Step S11: Enter the administrator authorization password;
[0014] Step S12: Call the trusted device to generate a random number, and use the generated random number as the trusted device hierarchy authorization password;
[0015] Step S13: Encrypt the trusted device hierarchy authorization password using the administrator authorization password;
[0016] Step S14: Calculate the unique ID of the hierarchy authorization manager;
[0017] Step S15: Using the unique ID of the hierarchy authorization management program as an index, obtain the trusted device hierarchy authorization password encrypted with the administrator authorization password.
[0018] The hierarchy authorization management program also manages trusted device hierarchy authorization passwords, including canceling the setting of trusted device hierarchy authorization passwords.
[0019] The hierarchy authorization management program includes the following steps to cancel the trusted device hierarchy authorization password setting:
[0020] Step S21: Enter the administrator authorization password;
[0021] Step S22: Decrypt the trusted device hierarchy authorization password using the administrator authorization password;
[0022] Step S23: Cancel the setting of the trusted device hierarchy authorization password;
[0023] Step S24: Delete the trusted device hierarchy authorization password encrypted with the application authorization password.
[0024] The hierarchy authorization management program generates encrypted trusted device hierarchy authorization passwords, which include:
[0025] Step S31: Enter the administrator authorization password;
[0026] Step S32: Decrypt the trusted device hierarchy authorization password, which is encrypted by the administrator authorization password generated by the hierarchy authorization management program, using the administrator authorization password to obtain the decrypted trusted device hierarchy authorization password.
[0027] Step S33: Set the application authorization password;
[0028] Step S34: Encrypt the trusted device hierarchy authorization password using the application authorization password;
[0029] Step S35: Calculate the application's unique ID;
[0030] Step S36: Using the application's unique ID as an index, obtain the ciphertext of the trusted device hierarchy authorization password encrypted with the application's authorization password.
[0031] In step S35, a unique ID for the application is calculated using a hash algorithm.
[0032] The hierarchy authorization management program destroys the encrypted trusted device hierarchy authorization password, which includes:
[0033] Step S41: Enter the administrator authorization password;
[0034] Step S42: Decrypt the trusted device hierarchy authorization password, which is encrypted by the administrator authorization password generated by the hierarchy authorization management program, using the administrator authorization password, to obtain the decrypted trusted device hierarchy authorization password.
[0035] Step S43: Enter the application authorization password;
[0036] Step S44: Using the application authorization password, decrypt the ciphertext of the trusted device hierarchy authorization password encrypted by the application authorization password to obtain the decrypted trusted device hierarchy authorization password.
[0037] Step S45: Determine whether the trusted device hierarchy authorization passwords decrypted in steps S42 and S44 are consistent: if they are inconsistent, do not destroy; if they are consistent, destroy the ciphertext of the trusted device hierarchy authorization password encrypted by the application authorization password.
[0038] The hierarchy authorization password encrypted storage module is located in the TEE secure memory or encryption card device.
[0039] The encrypted trusted device hierarchy authorization password for the application authorization password is stored in a format that consists of a 32-byte program hash value plus a 16-byte SM4-encrypted authorization password ciphertext.
[0040] This invention can solve the problem of abuse of hierarchy authorization passwords caused by the use of the same permission verification password among multiple applications when obtaining hierarchy authorization. Attached Figure Description
[0041] Figure 1A diagram illustrating how multiple applications use the same hierarchy authorization password to tamper with NV index data under the hierarchy;
[0042] Figure 2 Mind map of this invention;
[0043] Figure 3 The logical architecture diagram of the system for implementing multi-application authorization passwords based on trusted device hierarchy according to the present invention;
[0044] Figure 4 The flowchart of the hierarchy authorization management program of the present invention is as follows: it receives the initialization administrator authorization password to generate a trusted device hierarchy authorization password encrypted with the administrator authorization password.
[0045] Figure 5 The flowchart of the implementation of the hierarchy authorization management program of the present invention to cancel the trusted device hierarchy authorization password;
[0046] Figure 6 The flowchart of the implementation of the hierarchy authorization management program of the present invention to generate encrypted trusted device hierarchy authorization passwords for application authorization passwords;
[0047] Figure 7 The flowchart illustrates the implementation of the hierarchy authorization management program of this invention to destroy the encrypted trusted device hierarchy authorization password of the application authorization password. Detailed Implementation
[0048] To gain a better understanding of the technical solution and beneficial effects of the present invention, the technical solution of the present invention and its beneficial effects are described in detail below with reference to the accompanying drawings.
[0049] In this invention, the terminology used and its interpretation are as follows:
[0050] TPM: Trusted Platform Module;
[0051] TCM: Trusted Cryptography Module;
[0052] Trusted devices: refer to the Trusted Platform Module (TPM) and the Trusted Cryptography Module (TCM).
[0053] Hierarchy: Refers to a collection of interconnected entities managed as a whole. These entities include permanent objects (i.e., hierarchy handles), the master object at the root of the tree structure, and other objects in the tree (such as keys). NV indexes belong to a hierarchy but are not within the tree structure. Except for permanent entities, all other entities can be cleared as a whole.
[0054] This invention proposes a method based on trusted device hierarchy multi-authorization passwords. When using hierarchy authorization across different applications, each application has its own unique authorization password for hierarchy authorization verification, ensuring isolation of authorization verification between different applications and preventing password abuse. The design concept of this invention is as follows: Figure 2 As shown, when using the same key to unlock, the right to use this key is abstracted into N different keys to obtain that right. These N different keys correspond to opening N different boxes and retrieving the keys to unlock them. The N different keys can correspond to N different application authorization passwords, the key obtained from opening a box can correspond to a unique hierarchy authorization password, and the unlocking process corresponds to using the hierarchy authorization password to perform hierarchy authorization verification on a trusted device.
[0055] like Figure 3 As shown, the system for implementing multi-application authorization passwords based on trusted device hierarchy according to the present invention includes an interface service module, a hierarchy authorization management program, a trusted device management service module, a hierarchy authorization password ciphertext storage module, a trusted software stack, and a trusted device. The functions and roles of each module are described in detail below.
[0056] I. Interface Service Module
[0057] The interface service module connects with the trusted device management service module. It is designed for different applications and provides application authorization passwords through the application's unique ID to enable the service call of multiple authorization passwords for trusted device hierarchy. This allows different applications to obtain a unique trusted device hierarchy authorization password through different application authorization passwords.
[0058] The interface service module includes trusted function external call interfaces, interface function processing, and interface protocol sending. The external call interface function mainly manages the authorization password part of the trusted execution command hierarchy, so as to achieve external service calls based on multiple authorization passwords of trusted device hierarchy.
[0059] II. Hierarchy Authorization Management Procedure
[0060] The hierarchy authorization management program connects to the trusted device management service module. It executes management functions and sends interface protocols by calling the trusted device management service module. Specifically, it receives the administrator authorization password entered by the authorized administrator and / or the application authorization password transmitted from the interface service module to the trusted device management service module. It then manages the trusted device hierarchy authorization password, generating encrypted trusted device hierarchy authorization passwords, destroying encrypted trusted device hierarchy authorization passwords, and generating or destroying ciphertext encrypted trusted device hierarchy authorization passwords. The generated ciphertext of the encrypted trusted device hierarchy authorization password (e.g., ...) is used to... Figure 3 The encrypted trusted device hierarchy authorization passwords (password 0, password 1, ..., password N) shown are stored in the hierarchy authorization password storage module. 1. Initial administrator authorization password encrypted trusted device hierarchy authorization password.
[0061] like Figure 4 As shown, the process by which the hierarchy authorization management program receives the initialization administrator authorization password to generate a trusted device hierarchy authorization password encrypted with the administrator authorization password includes:
[0062] 1-1. Enter the initialization operation and check if the current hierarchy has an authorization password set. If yes, exit the initial setup. If no, proceed to step 1-2.
[0063] 1-2. Enter the administrator authorization password;
[0064] 1-3. Call the trusted device to generate a random number, and use the generated random number as the trusted device hierarchy authorization password;
[0065] 1-4. Encrypt the trusted device hierarchy authorization password using the administrator's authorization password;
[0066] 1-5. Calculate the unique ID of the hierarchy authorization management program;
[0067] 1-6. Using the unique ID of the hierarchy authorization management program as an index, obtain the trusted device hierarchy authorization password encrypted with the administrator authorization password. 2. Cancel the trusted device hierarchy authorization password.
[0068] like Figure 5As shown, the process by which the hierarchy authorization management program revokes the trusted device hierarchy authorization password includes:
[0069] 2-1. Enter the initialization operation and check if the current hierarchy has an authorization password set. If yes, exit the initial setup. If no, proceed to 2-2.
[0070] 2-2. Enter the administrator authorization password;
[0071] 2-3. Decrypt the trusted device hierarchy authorization password using the administrator's authorization password;
[0072] 2-4. Disable the trusted device hierarchy authorization password setting;
[0073] 2-5. Delete the trusted device hierarchy authorization password encrypted with the application authorization password.
[0074] 3. Generate ciphertext of the trusted device hierarchy authorization password, which is encrypted with the application authorization password.
[0075] like Figure 6 As shown, the process by which the hierarchy authorization manager generates ciphertext for the trusted device hierarchy authorization password, which is encrypted with the application authorization password, includes:
[0076] 3-1. Enter the generation operation and check if the current hierarchy has an authorization password set. If not, exit the initial settings. If yes, proceed to 3-2.
[0077] 3-2. Enter the administrator authorization password;
[0078] 3-3: Using the administrator authorization password, decrypt the trusted device hierarchy authorization password encrypted by the administrator authorization password generated by the hierarchy authorization management program to obtain the decrypted trusted device hierarchy authorization password;
[0079] 3-4: Set the application authorization password through the corresponding application;
[0080] 3-5: Encrypt the trusted device hierarchy authorization password using the application authorization password;
[0081] 3-6: Calculate the unique ID of the application. The method for calculating the unique ID is not limited in this invention. For example, a hash algorithm can be used to calculate the unique ID of the application.
[0082] 3-7: Using the application's unique ID as an index, obtain the ciphertext of the trusted device hierarchy authorization password encrypted with the application's authorization password.
[0083] 4. Destroy the encrypted trusted device hierarchy authorization password, which is encrypted with the application authorization password.
[0084] like Figure 7 As shown, the process by which the hierarchy authorization manager generates ciphertext for the trusted device hierarchy authorization password, which is encrypted with the application authorization password, includes:
[0085] 4-1. Enter the destruction operation and check if the current hierarchy has an authorization password set. If not, exit the initial settings. If yes, proceed to step 4-2.
[0086] 4-2: Enter the administrator authorization password;
[0087] 4-3: Using the administrator authorization password, decrypt the trusted device hierarchy authorization password encrypted by the administrator authorization password generated by the hierarchy authorization management program to obtain the decrypted trusted device hierarchy authorization password;
[0088] 4-4: Enter the application authorization password;
[0089] 4-5: Using the application authorization password, decrypt the ciphertext of the trusted device hierarchy authorization password encrypted by the application authorization password to obtain the decrypted trusted device hierarchy authorization password;
[0090] 4-6: Determine if the trusted device hierarchy authorization passwords decrypted in 4-3 and 4-5 are consistent: If they are inconsistent, do not destroy; if they are consistent, destroy the ciphertext of the trusted device hierarchy authorization password encrypted with the application authorization password. III. Trusted Device Management Service Module, Trusted Software Stack, and Trusted Devices
[0091] The Trusted Device Management Service Module provides authorization management functions as a service, which can run in an operating system or a secure environment. This invention does not limit the security environment; it can be in environments protected by encrypted memory, TEE isolation environments, etc. It is connected to the Interface Service Module, the Hierarchy Authorization Password Ciphertext Storage Module, the Trusted Software Stack, and the Trusted Device. It is used to decrypt the ciphertext of the Trusted Device Hierarchy Authorization Password, which is encrypted with the application authorization password received from the Interface Service Module, to obtain the Trusted Device Hierarchy Authorization Password. When an application needs to access a trusted device, the Trusted Device Management Service Module uses the application's unique ID as an index to find the application authorization password, and then decrypts the ciphertext of the Trusted Device Hierarchy Authorization Password, which is encrypted with the application authorization password, stored in the Hierarchy Authorization Password Ciphertext Storage Module using the application authorization password (corresponding to...). Figure 3 The process involves "executing the interface containing hierarchy authorization operations" and "decrypting the corresponding hierarchy authorization password ciphertext based on the application's authorization password" to obtain the trusted device's hierarchy authorization password. Authentication is then performed based on the plaintext of the trusted device's hierarchy authorization password to determine the application's operational permissions on the trusted device (corresponding to...). Figure 3 (Obtain the hierarchy authorization password and execute the corresponding authorized function).
[0092] The Trusted Software Stack connects the Trusted Device Management Service module and trusted devices. It is an open-source software stack officially maintained and standardized by the Trusted Computing Group (TCG) to support TPM 2.0 hardware. Its core function is to abstract the complex, low-level TPM 2.0 hardware commands and communication interfaces into a set of standard, easy-to-use, and secure programming interfaces (APIs) for software developers to use.
[0093] IV. Hierarchy Authorization Password Encryption Storage Module
[0094] The hierarchy authorization password ciphertext storage module is located in secure storage such as TEE secure memory and encryption card devices. It mainly stores the ciphertext of the trusted device hierarchy authorization password encrypted by the management program authorization password and the ciphertext of the trusted device hierarchy authorization password encrypted by the application authorization password.
[0095] In this invention, the hierarchy authorization password ciphertext storage format can be set to a 32-byte program hash value plus a 16-byte SM4-encrypted authorization password ciphertext. This invention provides the hierarchy authorization password ciphertext storage format for reference only and does not impose any limitations.
[0096] This invention proposes a design method for multiple authorization passwords based on trusted device hierarchy. It separates the allocation rights of hierarchy authorization passwords from the usage rights of applications based on the authorization management program. Furthermore, it implements secure protection of hierarchy authorization passwords when multiple applications call trusted devices, ensuring that each application has its own unique authorization password. This prevents the abuse of trusted device hierarchy passwords and improves the security of hierarchy authorization password usage.
[0097] Although the present invention has been described using the above preferred embodiments, it is not intended to limit the scope of protection of the present invention. Any changes and modifications made by those skilled in the art to the above embodiments without departing from the spirit and scope of the present invention shall still fall within the scope of protection of the present invention. Therefore, the scope of protection of the present invention shall be defined by the claims.
Claims
1. A system for implementing multi-application authorization passwords based on trusted device hierarchy, characterized in that: It includes an interface service module, a hierarchy authorization management program, a trusted device management service module, and a hierarchy authorization password encrypted storage module. The trusted device is a Trusted Platform Module (TPM) or a Trusted Cryptographic Module (TCM), and the hierarchy is a hierarchical structure of TPM / TCM. Each hierarchy only supports setting a single authorization password. The interface service module is connected to the trusted device management service module. It is oriented towards different applications and provides application authorization passwords through the unique ID of the application to realize the service call of multiple authorization passwords of trusted device hierarchy. This allows different applications to obtain a unique trusted device hierarchy authorization password through different application authorization passwords. The hierarchy authorization management program connects to the trusted device management service module to receive the administrator authorization password entered by the authorization administrator and / or the application authorization password transmitted from the interface service module to the trusted device management service module. It manages the trusted device hierarchy authorization password, thereby generating a trusted device hierarchy authorization password encrypted with the administrator authorization password, generating or destroying the ciphertext of the trusted device hierarchy authorization password encrypted with the application authorization password. The ciphertext of the generated trusted device hierarchy authorization password encrypted with the application authorization password is stored in the hierarchy authorization password ciphertext storage module. The hierarchy authorization management program manages the trusted device hierarchy authorization passwords and generates encrypted trusted device hierarchy authorization passwords, including: Step S11: Enter the administrator authorization password; Step S12: Call the trusted device to generate a random number, and use the generated random number as the trusted device hierarchy authorization password; Step S13: Encrypt the trusted device hierarchy authorization password using the administrator authorization password; Step S14: Calculate the unique ID of the hierarchy authorization manager; Step S15: Using the unique ID of the hierarchy authorization management program as an index, obtain the trusted device hierarchy authorization password encrypted with the administrator authorization password; The Trusted Device Management Service Module is connected to the Interface Service Module and the Hierarchy Authorization Password Ciphertext Storage Module. It is used to decrypt the ciphertext of the Trusted Device Hierarchy Authorization Password, which is encrypted by the application authorization password received by the Interface Service Module, to obtain the Trusted Device Hierarchy Authorization Password. It also includes a trusted software stack and a trusted device. The trusted device management service module, the trusted software stack, and the trusted device are connected in sequence. When an application needs to access a trusted device, the trusted device management service module uses the application's unique ID value as an index to find the application's authorization password. It then decrypts the ciphertext stored in the hierarchy authorization password ciphertext storage module using the application's authorization password. The ciphertext is the trusted device hierarchy authorization password encrypted by the application's authorization password. After decryption, the trusted device hierarchy authorization password is obtained. Authentication is performed based on the plaintext of the trusted device hierarchy authorization password to determine the application's operation permissions on the trusted device.
2. The system for implementing multi-application authorization passwords based on trusted device hierarchy as described in claim 1, characterized in that: The hierarchy authorization management program also manages trusted device hierarchy authorization passwords, including canceling the setting of trusted device hierarchy authorization passwords.
3. The system for implementing multi-application authorization passwords based on trusted device hierarchy as described in claim 2, characterized in that: The hierarchy authorization management program can disable the trusted device hierarchy authorization password setting, including: Step S21: Enter the administrator authorization password; Step S22: Decrypt the trusted device hierarchy authorization password using the administrator authorization password; Step S23: Cancel the setting of the trusted device hierarchy authorization password; Step S24: Delete the trusted device hierarchy authorization password encrypted with the application authorization password.
4. The system for implementing multi-application authorization passwords based on trusted device hierarchy as described in claim 1, characterized in that: The hierarchy authorization manager generates application authorization passwords. The encrypted trusted device hierarchy authorization password includes: Step S31: Enter the administrator authorization password; Step S32: Decrypt the trusted device hierarchy authorization password, which is encrypted by the administrator authorization password generated by the hierarchy authorization management program, using the administrator authorization password to obtain the decrypted trusted device hierarchy authorization password. Step S33: Set the application authorization password; Step S34: Encrypt the trusted device hierarchy authorization password using the application authorization password; Step S35: Calculate the application's unique ID; Step S36: Using the application's unique ID as an index, obtain the ciphertext of the trusted device hierarchy authorization password encrypted with the application's authorization password.
5. The system for implementing multi-application authorization passwords based on trusted device hierarchy as described in claim 4, characterized in that: In step S35, a unique ID for the application is calculated using a hash algorithm.
6. The system for implementing multi-application authorization passwords based on trusted device hierarchy as described in claim 1, characterized in that: The hierarchy authorization manager destroys application authorization passwords. The encrypted trusted device hierarchy authorization password includes: Step S41: Enter the administrator authorization password; Step S42: Decrypt the trusted device hierarchy authorization password, which is encrypted by the administrator authorization password generated by the hierarchy authorization management program, using the administrator authorization password to obtain the decrypted trusted device hierarchy authorization password. Step S43: Enter the application authorization password; Step S44: Using the application authorization password, decrypt the ciphertext of the trusted device hierarchy authorization password encrypted by the application authorization password to obtain the decrypted trusted device hierarchy authorization password. Step S45: Determine whether the trusted device hierarchy authorization passwords decrypted in steps S42 and S44 are consistent: if they are inconsistent, do not destroy; if they are consistent, destroy the ciphertext of the trusted device hierarchy authorization password encrypted by the application authorization password.
7. The system for implementing multi-application authorization passwords based on trusted device hierarchy as described in claim 1, characterized in that: The hierarchy authorization password ciphertext storage module is located in the TEE secure memory or encryption card device.
8. The system for implementing multi-application authorization passwords based on trusted device hierarchy as described in claim 1, characterized in that: The encrypted trusted device hierarchy authorization password storage format is set to 32 bytes of program hash value plus 16 bytes of SM4 encrypted authorization password ciphertext.