[GH-ISSUE #3005] enforce specific TLS Version

gitea-mirror commented

2026-05-05 13:32:47 -06:00

Owner

Copy link

Originally created by @felix530-h on GitHub (Jul 6, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/3005

Describe the feature request

Is it possible to enforce a specific TLS Version - for example only tls 1.3?
I tried it with "my-openssl.cnf". But this file is ignored.

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 @felix530-h on GitHub (Jul 6, 2022). Original GitHub issue: https://github.com/fatedier/frp/issues/3005 ### Describe the feature request Is it possible to enforce a specific TLS Version - for example only tls 1.3? I tried it with "my-openssl.cnf". But this file is ignored. ### 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

gitea-mirror

2026-05-05 13:32:47 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:32:50 -06:00

Author

Owner

Copy link

@fatedier commented on GitHub (Jul 6, 2022):

For proxy https or connections between frpc and frps?

@fatedier commented on GitHub (Jul 6, 2022): For proxy `https` or connections between frpc and frps?

gitea-mirror commented

2026-05-05 13:32:51 -06:00

Author

Owner

Copy link

@felix530-h commented on GitHub (Jul 6, 2022):

for a proxy https

@felix530-h commented on GitHub (Jul 6, 2022): for a proxy https

gitea-mirror commented

2026-05-05 13:32:52 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Aug 6, 2022):

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

@github-actions[bot] commented on GitHub (Aug 6, 2022): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

No Branch/Tag specified