[GH-ISSUE #3238] [Feature Request] FRP 隧道 默认的数据加密方式

gitea-mirror commented

2026-05-05 13:40:37 -06:00

Owner

Copy link

Originally created by @sshuangliu on GitHub (Jan 5, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3238

Describe the feature request

当FRPS--FRPC 建立隧道时，如果上面承载的是一些明文流量，例如http或者某些tcp.udp流量，隧道本身是否有默认的加密方式？
多谢

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 @sshuangliu on GitHub (Jan 5, 2023). Original GitHub issue: https://github.com/fatedier/frp/issues/3238 ### Describe the feature request 当FRPS--FRPC 建立隧道时，如果上面承载的是一些明文流量，例如http或者某些tcp.udp流量，隧道本身是否有默认的加密方式？多谢 ### 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:40:37 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:40:41 -06:00

Author

Owner

Copy link

@Becods commented on GitHub (Jan 5, 2023):

#Encryption and Compression

@Becods commented on GitHub (Jan 5, 2023): [#Encryption and Compression](https://github.com/fatedier/frp#encryption-and-compression)

gitea-mirror commented

2026-05-05 13:40:42 -06:00

Author

Owner

Copy link

@superzjg commented on GitHub (Jan 6, 2023):

关于加密的中文版说明：
单个代理加密：https://gofrp.org/docs/features/common/network/network/
全局TLS加密：https://gofrp.org/docs/features/common/network/network-tls/

@superzjg commented on GitHub (Jan 6, 2023): 关于加密的中文版说明：单个代理加密：https://gofrp.org/docs/features/common/network/network/ 全局TLS加密：https://gofrp.org/docs/features/common/network/network-tls/

gitea-mirror commented

2026-05-05 13:40:42 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Feb 6, 2023):

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 (Feb 6, 2023): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

No Branch/Tag specified