https://sourceforge.net/p/q3rain/wiki/AuthAndRegForDevelopers/Recent changes to AuthAndRegForDevelopersenMon, 18 Nov 2013 22:43:31 -0000https://sourceforge.net/p/q3rain/wiki/AuthAndRegForDevelopers/<div class="markdown_content"><h1 id="authorization">Authorization</h1> <p>Client will send a OOB message to the master server. </p> <p><code>auth &lt;nickname&gt; &lt;password&gt;</code></p> <p>Master's responses: </p> <p><code>authSuccess</code></p> <p><code>authFail</code></p> <h1 id="registration">Registration</h1> <p>Only via webinterface </p> <h1 id="nick-registration">Nick Registration</h1> <p>Only via webinterface </p> <h1 id="nick-dropping">Nick dropping</h1> <p>Only via webinterface </p> <h1 id="account-dropping">Account dropping</h1> <p>Only via webinterface </p> <h1 id="guid-logic-tbd">Guid Logic (TBD!)</h1> <p>On startup, client sends its nickname and md5-hashed guid to the masterserver, which checks if they fit. This way we don't need to save password. The guid must be first saved in the webinterface, where a new one can also be retrieved from. When connecting to a server, the client sends its md5-hashed guid to the server, which then checks the data with the master server again. Random checks while ingame are probably a good idea too. If two different accounts use the same guid, they are both disabled until the issue is resolved by a Hazewood admin. Invalid guids will resolve in failed logins, which will also disable a few cheats. Changing guid while playing will result in an 24 hour global ban and an admin notice. </p></div>AnonymousMon, 18 Nov 2013 22:43:31 -0000https://sourceforge.net63d417adc836220cba3407fbf4a7bfbf0fc67f0e