[GH-ISSUE #3189] [Feature Request] 开启 tls_enable 时支持远程证书 #2562

Closed
opened 2026-05-05 13:38:52 -06:00 by gitea-mirror · 4 comments
Owner

Originally created by @liuweiGL on GitHub (Nov 28, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/3189

Describe the feature request

现在开启 tls_enable 之后每个端都要复制一份证书文件有点麻烦,希望能添加一个配置项比如 tls_remote_repo 用于从远程仓库自动下载更新 tls_cert_file tls_key_file tls_trusted_ca_file 所需要的证书文件

Describe alternatives you've considered

No response

Affected area

  • Docs
  • Installation
  • Performance and Scalability
  • Security
  • User Experience
  • Test and Release
  • Developer Infrastructure
  • Client Plugin
  • Server Plugin
  • Extensions
  • Others
Originally created by @liuweiGL on GitHub (Nov 28, 2022). Original GitHub issue: https://github.com/fatedier/frp/issues/3189 ### Describe the feature request 现在开启 `tls_enable` 之后每个端都要复制一份证书文件有点麻烦,希望能添加一个配置项比如 `tls_remote_repo` 用于从远程仓库自动下载更新 `tls_cert_file` `tls_key_file` `tls_trusted_ca_file` 所需要的证书文件 ### Describe alternatives you've considered _No response_ ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [X] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others
gitea-mirror 2026-05-05 13:38:52 -06:00
Author
Owner

@fatedier commented on GitHub (Nov 28, 2022):

那如何信任远端获取的证书?

<!-- gh-comment-id:1328444020 --> @fatedier commented on GitHub (Nov 28, 2022): 那如何信任远端获取的证书?
Author
Owner

@liuweiGL commented on GitHub (Nov 28, 2022):

这个是用户自己配置的应该没问题吧,只不过是把本地文件放在远程仓库里面统一维护而已

<!-- gh-comment-id:1328457352 --> @liuweiGL commented on GitHub (Nov 28, 2022): 这个是用户自己配置的应该没问题吧,只不过是把本地文件放在远程仓库里面统一维护而已
Author
Owner

@xqzr commented on GitHub (Nov 30, 2022):

那如何信任远端获取的证书?

系统内置 CA

<!-- gh-comment-id:1332549367 --> @xqzr commented on GitHub (Nov 30, 2022): > 那如何信任远端获取的证书? 系统内置 CA
Author
Owner

@github-actions[bot] commented on GitHub (Dec 31, 2022):

Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

<!-- gh-comment-id:1368134769 --> @github-actions[bot] commented on GitHub (Dec 31, 2022): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/frp#2562
No description provided.