Release v1.8.4 RPM#175
Merged
Merged
Conversation
Signed-off-by: Jiale Zhang <xinjian.zjl@alibaba-inc.com>
Collaborator
|
@jialez0 ，您好，您的请求已接收，请耐心等待结果。 |
Collaborator
|
@jialez0 ，您好，未检测到有镜像需要构建，如需重新检测请评论 /start 。 |
The unique index on `instance_id` (VARCHAR(255), utf8mb4) overflowed MySQL InnoDB's 767-byte key length limit (255 * 4 = 1020 bytes), causing `CREATE UNIQUE INDEX ... ON aa_instance_heartbeats(instance_id)` to fail with "Specified key was too long" during gateway startup and aborting the migration. Switch the MySQL DDL to a 191-char prefix index, which keeps the index key under 767 bytes (191 * 4 = 764) while remaining longer than any realistic instance_id value. SQLite path is unaffected. Signed-off-by: Jiale Zhang <xinjian.zjl@alibaba-inc.com>
Collaborator
|
@jialez0 ，您好，您的请求已接收，请耐心等待结果。 |
Collaborator
|
@jialez0 ，您好，未检测到有镜像需要构建，如需重新检测请评论 /start 。 |
The previous verify path built an SM2 PKey and ran the signature through OpenSSL's EVP_DigestVerify (effectively `Verifier::new(SM3, pkey)`). That path either applies the GB/T 32918 ZA pre-processing (SM3(ENTL || ID || a || b || xG || yG || xA || yA) prepended to the message) or, on a plain EC PKey, silently dispatches to ECDSA verify. Neither matches what TPM2 produces: per the TPM 2.0 spec the SM2 quote signs SM3(attestBody) directly, with no ZA mixing and no DER wrapping. End-to-end attestation against a real Hygon TPM therefore failed with "Verify Hygon TPM quote signature failed" even when the AK, evidence body, and signature were all correct. Drop the OpenSSL high-level verifier and implement the SM2 verify equation from GB/T 32918.2-2016 §7.1 directly using BigNum/EcPoint: e = SM3(attestBody) t = (r + s) mod n with t != 0 P = s * G + t * Q ok iff (e + P.x) mod n == r Range-check r and s against [1, n-1] up front and reject t == 0 to match the spec. Reuse the existing extracted (r, s) from the marshalled TPM signature; create_sm2_pkey is left in place because it is still used to compare AK pubkeys against the keylime registrar. Signed-off-by: Jiale Zhang <xinjian.zjl@alibaba-inc.com>
Collaborator
|
@jialez0 ，您好，您的请求已接收，请耐心等待结果。 |
Collaborator
|
@jialez0 ，您好，未检测到有镜像需要构建，如需重新检测请评论 /start 。 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.