[GH-ISSUE #5138] [Feature Request] stcp 安全问题

gitea-mirror commented

2026-05-05 14:33:08 -06:00

Owner

Originally created by @re1oaded on GitHub (Jan 26, 2026).
Original GitHub issue: https://github.com/fatedier/frp/issues/5138

Describe the feature request

frpc被控端配置：

serverAddr = "1.1.1.1"
serverPort = 7000
[transport]
tls.enable = true
[[proxies]]
name = "HOME"
type = "stcp"
localIP = "127.0.0.1"
localPort = 5900
secretKey = "xxxxxx"
transport.useEncryption = true
transport.useCompression = true

在stcp模式下，是不是只有开启transport.useEncryption才会使用secretKey实现端到端加密？
如果不开启，就算在stcp模式下，frps服务端理论上是可以窥探传输数据的。
我想确保远程回家的传输数据过程中不会被任何一方窥探，特别是frps服务端。

我没有在文档看到stcp或transport.useEncryption在不同模式下的说明。
因为能力有限，所来确认一下，感谢。 @fatedier

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 @re1oaded on GitHub (Jan 26, 2026). Original GitHub issue: https://github.com/fatedier/frp/issues/5138 ### Describe the feature request frpc被控端配置： ``` serverAddr = "1.1.1.1" serverPort = 7000 [transport] tls.enable = true [[proxies]] name = "HOME" type = "stcp" localIP = "127.0.0.1" localPort = 5900 secretKey = "xxxxxx" transport.useEncryption = true transport.useCompression = true ``` 在stcp模式下，是不是只有开启`transport.useEncryption`才会使用secretKey实现端到端加密？如果不开启，就算在stcp模式下，frps服务端理论上是可以窥探传输数据的。我想确保远程回家的传输数据过程中不会被任何一方窥探，特别是frps服务端。我没有在文档看到stcp或`transport.useEncryption`在不同模式下的说明。因为能力有限，所来确认一下，感谢。 @fatedier ### 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 14:33:08 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:33:11 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 10, 2026):

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

@github-actions[bot] commented on GitHub (Feb 10, 2026): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

gitea-mirror referenced this issue

2026-05-05 14:50:43 -06:00

[PR #4018] [MERGED] use go1.22 #4892