A cross-platform certificate mutual trust and synchronization method
By constructing a certificate chain path graph and a local candidate path set, the problems of certificate chain path forks and the residual effects of cross-signatures in cross-platform certificate mutual trust are solved, enabling more accurate judgment of cross-platform certificate mutual trust status and risk management.
Patent Information
- Application Number
- CN202611224051.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-13
- Publication Date
- 2026-11-10
- Estimated Expiration
- 2046-08-13
AI Technical Summary
In cross-platform mutual trust scenarios, existing technologies struggle to accurately identify and handle forks in the certificate chain path, residual effects of cross-signatures, and collisions of untrusted paths, leading to inaccurate judgments on cross-platform certificate mutual trust and insufficient risk management.
By generating a certificate chain path evidence body, and combining it with a local trust anchor library, certificate chain cache, cross-signature relationship library and path governance ledger, a certificate chain path graph is constructed, a local candidate path set is extracted, and based on the certificate chain path evidence body and the local candidate path set, a synchronization fingerprint matching path, certificate chain path fork degree, cross-signature residual age, etc. are generated to determine the mutual trust status of the certificates of the nodes to be synchronized.
It improves the accuracy and traceability of cross-platform certificate trust judgment, enhances the refinement of cross-platform certificate trust management and risk handling capabilities, and avoids misjudgments caused by single certificate verification results.
Smart Images

