-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Want a more efficient method of authentication #164
Comments
The ask is valid, but are you facing real performance problems? A benchmark shows in my cheap VPS, it can handle 25k authentications computing per second. We also have the caching of authentication cipher blocks. So in real world I think the current implementation is able to scale up to 100k users per VPS. |
I'm just worried about this, I haven't put it into a real project yet, I'll test it later. |
@satel-global I opened bug #166 to track the grpc error. |
Thanks |
Another concern I have is that if the attacker sends a large number of verification requests, it will immediately overload the server. Shadowsocks has the same problem. |
This issue is stale because it has been open 80 days with no activity. Remove stale label or comment or this will be closed in 9 days. |
The current authentication method inevitably has some performance problems in scenarios with a large number of users
Are you considering using other methods (such as RSA) in a future release to verify the user so that no matter how many users there are, it won't affect performance
The text was updated successfully, but these errors were encountered: