mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 16:15:49 -06:00
[GH-ISSUE #1815] Login verification bugs when using fp-multiuser #1432
Labels
No labels
In Progress
WIP
WaitingForInfo
bug
doc
duplicate
easy
enhancement
future
help wanted
invalid
lifecycle/stale
need-issue-template
need-usage-help
no plan
proposal
pull-request
question
todo
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/frp#1432
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Erik-37 on GitHub (May 20, 2020).
Original GitHub issue: https://github.com/fatedier/frp/issues/1815
What version of frp are you using (./frpc -v or ./frps -v)?
0.32.1
What operating system and processor architecture are you using (
go env)?linux_amd64
darwin_amd64
Configures you used:
frps:
token:
frpc1
frpc2:
Steps to reproduce the issue:
Describe the results you expected:
login to server failed: invalid meta token
@brvphoenix commented on GitHub (May 20, 2020):
Modify the conditional logic in the this line and recompile it yourself.
From:
if c.tokens[content.User] == token {to:
if (len(content.User) > 0 && len(token) > 0) && c.tokens[content.User] == token {This modification will make it reject clients without the keywords "user" and "meta_token", and you can also test the self-compiled binaries of linux-amd64.
fp-multiuser-linux-amd64.zip
@Erik-37 commented on GitHub (May 20, 2020):
Great solution!!! thanks
@fatedier commented on GitHub (May 21, 2020):
@brvphoenix Can you send a PR with your modification to fp-multiuser.
@brvphoenix commented on GitHub (May 21, 2020):
@fatedier
https://github.com/gofrp/fp-multiuser/pull/2