Post: #9

(08-15-2014 08:59 AM)Ben Wrote:  ok this is what I was talking about... I just did not test it though.

[FUNCTION f_onaccount_connect] //Read carefully
// The f_onaccount_connect function is called before the sent password is checked.
// local.account --> username of the account connecting.
// local.password --> password given.
// RETURN
// 0 --> Let Sphere do its password checks.
// 1 --> Deny access assuming the given password is wrong.
// 6 --> Force login, without other password checks than the ones made in this function.
IF (!STRCMPI(<SERV.ACCOUNT.<local.account>.PASSWORD>,<MD5HASH <local.password>>) && !<SERV.MD5PASSWORDS>)
SERV.ACCOUNT.<local.account>.PASSWORD = <local.password>
ENDIF
RETURN 0

There is problem:
when i shut down the server to change MD5PASSWORDS to 0 then I start again sphere, sphere cuts the MD5 pass in this way:

0cc175b9c0f1b6a831c399e269772661 -> 0cc175b9c0f1b6a8

So the pass will be always wrong.