mirror of
https://github.com/certimate-go/certimate.git
synced 2026-04-25 20:55:52 +03:00
[PR #1048] [MERGED] bugfix #1122
Labels
No labels
announcement
backlog
bug
declined
documentation
duplicate
enhancement
good first issue
good first issue
help wanted
invalid
pull-request
question
stale
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/certimate#1122
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/certimate-go/certimate/pull/1048
Author: @Qmli04
Created: 11/20/2025
Status: ✅ Merged
Merged: 11/20/2025
Merged by: @fudiwei
Base:
main← Head:QmLi📝 Commits (2)
75a8870fix: upload the certificate to aliyun slb repeatedlyd1ed325fix: init tencent waf deployer add region param📊 Changes
2 files changed (+7 additions, -3 deletions)
View changed files
📝
internal/certdeploy/deployers/sp_tencentcloud_waf.go(+1 -0)📝
pkg/core/certmgr/providers/aliyun-slb/aliyun_slb.go(+6 -3)📄 Description
该 PR 包含以下内容变更:
阿里云 slb.DescribeServerCertificates api 返回的 Fingerprint字段 是sha1的。 但在certimate的aliyun slb upload中,是通过sha2计算出Fingerprint, 这会导致指纹匹配失败,证书重复上传。
虽然许多组织和浏览器已经弃用 sha1,但为了解决这个问题,该pr在上传证书到aliyun slb中,同时支持了sha1和sha256校验
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.