Figure CN122741074B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of digital certificate trust management technology, and more specifically, to a cross-platform certificate mutual trust synchronization method. Background Technology
[0002] With the widespread application of multi-platform business collaboration, cross-domain node access, edge computing node interconnection, and multi-level certificate systems, digital certificates have become a crucial basis for identity verification and trust transfer between different platforms. In existing certificate trust management processes, platforms typically assess the trustworthiness of access node certificates based on local trust anchors, certificate chain verification results, certificate validity, certificate revocation status, and certificate signature relationships. For relatively stable single-trust-domain scenarios, this approach can effectively verify the authenticity, integrity, and validity of certificates.
[0003] In cross-platform trust scenarios, different platforms often maintain their own independently maintained trust anchor libraries, certificate chain caches, cross-signature relationship records, and certificate governance records. A trusted certificate chain path formed by the same node certificate to be synchronized on one platform may correspond to different local candidate certificate chain paths when entering another platform due to differences in local trust anchor configurations, certificate chain caches, cross-signature relationships, or historical governance records. In other words, cross-platform trust determination involves not only the validity of the node certificate itself, but also the certificate chain path along which the node certificate forms a trusted basis, and whether that certificate chain path remains stable, clear, and unisolated within the target platform's local trust environment.
[0004] Existing inter-platform certificate synchronization methods typically focus more on the transmission of certificate content, certificate chain files, or basic verification results, while neglecting the evidentiary description of the certificate chain path itself, path fingerprint matching, local candidate path forks, the impact of cross-signature residues, and collisions of untrusted paths. When cross-signed certificates still remain in the local certificate chain cache, or when a trust anchor has exited but the related paths have not yet fully converged, the target platform may simultaneously identify multiple candidate paths that can reach different local trust anchors. If a trustworthy or untrustworthy judgment is made based solely on a single certificate verification result, it is difficult to distinguish between slight differences in paths, risks of restricted mutual trust, and situations where mutual trust should be suspended.
[0005] Furthermore, in an environment where certificate governance is becoming increasingly refined, some certificate chain paths may no longer be suitable as a basis for normal cross-platform mutual trust due to reasons such as revocation, downgrade, breach of trust, expiration of governance confirmation period, or expiration of certificate validity. If the target platform cannot correlate and compare the certificate chain path evidence provided by the sending platform with its own local trust resources, it will be difficult to identify in a timely manner whether the synchronous fingerprint matching path falls into the residual isolated path, and it will also be difficult to determine whether there are still acceptable candidate paths available in the local candidate path set.
[0006] Therefore, this application proposes a cross-platform certificate mutual trust and synchronization method. Summary of the Invention
[0007] To address the shortcomings of existing technologies, the purpose of this invention is to provide a cross-platform certificate mutual trust and synchronization method.
[0008] To achieve the above objectives, the present invention provides the following technical solution:
[0009] A cross-platform certificate mutual trust and synchronization method includes:
[0010] Step 1: Generate a certificate chain path evidence body for the certificate of the node to be synchronized, encapsulate the certificate chain path evidence body into a certificate mutual trust synchronization message, and send the certificate mutual trust synchronization message to the target platform;
[0011] The certificate chain path evidence body includes the certificate basic fields, path description fields, and path fingerprint fields; the certificate mutual trust synchronization message includes the certificate chain path evidence body, sending platform identifier, synchronization sequence number, message generation time, and platform signature value.
[0012] Step 2: Receive certificate mutual trust synchronization messages, verify the source credibility and synchronization legality of the certificate mutual trust synchronization messages, extract the certificate chain path evidence body after the verification is passed, and construct the certificate chain path graph corresponding to the certificate of the node to be synchronized based on the local trust anchor library, local certificate chain cache, local cross-signature relationship library, local path governance ledger and local untrusted path library, and extract the local candidate path set from the certificate chain path graph.
[0013] Step 3: Based on the certificate chain path evidence body and the local candidate path set, generate the synchronous fingerprint matching path, certificate chain path fork degree, cross-signature residual age, residual isolation path set, and candidate available path set;
[0014] Step 4: Based on the certificate chain path fork degree, cross-signature residual age, residual isolation path set, candidate available path set, and synchronization fingerprint matching path, determine the mutual trust status adjustment result of the certificate to be synchronized, and accordingly set the cross-platform mutual trust status of the certificate to be synchronized to a trusted state, a restricted mutual trust state, or a suspended state.
[0015] In one embodiment, the certificate base fields include the certificate of the node to be synchronized, the certificate digest of the node to be synchronized, the certificate validity period, and the issuer identifier; the path description field includes a path element sequence and a trust anchor identifier, the path element sequence includes path node digests arranged in the order of the certificate chain path, and the path node digest includes a certificate digest, an issuer public key digest, and a certificate policy constraint digest; the path fingerprint field includes a certificate chain path fingerprint, which is a path-level evidence identifier that forms the basis for cross-platform mutual trust along a specific certificate chain path of the certificate of the node to be synchronized.
[0016] In one embodiment, the certificate chain path graph uses the certificate digest, the issuer's public key digest, and the local trust anchor identifier in the local trust anchor library as path nodes, and the certificate issuance relationship, cross-signature relationship, and trust anchor anchoring relationship as directed path edges.
[0017] The local candidate path set consists of local candidate certificate chain paths extracted from the certificate chain path graph. Each local candidate certificate chain path has a local path element sequence, a local trust anchor identifier, and a local certificate chain path fingerprint.
[0018] In one embodiment, in step three: the certificate chain path fork degree is generated based on the basic path fork degree, the cross-signature residual age, and the isolation convergence impact coefficient; the basic path fork degree is generated by the local path difference tuple; the basic path fork degree increases as the values of each item in the local path difference tuple increase; the local path difference tuple is generated based on the local candidate certificate chain path.
[0019] In one embodiment, the local path difference tuple includes path topology discrete value, trust anchor offset value, path fingerprint offset value, issuer public key divergence value, certificate policy constraint offset value, and untrusted path collision value.
[0020] In one embodiment, the local path difference tuple contains: the issuer public key divergence value is generated based on the difference in issuer public key digests between the local path element sequence and the path element sequence; the certificate policy constraint offset value is generated based on the difference in certificate policy constraint digests between the local path element sequence and the path element sequence; and the default path collision value is generated based on the hit relationship between the local certificate chain path fingerprint and the default certificate chain path fingerprint recorded in the local default path database.
[0021] In one embodiment, the residual isolated path set and the candidate available path set are determined as follows: the local candidate certificate chain path containing the certificate corresponding to the cross-signature relationship in the local cross-signature relationship library is determined as the cross-signature certificate chain path;
[0022] Based on the cross-signature residual age and the local path difference tuple, the set of residual isolated paths is determined from the cross-signature certificate chain path, and the set of residual isolated paths is excluded from the local candidate path set to obtain the candidate available path set.
[0023] In one embodiment, determining the cross-signature residual age includes: generating a cross-signature residual event set for the cross-signature certificate chain path, generating the cross-signature path residual age corresponding to each cross-signature certificate chain path based on the cross-signature residual event set, and determining the cross-signature residual age corresponding to the certificate of the node to be synchronized based on the residual age of each cross-signature path.
[0024] In one embodiment, the cross-signature residual event set includes at least one of the following: certificate revocation event, certificate breach of trust event, certificate downgrade event, trust anchor exit event, governance confirmation period expiration event, and certificate validity period expiration event.
[0025] In one embodiment, the isolation convergence impact coefficient is generated as follows:
[0026] After determining the cross-signature residual age based on the cross-signature residual event set, and determining the residual isolation path set based on the cross-signature residual age and the local path difference tuple, the isolation convergence impact coefficient is generated according to the path ratio of the residual isolation path set relative to the local candidate path set, whether the synchronous fingerprint matching path belongs to the residual isolation path set, and whether the candidate available path set is empty.
[0027] Compared with the prior art, the present invention has the following beneficial effects:
[0028] This invention extracts certificate chain path evidence from the target platform after successful verification and constructs a certificate chain path graph by combining it with a local trust anchor library, a local certificate chain cache, a local cross-signature relationship library, a local path governance ledger, and a local untrusted path library. This allows for the reconstruction of the possible certificate chain path relationships corresponding to the certificates of the nodes to be synchronized within the target platform's local trust environment. By extracting a local candidate path set from the certificate chain path graph, the target platform can perform path-level comparisons between the path evidence provided by the sending platform and the local candidate paths. This facilitates the identification of synchronization fingerprint matching paths, certificate chain path forks, the residual impact of cross-signatures, and untrusted path associations, improving the accuracy and traceability of cross-platform certificate mutual trust judgment.
[0029] By generating synchronization fingerprint matching paths, certificate chain path forks, cross-signature residual ages, residual isolation path sets, and candidate available path sets based on certificate chain path evidence bodies and local candidate path sets, and determining the mutual trust status adjustment results of the certificates to be synchronized, the target platform can classify the cross-platform mutual trust status of the certificates to be synchronized according to the degree of path matching, path fork degree, cross-signature residual degree, and available path status. Compared with the method of making a single judgment based on certificate validity, this invention can accurately place the certificates to be synchronized into a trusted state, a restricted mutual trust state, or a suspended state, enhancing the refinement of cross-platform certificate mutual trust management and risk handling capabilities. Attached Figure Description
[0030] Figure 1 This is a schematic diagram of the overall process of a cross-platform certificate mutual trust and synchronization method according to the present invention;
[0031] Figure 2 This is a flowchart illustrating the process by which the target platform verifies the source credibility and synchronization legitimacy of certificate mutual trust synchronization messages and extracts the certificate chain path evidence.
[0032] Figure 3 This diagram illustrates the construction of a certificate chain path graph and the extraction of a local candidate path set based on a local trust anchor library, a local certificate chain cache, a local cross-signature relationship library, a local path governance ledger, and a local untrusted path library.
[0033] Figure 4 This is a schematic diagram showing the relationship between path nodes and directed path edges in the local candidate certificate chain path. Detailed Implementation
[0034] Reference Figures 1 to 4 A cross-platform certificate mutual trust and synchronization method includes:
[0035] Step 1: Generate a certificate chain path evidence body for the certificate of the node to be synchronized, encapsulate the certificate chain path evidence body into a certificate mutual trust synchronization message, and send the certificate mutual trust synchronization message to the target platform. The certificate chain path evidence body includes the basic certificate fields, path description fields, and path fingerprint fields. The certificate mutual trust synchronization message includes the certificate chain path evidence body, the sending platform identifier, the synchronization sequence number, the message generation time, and the platform signature value. The certificate chain path information that forms the basis of mutual trust between the certificate of the node to be synchronized and the sending platform is organized into the certificate chain path evidence body, rather than simply transmitting the certificate of the node to be synchronized itself.
[0036] The certificate basic field records the basic identity information of the certificate to be synchronized, the path description field records the composition of the certificate chain path of the certificate to be synchronized, and the path fingerprint field records the path-level evidence identifier corresponding to the certificate chain path. By encapsulating the certificate chain path evidence body into a certificate mutual trust synchronization message, and configuring the sending platform identifier, synchronization sequence number, message generation time, and platform signature value in the certificate mutual trust synchronization message, the target platform receives not only the certificate content, but also the certificate chain path source, synchronization batch, generation time, and platform confirmation information. This process facilitates the target platform to fully verify the certificate mutual trust evidence transmitted across platforms, reducing problems such as missing path evidence, difficulty in confirming the source, or difficulty in distinguishing duplicate synchronizations caused by synchronizing individual certificates.
[0037] The sending platform extracts basic certificate fields from the certificate of the node to be synchronized. The basic certificate fields include the certificate of the node to be synchronized, the certificate digest of the node to be synchronized, the certificate validity period, and the issuer identifier. The certificate digest of the node to be synchronized is calculated according to a preset digest algorithm to obtain the complete encoded content of the certificate of the node to be synchronized. The certificate validity period is taken from the start and end time recorded in the certificate of the node to be synchronized. The issuer identifier is taken from the identity content corresponding to the issuing entity in the certificate of the node to be synchronized.
[0038] The certificate digest, issuer public key digest, and certificate policy constraint digest are generated using the same digest algorithm. The certificate corresponding to each path node is denoted as . , of The encoding is denoted as The issuer's public key information is recorded as The set of extended terms included in the path constraint judgment is denoted as The digest algorithm is denoted as The certificate digest satisfies:
[0039]
[0040] The issuer's public key digest satisfies:
[0041]
[0042] Certificate policy constraint digest satisfies:
[0043]
[0044] in, , This represents the total number of path nodes. For the normalization coding function of certificate policy constraint extension items, This includes certificate policy identifier, basic constraints, path length constraints, key usage, extended key usage, name constraints, and policy constraints; if the corresponding extended item does not exist, the field value is recorded as... Still participating coding; Pick Or a collision-resistant summary algorithm for the target platform path evaluation strategy record.
[0045] For example, when the certificate to be synchronized is an edge access node certificate, the sending platform records the certificate body, the certificate digest, the certificate validity period, and the certificate issuer identifier of the edge access node certificate, and traces upwards along the edge access node certificate to the corresponding trust anchor to form a certificate chain path;
[0046] The sending platform generates a path description field and a path fingerprint field based on the certificate chain path. The path description field includes a path element sequence and a trust anchor identifier. The path element sequence arranges the path node digests according to the certificate chain path order. Each path node digest includes a certificate digest, an issuer public key digest, and a certificate policy constraint digest. The path fingerprint field includes a certificate chain path fingerprint. The certificate chain path fingerprint is a path-level evidence identifier that forms the basis for cross-platform mutual trust along a specific certificate chain path of the certificate to be synchronized node.
[0047] Trust anchor identifier is denoted as When a trust anchor is stored in the form of a certificate, the trust anchor certificate... Encode and calculate digest, obtain When the trust anchor is stored in the form of the principal's public key, a digest is calculated from the principal's public key information to obtain... The platform's internal registration number is stored as an additional record and does not replace the trust anchor identifier. The standardized encoding of the certificate chain path fingerprint is denoted as... The certificate digest of the node to be synchronized is denoted as , No. The path node codes are denoted as The path edge type is denoted as The length prefix encoding function is denoted as Byte string concatenation symbol is denoted as The path node encoding satisfies:
[0048]
[0049] The certificate chain path normalization encoding satisfies:
[0050]
[0051] The certificate chain path fingerprint satisfies:
[0052]
[0053] in, For certificate chain path fingerprint; hour, For the first The path node to the first The type of directed path edge between path nodes; hour, For the first The trust anchoring relationship between each path node and the trust anchor identifier; Choose one of the following: certificate issuance relationship, cross-signature relationship, or trust anchoring relationship.
[0054] For example, the path element sequence sequentially records the edge access node certificate digest, intermediate certificate digest, and root certificate digest, and also records the issuer public key digest and certificate policy constraint digest of each path node. The trust anchor identifier records the local trust anchor identifier corresponding to the root certificate. The sending platform normalizes and calculates the digests of the path element sequence, trust anchor identifier, and certificate digests of the nodes to be synchronized, forming a certificate chain path fingerprint. Then, the certificate basic fields, path description fields, and path fingerprint fields are combined into a certificate chain path evidence body. The certificate chain path evidence body, together with the sending platform identifier, synchronization sequence number, message generation time, and platform signature value, is encapsulated into a certificate mutual trust synchronization message, which is sent by the sending platform to the target platform.
[0055] Step two involves receiving certificate mutual trust synchronization messages, verifying the source credibility and synchronization legitimacy of these messages, extracting the certificate chain path evidence body after successful verification, and constructing a certificate chain path graph corresponding to the certificates of the nodes to be synchronized based on the local trust anchor library, local certificate chain cache, local cross-signature relationship library, local path governance ledger, and local untrusted path library. A local candidate path set is then extracted from the certificate chain path graph. The target platform does not directly accept the received certificate mutual trust synchronization messages but instead verifies their source credibility and synchronization legitimacy.
[0056] Source trustworthiness verification focuses on whether the certificate mutual trust synchronization message was indeed generated by a trusted sending platform. Synchronization legitimacy verification focuses on whether the synchronization sequence, message generation time, platform signature value, and other content meet the target platform's synchronization management requirements. After successful verification, the target platform extracts the certificate chain path evidence body and, in conjunction with the local trust anchor library, local certificate chain cache, local cross-signature relationship library, local path governance ledger, and local untrusted path library, constructs a certificate chain path graph corresponding to the certificate of the node to be synchronized. This certificate chain path graph reflects the possible certificate chain path relationships associated with the certificate of the node to be synchronized from the target platform's local perspective. The local candidate path set is extracted from the certificate chain path graph and serves as the path basis for the target platform to perform local comparison, fork judgment, and remnant identification of external certificate chain path evidence bodies.
[0057] After receiving the certificate mutual trust synchronization message from the sending platform, the target platform performs source trust verification and synchronization legality verification on the certificate mutual trust synchronization message. Source trust verification includes querying the pre-set platform trust record based on the sending platform identifier, and verifying the platform signature value using the platform public key corresponding to the sending platform identifier, and checking whether the content of the certificate mutual trust synchronization message has changed during transmission. Synchronization legality verification includes verifying whether the synchronization sequence number falls within the synchronization range allowed by the target platform, whether the message generation time meets the time window requirements, and whether there are duplicate or out-of-order submissions of the same certificate to be synchronized node. After the verification is passed, the certificate chain path evidence body is extracted to obtain the certificate basic field, path description field, and path fingerprint field.
[0058] The certificate chain path evidence body is denoted as The sending platform identifier is recorded as The synchronization sequence number is denoted as The message generation time is recorded as The target platform's receiving time is recorded as Send platform identifier The corresponding platform public key is denoted as The platform signature value is recorded as The signature verification function is denoted as The message signature input is recorded as The platform signature value covers the certificate chain path evidence body, the sending platform identifier, the synchronization sequence number, and the message generation time.
[0059]
[0060] Source credibility verification satisfies:
[0061]
[0062] Synchronization validity verification: The synchronization sequence number is greater than the target platform's. The most recently received synchronization sequence number is recorded, and the deviation between the message generation time and the target platform's reception time does not exceed [a certain value]. And the duplicate submission flag does not exist. The duplicate submission flag satisfies:
[0063]
[0064] If there is no recently received synchronization sequence number record, the sequence number is treated as 0; Allow for deviation in message generation time; 30 minutes is used when not configured. A collection of duplicate submission records stored for the target platform. After successful synchronization validity verification and acceptance of the certificate trust synchronization message, the target platform updates... The corresponding most recently accepted synchronization sequence number will be... Write .
[0065] For example, when the target platform receives a certificate mutual trust synchronization message corresponding to the edge access node certificate, if the platform signature value is successfully verified, the synchronization sequence number is not used, and the message generation time does not exceed the receiving range set by the target platform, then the certificate digest, path element sequence, trust anchor identifier, and certificate chain path fingerprint of the node to be synchronized are read as input content for constructing the certificate chain path graph.
[0066] The target platform constructs a certificate chain path graph corresponding to the certificates of the nodes to be synchronized, based on a local trust anchor library, a local certificate chain cache, a local cross-signature relationship library, a local path governance ledger, and a local untrusted path library. The certificate chain path graph uses certificate digests, issuer public key digests, and local trust anchor identifiers in the local trust anchor library as path nodes, and certificate issuance relationships, cross-signature relationships, and trust anchor anchoring relationships as directed path edges. Among them, the local certificate chain cache provides the certificate issuance relationship between the certificate of the node to be synchronized and its superior certificate; the local cross-signature relationship library provides the cross-signature relationship formed between different trust anchors with the same public key or the same issuer; the local path governance ledger provides path records that have been confirmed, downgraded, or withdrawn through governance; and the local untrusted path library provides fingerprints of untrusted certificate chain paths that should not be included in the normal mutual trust judgment.
[0067] Records in the local cross-signature relationship database must include at least the cross-signature relationship identifier, associated certificate digest, subject public key digest, associated trust anchor identifier, and relationship status. Records in the local path governance ledger must include at least the governance event type, event occurrence time, associated certificate digest, associated trust anchor identifier, associated certificate chain path fingerprint, and governance status. Records in the local default path database must include at least the default certificate chain path fingerprint, default reason, recording time, and default status. The certificate chain path diagram is notated as follows: The nodes include certificate digest nodes, issuer public key digest nodes, and local trust anchor identifier nodes; the directed path edges include certificate issuance relationship edges, cross-signature relationship edges, and trust anchor anchoring relationship edges. The direction of the certificate issuance relationship edge is that the issued certificate digest node points to the issuer public key digest node, and the issuer public key digest node points to the corresponding superior certificate digest node; the direction of the cross-signature relationship edge is determined according to the search direction from the certificate digest of the node to be synchronized to the local trust anchor identifier; the direction of the trust anchor anchoring relationship edge is that either the certificate digest node or the issuer public key digest node points to the local trust anchor identifier node.
[0068] The local candidate certificate chain path is denoted as The local candidate path set is denoted as The target platform along A cycle-free search is performed on the directed path edges, starting from the certificate digest of the node to be synchronized and ending at the local trust anchor node; The same certificate digest node must not appear repeatedly; when a local trust anchor identifier node is found, the corresponding path will be included. ; path length reaches The search for this branch will stop if the local trust anchor node is not reached. To determine the maximum path length, take the maximum certificate chain path length recorded in the target platform's path evaluation strategy. Path length constraints in the extension of basic certificate constraints The smaller of the two; not read At that time, according to Processing; Not configured hour, Take 10.
[0069] After the certificate chain path graph is formed, the target platform starts from the path node corresponding to the certificate digest of the node to be synchronized and searches along the directed path edge to the path node corresponding to the local trust anchor identifier, and extracts the local candidate path set. The local candidate path set is composed of local candidate certificate chain paths. Each local candidate certificate chain path has a local path element sequence, a local trust anchor identifier, and a local certificate chain path fingerprint.
[0070] For example, an edge access node certificate may have a certificate issuance relationship from intermediate certificate A to root certificate A and a cross-signature relationship from cross-signature certificate B to root certificate B in its local certificate chain cache. Based on this, the target platform forms two local candidate certificate chain paths and generates corresponding local path element sequences, local trust anchor identifiers, and local certificate chain path fingerprints.
[0071] Step 3: Based on the certificate chain path evidence body and the local candidate path set, generate the synchronization fingerprint matching path, certificate chain path fork degree, cross-signature residual age, residual isolation path set, and candidate available path set; compare the certificate chain path evidence body provided by the sending platform with the local candidate path set extracted by the target platform to form multiple intermediate results related to mutual trust status judgment.
[0072] The synchronous fingerprint matching path reflects the matching status between the path fingerprint field in the certificate chain path evidence body and the local candidate path set; the certificate chain path fork degree reflects the degree of difference between the target platform's local candidate paths and the paths corresponding to the certificate chain path evidence body; the cross-signature residual age reflects the residual status of cross-signature relationships in the local path environment; the residual isolated path set records paths that need to be removed from the normal mutual trust judgment criteria; and the candidate available path set retains paths that have not been excluded from the local candidate path set. Through this step, the target platform obtains the judgment materials such as path matching, path fork, cross-signature residuals, and available path range required for mutual trust state control, avoiding making mutual trust conclusions based solely on a single certificate chain path fingerprint.
[0073] The target platform performs path-level verification against each local candidate certificate chain path in the local candidate path set based on the path element sequence, trust anchor identifier, and certificate chain path fingerprint in the certificate chain path evidence body. If the local certificate chain path fingerprint of a certain local candidate certificate chain path is consistent with the certificate chain path fingerprint in the certificate chain path evidence body, then the local candidate certificate chain path is determined as the synchronization fingerprint matching path.
[0074] The local certificate chain path fingerprint and the certificate chain path fingerprint in the certificate chain path evidence body are calculated using the same normalized encoding rules and the same digest algorithm. Local candidate certificate chain path The normalized encoding is denoted as The local certificate chain path fingerprint is recorded as ,satisfy:
[0075]
[0076] Certificate chain path fingerprint in the certificate chain path evidence body Obtained under the same rules. The target platform will and Consistent candidate paths are determined as synchronous fingerprint matching paths. When multiple synchronous fingerprint matching paths exist, the path with the shortest path length is selected and denoted as... If multiple paths of the same length exist, the path with the smallest certificate digest sequence in ascending byte order is selected; if they are still the same, the path with the smallest local trust anchor identifier in ascending byte order is selected. If no synchronous fingerprint matching path exists, Record as empty.
[0077] In the absence of a completely consistent scenario, the target platform retains each local candidate certificate chain path and generates a local path difference tuple for each local candidate certificate chain path. The local path difference tuple includes path topology discrete value, trust anchor offset value, path fingerprint offset value, issuer public key divergence value, certificate policy constraint offset value, and untrusted path collision value. Among them, the path topology discrete value is generated according to the difference in node order and node addition / reduction between the local path element sequence and the path element sequence; the trust anchor offset value is generated according to whether the local trust anchor identifier is consistent with the trust anchor identifier in the certificate chain path evidence body; the path fingerprint offset value is generated according to whether the local certificate chain path fingerprint is consistent with the certificate chain path fingerprint; the issuer public key divergence value is generated according to the difference in issuer public key digest between the local path element sequence and the path element sequence; the certificate policy constraint offset value is generated according to the difference in certificate policy constraint digest between the local path element sequence and the path element sequence; and the untrusted path collision value is generated according to the hit relationship between the local certificate chain path fingerprint and the untrusted certificate chain path fingerprint recorded in the local untrusted path database.
[0078] The certificate digest sequence, issuer public key digest sequence, certificate policy constraint digest sequence, trust anchor identifier, and certificate chain path fingerprint in the certificate chain path evidence body are respectively denoted as: ;No. The corresponding contents in each local candidate certificate chain path are denoted as follows: The set of path fingerprints for the chain of untrusted certificates in the local untrusted path database is denoted as... The longest common subsequence length function is denoted as . Indicator function Under conditions When it is true, take 1; under the condition... If the condition is not met, the value is 0. The discrete values of the path topology satisfy:
[0079]
[0080] The trust anchor offset value is denoted as The path fingerprint offset value is denoted as The collision value of the untrusted path is recorded as The three are respectively arranged as follows: and Are they different? and Are they different? Did it hit? The public key divergence value is set to 1 if the condition is met, and 0 if the condition is not met. The issuer's public key divergence value satisfies:
[0081]
[0082] The certificate policy constraint offset value satisfies:
[0083]
[0084] When the denominator is 0, the corresponding difference value is 0. The basic path fork degree of the local candidate certificate chain path is denoted as . ,satisfy:
[0085]
[0086] Among them, all weight coefficients are non-negative, and When no weighting coefficients are configured, all weighting coefficients take equal values. The value range is from 0 to 1.
[0087] For example, if the path recorded in the certificate chain path evidence body of the node certificate to be synchronized is node certificate, intermediate certificate A, and root certificate A, and the target platform's local candidate path set also contains a path of node certificate, intermediate certificate B, cross-signature certificate B, and root certificate B, then the target platform calculates the values of this path in terms of path topology, trust anchor, path fingerprint, issuer public key digest, certificate policy constraint digest, and collision of untrusted paths, and increases the basic path fork degree corresponding to the increase of the values of each item in the local path difference tuple;
[0088] The target platform determines the local candidate certificate chain path containing the certificates corresponding to the cross-signature relationships in the local cross-signature relationship library as the cross-signature certificate chain path, and generates a cross-signature residual event set for the cross-signature certificate chain path. The cross-signature residual event set includes at least one of the following: certificate revocation event, certificate default event, certificate downgrade event, trust anchor exit event, governance confirmation period expiration event, and certificate validity period expiration event.
[0089] No. The set of cross-signature residual events for each cross-signature certificate chain path is denoted as... , Any event in is denoted as .event At least include event types Time of the incident Source of the incident Associated Certificate Summary Or cross-signature relationship identifier .event and When any certificate digest, trust anchor identifier, or cross-signature relationship identifier in the event has a corresponding relationship, Into The current judgment time is recorded as... The residual reference period is denoted as Not configured Time to take day. and Use the same unit of time. The residual age of the cross-signature certificate chain path is denoted as: ; When R_i is empty, R_i = 0; When not empty, satisfy:
[0090]
[0091] The cross-signature residual age corresponding to the certificate of the node to be synchronized is denoted as Take each The maximum value in; when there is no cross-signature certificate chain path, .
[0092] The target platform generates the cross-signature path residual age corresponding to each cross-signature certificate chain path based on the cross-signature residual event set, and determines the cross-signature residual age corresponding to the certificate of the node to be synchronized based on the residual age of each cross-signature path. When the cross-signature residual age reaches the residual judgment condition set by the target platform, and there are abnormal values in the path fingerprint offset value, issuer public key divergence value, certificate policy constraint offset value, or untrusted path collision value in the local path difference tuple of the corresponding local candidate certificate chain path, the cross-signature certificate chain path is included in the residual isolation path set. The target platform excludes the residual isolation path set from the local candidate path set to obtain the candidate available path set, and generates the isolation convergence impact coefficient based on the path ratio of the residual isolation path set relative to the local candidate path set, whether the synchronization fingerprint matching path belongs to the residual isolation path set, and whether the candidate available path set is empty.
[0093] Local candidate path set Paths containing cross-signature relationship edges form a cross-signature certificate chain path set, denoted as . The set of residual isolation paths is denoted as The set of candidate available paths is denoted as When no cross-signature certificate chain path exists, and All are denoted as the empty set. For The Middle Cross-signature certificate chain path The isolation decision value is recorded as .like Not less than ,or equal to 1, or Equal to 1 and Not less than ,or Not less than ,or Equal to 1 and If it includes the anchoring relationship corresponding to the exited trust anchor, then Take 1; otherwise Take 0. The cross-signature certificate chain path with a value of 1 is included. ;Target platform from Excluded ,get The synchronous fingerprint matching path isolation hit value is recorded as... , belong hour Select 1 otherwise select 0; the empty set of candidate available paths is denoted as... , When empty Set to 1 otherwise set to 0. The isolation convergence impact coefficient is denoted as... ,satisfy:
[0094]
[0095] in, , , ; These are non-negative weighting coefficients. When not configured, all three are taken The certificate chain path fork degree is denoted as... A synchronous fingerprint matching path exists. At that time, the path bifurcation baseline value Pick Corresponding basic path branching degree ; Empty and local candidate path set When not empty, Take the minimum value of the basic path bifurcation degree of each candidate path; When empty, The certificate chain path fork degree satisfies:
[0096]
[0097] in, All are non-negative numbers, and When not configured, all three are taken. . The value range is from 0 to 1.
[0098] Based on this, the target platform generates the certificate chain path fork degree by combining the basic path fork degree, the cross-signature residual age, and the isolation convergence impact coefficient. For example, although a certain cross-signature certificate chain path can reach the local trust anchor identifier, its cross-signature residual event set includes trust anchor exit events and governance confirmation period expiration events. Furthermore, the local certificate chain path fingerprint of this path matches the fingerprint of the untrusted certificate chain path recorded in the local untrusted path database. In this case, the cross-signature certificate chain path is classified into the residual isolation path set. The candidate available path set only retains local candidate certificate chain paths that have not experienced residual isolation. The certificate chain path fork degree is adjusted according to the changes in the basic path fork degree, the cross-signature residual age, and the isolation convergence impact coefficient.
[0099] Step four: Based on the certificate chain path fork degree, cross-signature residual age, residual isolated path set, candidate available path set, and synchronization fingerprint matching path, determine the mutual trust status adjustment result of the certificate to be synchronized, and accordingly set the cross-platform mutual trust status of the certificate to be synchronized to a trusted state, a restricted mutual trust state, or a suspended state. The path judgment materials formed in step three are then summarized into the cross-platform mutual trust status management process for the certificate to be synchronized.
[0100] The certificate chain path fork degree reflects the degree of path difference; the cross-signature residual age reflects the residual impact of cross-signature relationships; the residual isolated path set reflects risky paths that should be excluded; the candidate available path set reflects the range of local paths that can still be included in the judgment; and the synchronization fingerprint matching path reflects the correspondence between the path evidence of the sending platform and the local path of the target platform. Based on the above, the target platform determines the mutual trust status adjustment result of the certificates to be synchronized and sets the cross-platform mutual trust status of the certificates to be synchronized to a trusted state, a restricted mutual trust state, or a suspended state. A trusted state corresponds to a situation where the paths are relatively consistent and there is no obvious residual isolation impact; a restricted mutual trust state corresponds to a situation where the path has some fork, residual impact, or a narrowing of the available range; and a suspended state corresponds to a situation where the path risk is high, there are insufficient available paths, or the matching path is affected by residual isolation. This processing makes the cross-platform mutual trust status of the certificates to be synchronized no longer solely dependent on the existence of the certificate, but rather a hierarchical adjustment combining the certificate chain path, cross-signature residuals, and local governance results.
[0101] The target platform obtains the certificate chain path fork degree Cross-signature residual age Residual isolation path set Candidate available path set and synchronized fingerprint matching path Then, according to the trusted bifurcation threshold Pause fork threshold Confidential residual threshold and pause residual threshold Generate mutual trust state regulation results When no threshold is configured, Take 0.25, Take 0.75, Take 0.30, Set the value to 0.70. The priority for state determination is: paused state is higher than trusted state, and trusted state is higher than restricted mutual trust state.
[0102] when belong ,or Empty, or Not less than ,or Not less than ,or Existence and corresponding When equal to 1, Retrieve from pause state. When Existence, and Not belonging to ,and Not empty, and Not higher than ,and Not higher than ,and corresponding When equal to 0, Take a trusted state. It does not meet the conditions for a paused state and does not meet the conditions for a trusted state, but... When not empty, Take the restricted mutual trust state and record at least one of the following reasons for the restriction: path fork, cross-signature residue, high proportion of residual isolated paths, and incomplete matching of synchronization fingerprints. Each weight coefficient and each threshold is recorded in the target platform path evaluation strategy; when the target platform generates mutual trust status adjustment results, the version number of the path evaluation strategy used is recorded simultaneously.
[0103] For example, if the synchronization fingerprint matching path corresponding to the edge access node certificate matches the residual isolated path associated with the local untrusted path library, and the set of candidate available paths is empty, the target platform will generate a mutual trust status adjustment result in a suspended state and refuse to include the certificate of the node to be synchronized in the normal cross-platform mutual trust scope.
[0104] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. A cross-platform certificate mutual trust and synchronization method, characterized in that, include: Step 1: Generate a certificate chain path evidence body for the certificate of the node to be synchronized, encapsulate the certificate chain path evidence body into a certificate mutual trust synchronization message, and send the certificate mutual trust synchronization message to the target platform; The certificate chain path evidence body includes the certificate basic fields, path description fields, and path fingerprint fields; the certificate mutual trust synchronization message includes the certificate chain path evidence body, sending platform identifier, synchronization sequence number, message generation time, and platform signature value. Step 2: Receive certificate mutual trust synchronization messages, verify the source credibility and synchronization legality of the certificate mutual trust synchronization messages, extract the certificate chain path evidence body after the verification is passed, and construct the certificate chain path graph corresponding to the certificate of the node to be synchronized based on the local trust anchor library, local certificate chain cache, local cross-signature relationship library, local path governance ledger and local untrusted path library, and extract the local candidate path set from the certificate chain path graph. Step 3: Based on the certificate chain path evidence body and the local candidate path set, generate the synchronous fingerprint matching path, certificate chain path fork degree, cross-signature residual age, residual isolation path set, and candidate available path set; In step three: the certificate chain path fork degree is generated based on the basic path fork degree, the cross-signature residual age, and the isolation convergence impact coefficient; the basic path fork degree is generated by the local path difference tuple; the basic path fork degree increases with the increase of the values of each item in the local path difference tuple; the local path difference tuple is generated based on the local candidate certificate chain path. The local path difference tuple includes path topology discrete value, trust anchor offset value, path fingerprint offset value, issuer public key divergence value, certificate policy constraint offset value, and untrusted path collision value; In the local path difference tuple: the issuer public key divergence value is generated based on the difference in issuer public key digests between the local path element sequence and the path element sequence; the certificate policy constraint offset value is generated based on the difference in certificate policy constraint digests between the local path element sequence and the path element sequence; and the default path collision value is generated based on the hit relationship between the local certificate chain path fingerprint and the default certificate chain path fingerprint recorded in the local default path database. The residual isolation path set and the candidate available path set are determined as follows: the local candidate certificate chain path containing the certificate corresponding to the cross-signature relationship in the local cross-signature relationship library is determined as the cross-signature certificate chain path; Based on the cross-signature residual age and the local path difference tuple, the set of residual isolated paths is determined from the cross-signature certificate chain path, and the set of residual isolated paths is excluded from the local candidate path set to obtain the candidate available path set; Determining the cross-signature residual age includes: generating a cross-signature residual event set for the cross-signature certificate chain path, generating the cross-signature path residual age corresponding to each cross-signature certificate chain path based on the cross-signature residual event set, and determining the cross-signature residual age corresponding to the certificate of the node to be synchronized based on the residual age of each cross-signature path. The cross-signature residual event set includes at least one of the following: certificate revocation event, certificate breach of trust event, certificate downgrade event, trust anchor exit event, governance confirmation period expiration event, and certificate validity period expiration event; The isolation convergence impact coefficient is generated as follows: After determining the cross-signature residual age based on the cross-signature residual event set, and determining the residual isolated path set based on the cross-signature residual age and the local path difference tuple, the isolation convergence impact coefficient is generated according to the path ratio of the residual isolated path set relative to the local candidate path set, whether the synchronous fingerprint matching path belongs to the residual isolated path set, and whether the candidate available path set is empty. Step 4: Based on the certificate chain path fork degree, cross-signature residual age, residual isolation path set, candidate available path set, and synchronization fingerprint matching path, determine the mutual trust status adjustment result of the certificate to be synchronized, and accordingly set the cross-platform mutual trust status of the certificate to be synchronized to a trusted state, a restricted mutual trust state, or a suspended state.
2. The cross-platform certificate mutual trust and synchronization method according to claim 1, characterized in that, The certificate basic fields include the certificate of the node to be synchronized, the certificate digest of the node to be synchronized, the certificate validity period, and the issuer identifier; the path description fields include the path element sequence and the trust anchor identifier. The path element sequence includes the path node digests arranged in the order of the certificate chain path. The path node digests include the certificate digest, the issuer's public key digest, and the certificate policy constraint digest; the path fingerprint field includes the certificate chain path fingerprint. The certificate chain path fingerprint is a path-level evidence identifier that forms the basis for cross-platform mutual trust based on the certificate of the node to be synchronized along a specific certificate chain path.
3. The cross-platform certificate mutual trust and synchronization method according to claim 1, characterized in that, The certificate chain path graph uses the certificate digest, the issuer's public key digest, and the local trust anchor identifier in the local trust anchor library as path nodes, and the certificate issuance relationship, cross-signature relationship, and trust anchor anchoring relationship as directed path edges; The local candidate path set consists of local candidate certificate chain paths extracted from the certificate chain path graph. Each local candidate certificate chain path has a local path element sequence, a local trust anchor identifier, and a local certificate chain path fingerprint.
Citation Information
Patent Citations
Identity authentication method and device, electronic equipment and storage medium
CN117879925A
Heterogeneous terminal network authentication method and system
CN121664559A
