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

Console command "status" works not properly #2095

Closed
SNMetamorph opened this issue Mar 19, 2025 · 2 comments
Closed

Console command "status" works not properly #2095

SNMetamorph opened this issue Mar 19, 2025 · 2 comments

Comments

@SNMetamorph
Copy link
Member

When joining server and typing status command, it isn't being sent to the server, instead just prints no server running.

@SNMetamorph
Copy link
Member Author

As far as I know, on GoldSrc status command prints detailed info about clients if this command was invoked from HLDS command line. But when clients uses status command on server, limited information being sent to the clients, for example clients IPs not presented in there for obvious reason. I think this command should work like it works in GoldSrc, but also I have some ideas:

  1. XashID shouldn't be exposed in command output in case when some client invoked this command. We could print some salted value, and salt should be randomly generated once on dedicated server process startup.
  2. We also could present additional non-vulnerable clients info, like their platform name or type of used input interface (keyboard, mouse, gamepad, touch, etc.)

@a1batross
Copy link
Member

a1batross commented Mar 20, 2025

Hashed XashID is already available for other clients through svc_updateuserinfo message. I decided not to put any XashID value in proposed status command yet.

Nor did I include complete useragent, as this might be somewhat sensitive information, considering how unique build number + os + arch combination might be. Maybe we can just send os-arch string, it should be less harmful.

However I added sending input devices. I think other clients deserve to know what input devices the player claims to have enabled.

While we're here, I tried to improve the original status command output, making it easier to read in my taste.

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

2 participants