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.

Sign up for GitHub

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

Jump to bottom

[FEATURE] Output of build date + hash in console for server ops #437

Open
xedmain opened this issue Jun 30, 2024 · 0 comments · May be fixed by #496
Open

[FEATURE] Output of build date + hash in console for server ops #437

xedmain opened this issue Jun 30, 2024 · 0 comments · May be fixed by #496
Assignees
@nullsystem
Labels
enhancement New feature or request

Comments

@xedmain
Copy link
Contributor

xedmain commented Jun 30, 2024

Description

Add an output of build date + hash in console for server ops on launching the server/map change

Proposed Solution

As a server op, I would want to see the build date + hash in the console when launching the server or when the map changes, so that I can easily find out what version I'm running, plus it will appear in the logs so that will be helpful too.

Alternatives Considered

The neo_version command, but I will need to enter that every time or include it in the autoexec, which are both options which are not as neat as just having it outputted by itself, as well it will be server-dependent, so if I checkout a log from a different server and they don't have that command in autoexec, I wouldn't know what version they're running.

Additional Context

No response
@xedmain xedmain added the enhancement New feature or request label Jun 30, 2024
@nullsystem nullsystem self-assigned this Jun 30, 2024
nullsystem added a commit to nullsystem/neo that referenced this issue Jul 7, 2024
@nullsystem
Build integrity + server print neo_version info
e266b6d 
* Server now just prints neo_version on startup
* Server and client long git hashes are now matched up on startup to
  check build integrity. If they don't, the client cannot connect unless
  they have matching git hashes.
* Server convar `neo_sv_build_integrity_check` to enable/disable this
  integrity check feature. Enabled by default.
* fixes NeotokyoRebuild#437
* fixes NeotokyoRebuild#485
@nullsystem nullsystem linked a pull request Jul 7, 2024 that will close this issue
Open
nullsystem added a commit to nullsystem/neo that referenced this issue Jul 14, 2024
@nullsystem
Build integrity + server print neo_version info
303a61a 
* Server now just prints neo_version on startup
* Server and client long git hashes are now matched up on startup to
  check build integrity. If they don't, the client cannot connect unless
  they have matching git hashes.
* Server convar `neo_sv_build_integrity_check` to enable/disable this
  integrity check feature. Enabled by default.

Debug builds integrity check bypass
* Debug builds will have their first byte final bit fliped to 1 to
  indicate it's a debug build
* This will indicate to the server that it's a debug build and if
  the server allows bypass, then it will
* Mask out final bit before comparison to allow debug build that
  matches hash without first byte final bit

* fixes NeotokyoRebuild#437
* fixes NeotokyoRebuild#485
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nullsystem nullsystem

Labels
enhancement New feature or request
Projects
Bug Bounty
Status: In Progress
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Client vs server build integrity check + server startup print neo_version info nullsystem/neo
2 participants
@nullsystem @xedmain