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

Client id for stat tracking #110

Open
aufau opened this issue Nov 4, 2018 · 1 comment
Open

Client id for stat tracking #110

aufau opened this issue Nov 4, 2018 · 1 comment
Assignees

Comments

@aufau
Copy link
Member

aufau commented Nov 4, 2018

Provide unique client id to servers for simple tracking systems in serverside mods.

Either port ja_guid from OpenJK that provides rudimentary safety from impersonation attempts, but the id is different on each server (changes with server ip/port). This probably could be ported to a qvm mod so it's a bit superfluous.

Or use a public-key cryptography approach where client has a single public key as its id for all servers and authenticates using matching private key. This is better (single id allows cross-server tracking), safer and can't be ported to mod easily because cryptographic libraries depend on 64bit integer variables.

This requires designing authentication protocol and embedding it into existing connection protocols.

@aufau aufau added this to the Version 1.5 milestone Nov 7, 2018
@aufau aufau self-assigned this Nov 7, 2018
@aufau aufau removed this from the Version 1.5 milestone May 6, 2019
@aufau
Copy link
Member Author

aufau commented Aug 16, 2019

Note: It seems ja_guid OpenJK implementation isn't safe after all. Secret key or equivalent can be probably extracted.

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

No branches or pull requests

1 participant