[GH-ISSUE #3119] [Feature Request] frps如何获取frpc客户端登陆的账号密码 #2498

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

Originally created by @NozVine on GitHub (Oct 3, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/3119

Describe the feature request

frps服务端有相应的日志或者工具可以查看到连接过来的客户端的账号密码嘛?

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 @NozVine on GitHub (Oct 3, 2022). Original GitHub issue: https://github.com/fatedier/frp/issues/3119 ### Describe the feature request frps服务端有相应的日志或者工具可以查看到连接过来的客户端的账号密码嘛? ### 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:36:30 -06:00
Author
Owner

@Becods commented on GitHub (Oct 4, 2022):

#Authenticating the Client

frp原版默认只有token和oidc这两种验证方法

二开请到对应仓库提issue

<!-- gh-comment-id:1266444172 --> @Becods commented on GitHub (Oct 4, 2022): [#Authenticating the Client](https://github.com/fatedier/frp#authenticating-the-client) frp原版默认只有token和oidc这两种验证方法 二开请到对应仓库提issue
Author
Owner

@NozVine commented on GitHub (Oct 4, 2022):

用的就是原版的工具呀,想知道frpc客户端连上frps服务端后,比如用win的master工具远程访问frpc客户端这台电脑需要输入账号密码,那么frps服务端可以知道这个账号密码嘛?

<!-- gh-comment-id:1267454917 --> @NozVine commented on GitHub (Oct 4, 2022): 用的就是原版的工具呀,想知道frpc客户端连上frps服务端后,比如用win的master工具远程访问frpc客户端这台电脑需要输入账号密码,那么frps服务端可以知道这个账号密码嘛?
Author
Owner

@Becods commented on GitHub (Oct 5, 2022):

不能

这不属于frp的问题

<!-- gh-comment-id:1267915219 --> @Becods commented on GitHub (Oct 5, 2022): 不能 这不属于frp的问题
Author
Owner

@github-actions[bot] commented on GitHub (Nov 5, 2022):

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

<!-- gh-comment-id:1304357550 --> @github-actions[bot] commented on GitHub (Nov 5, 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#2498
No description provided.