-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
SteamIdHashSalt no longer treats empty value as 'no salt', breaking default configuration. #1
Comments
Hi @s1lentq, do you mind taking a look to this issue? In the current state, the latest release version is broken out-of-the-box, which would be undesired for users who want to try the latest Reunion and find out isn't working. |
Since the recommended I believe it is better to set the salt explicitly once, ensuring the user is aware of and controls this security feature. |
Hmm, I don't think this is the best approach, servers owners not aware of this change would not understand why Reunion isn't working in the new version without reading the configuration documentation, error message is not clear about this change, installation instructions neither (also this add a new configuration step). Perhaps a better solution would be to warn in console about SteamIdHashSalt being required when using the new auth version and falling back to AuthVersion2, but I think's is a too agressive aproach not letting Reunion start. By the way, what's the difference between AuthVersion 2 and 3? |
what do i put in SteamIdHashSalt = ? reunion is not loading |
generate any random string for 32 symbols and paste |
from where do i generate this string ? can i just set auth to 1 and play with my 47 protocol friends ? |
from any tool. https://onlinetexttools.com/generate-text-of-certain-length |
In the latest version, Reunion no longer treats an empty SteamIdHashSalt value as "no salt". Instead, it is now flagging the empty value as being too short, requiring you to provide a non-empty salt string, otherwise it will not run.
The text was updated successfully, but these errors were encountered: