MantisBT - Zandronum
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001947Zandronum[All Projects] Bugpublic2014-10-06 21:562014-10-07 19:26
ReporterAlexMax 
Assigned To 
PrioritynormalSeverityminorReproducibilityalways
StatusnewResolutionopen 
PlatformOSOS Version
Product Version1.3 
Target VersionFixed in Version 
Summary0001947: authhostname is only read on bootup
DescriptionPretty much what it says on the tin - authhostname is only parsed once on server boot and never afterwards.

Is this a bug or a feature? Seems to me like switching authentication servers - at least right now - is a BAD idea due to the fact that usernames in one auth server might not line up with usernames on another. However, this fact is never revealed to server administrators, who can change the CVAR at will and might chalk up its current behavior to a bug.

Does ZDoom have a concept of a read-only CVAR? Perhaps it could be 'locked in' after startup to ensure nobody tries anything tricky?
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2014-10-06 21:56AlexMaxNew Issue
2014-10-07 00:23DuskNote Added: 0010372
2014-10-07 16:57Torr SamahoNote Added: 0010379

Notes
(0010372)
Dusk   
2014-10-07 00:23   
Perhaps the authhostname should become a command-line parameter and the CVAR replaced with a console command which prints the authhostname?
(0010379)
Torr Samaho   
2014-10-07 16:57   
When I implemented this, I thought it's fine if changing the CVAR requires a restart, but completely forgot to document this anywhere. The easiest (and a quite secure) solution would be to keep the current behavior, but print a warning to the console that the changed auth server will only be used after the server is restarted. I prefer a CVAR over a command-line parameter because it allows us to transparently set a default auth server, which we already do for the master server.