Skip to content
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

自动获取口令/账密登录 #1186

Open
ZhangHB-321688 opened this issue Dec 4, 2024 · 2 comments
Open

自动获取口令/账密登录 #1186

ZhangHB-321688 opened this issue Dec 4, 2024 · 2 comments

Comments

@ZhangHB-321688
Copy link

现在登录太不方便了
获取的口令很快就会失效,基本每天玩的时候都要:
打开多人模式 - 点击获取口令 - 跳转浏览器 - 输入账号 - 输入密码 - 手动切回游戏 - 粘贴口令 - 连接服务器

但是如果游戏内保存账号密码登录就可以简化成:
第一次:
打开多人模式 - 输入账号和密码 - 连接服务器
以后:
打开多人模式 - 连接服务器

这样多人模式就会更容易进入,在线人数和活跃人数甚至用户数量都会变多
很爱铁壳,但是登录太难受了。改完以后甚至可能成为群友tetrio的替代品(?

@ParticleG
Copy link
Member

The main reason for not using account and password login in the game at present is that the network module of the game does not support SSL, which means that the account and password will be sent in plaintext to the server.
See discussions in #246

@SweetSea-ButImNotSweet
Copy link
Contributor

SweetSea-ButImNotSweet commented Dec 8, 2024

For now if we don't really trust about local "cookie" saving, we can try to extend the authorization code longer, like up to 24h instead of 30 minutes. So assuming someone usually play everyday they will not have to relogin again

Another attempt is using a AES-256 keys pair, one public one private. Like for logging the first time the user will get the authorization code but it is actually the certificate key pair. This key pair can be used to encrypt and decrypt requests, also if the request is modified by somehow, the server can simply return error. We should also consider HMAC, key diversity (one session use a seperate key), key invalidation (after 4/8/12/24h) (or key rotation can be used); timestamps also can be used so we can check if a request is being blocked and tampered

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants