[GH-ISSUE #3043] [Feature Request] remove TLS 1.0/1.1 support

gitea-mirror commented

2026-05-05 13:33:57 -06:00

Owner

Originally created by @popolin7991 on GitHub (Aug 3, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/3043

Describe the feature request

sslscan frp server bind_port TLSv1.0/1.1 enabled
If not blocked, detect obsolete cipher suites

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 @popolin7991 on GitHub (Aug 3, 2022). Original GitHub issue: https://github.com/fatedier/frp/issues/3043 ### Describe the feature request sslscan frp server bind_port TLSv1.0/1.1 enabled If not blocked, detect obsolete cipher suites ### Describe alternatives you've considered _No response_ ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [X] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 13:33:57 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:34:00 -06:00

Author

Owner

@popolin7991 commented on GitHub (Aug 3, 2022):

frp 0.35.1

TLSv1.0 disabled
TLSv1.1 disabled
TLSv1.2 disabled
TLSv1.3 disabled

frp 0.41.0

TLSv1.0 enabled
TLSv1.1 enabled
TLSv1.2 enabled
TLSv1.3 enabled

@popolin7991 commented on GitHub (Aug 3, 2022): frp 0.35.1 - TLSv1.0 disabled - TLSv1.1 disabled - TLSv1.2 disabled - TLSv1.3 disabled frp 0.41.0 - TLSv1.0 enabled - TLSv1.1 enabled - TLSv1.2 enabled - TLSv1.3 enabled

gitea-mirror commented

2026-05-05 13:34:01 -06:00

Author

Owner

@Becods commented on GitHub (Aug 3, 2022):

Why do you propose to do this?

What is the motivation for doing it?

What will happen when the proposal is implemented?

@Becods commented on GitHub (Aug 3, 2022): Why do you propose to do this? What is the motivation for doing it? What will happen when the proposal is implemented?

gitea-mirror commented

2026-05-05 13:34:02 -06:00

Author

Owner

@popolin7991 commented on GitHub (Aug 4, 2022):

@Becods 資安漏洞？！
TLS 1.0/1.1 已被棄用，只是想問問該怎麼關閉

@popolin7991 commented on GitHub (Aug 4, 2022): @Becods 資安漏洞？！ TLS 1.0/1.1 已被棄用，只是想問問該怎麼關閉

gitea-mirror commented

2026-05-05 13:34:03 -06:00

Author

Owner

@Anduin2017 commented on GitHub (Aug 4, 2022):

Directly expose 443 port as pure TCP. Secure that in the original web server.

Here is my configuration:

Sample frps.ini:

[common]
bind_port = 7000
token = your_strong_password

Sample frpc.ini:

[common]
server_addr = my-frp.com
server_port = 7000
token = your_strong_password

[HTTP]
type = tcp
local_ip = 127.0.0.1
local_port = 80
remote_port = 80

[HTTPS]
type = tcp
local_ip = 127.0.0.1
local_port = 443
remote_port = 443

And install a modern web server locally, listening to local 80 and 443.

You can follow the steps via the document from the web server you installed. Disable obsolete protocols and you can pass that.

@Anduin2017 commented on GitHub (Aug 4, 2022): Directly expose 443 port as pure TCP. Secure that in the original web server. Here is my configuration: --------------------- Sample frps.ini: ```ini [common] bind_port = 7000 token = your_strong_password ``` Sample frpc.ini: ```ini [common] server_addr = my-frp.com server_port = 7000 token = your_strong_password [HTTP] type = tcp local_ip = 127.0.0.1 local_port = 80 remote_port = 80 [HTTPS] type = tcp local_ip = 127.0.0.1 local_port = 443 remote_port = 443 ``` And install a modern web server locally, listening to local 80 and 443. You can follow the steps via the document from the web server you installed. Disable obsolete protocols and you can pass that. ![image](https://user-images.githubusercontent.com/19531547/182775137-452170e1-27cd-46a7-8ccd-b776f4be69f9.png) ![image](https://user-images.githubusercontent.com/19531547/182775166-5c750414-afee-440c-aadc-8ded954ead5d.png)

gitea-mirror commented

2026-05-05 13:34:03 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 4, 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 (Sep 4, 2022): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.