'password', // clever choice there, test 'z-män' => 'passwörd' // test for utf8 usernames and passwords ); $password = $passwords[ $user ]; if ( NULL == $password ) return NULL; // return a pair of username and password. // it is important that you return the username // exactly as it appeared in the database. // If the username lookup is case insensitive, // the rest of the script and the game servers // need to know what the correct form of the name // is. return array( $user, $password ); } // these two functions return prefix and suffix for the md5 // hash method. They are prepended/appended to the password // before md5 is applied on it. Adapt them to the way your // md5 password hash is stored in your database. // IMPORTANT: if you want to keep the %u (a good idea for // security, prevents precomputation attacks on the passwords) // user name lookup needs to be case sensitive, or there will // be unexplainable password failures. function getPrefix() { return "%u:aaauth:"; } function getSuffix() { global $authority; return ":$authority"; } // You do not need plain text passwords. The // checks on the passwords are done to a hash function // thereof. You can just as well precompute the // work of this function and store the result, // and maybe your user database already contains // the one or other hash. phpBB, for example, // stores md5( $password ). function getPasswordHash( $user, $method ) { // fetch the plaintext password $userInfo = getPassword( $user ); if ( NULL == $userInfo ) return NULL; // unpack the data $trueUser = $userInfo[0]; $password = $userInfo[1]; // check that neither prefix nor suffix conain %u if $trueUser != $user if ( $trueUser != $user && ( strpos( getPrefix(), '%u' ) !== FALSE || strpos( getPrefix(), '%u' ) !== FALSE ) ) { conclude(404, 'UNKNOWN_USER ' . $user . ' Do not use %u in pre/suffix if your user database is making case-insensitive lookups.'); } // two methods are currently supported // by server and client, bmd5 (broken md5) // and md5. Both use the md5 hash algorithm. switch( $method ) { case 'bmd5': // bmd5 quirk: the hash is computed for password + a trailing 0 $password = "$password" . chr(0); break; case "md5": // md5 adds the prefix and suffix before calculating // the hash. The example values are chosen so that the // resulting hash is the same one you find in .htdigest // files and that is used in the digest http authentication // method. If you set the prefix and suffix to empty // strings, the resulting hash will be the one found // in phpBB user databases. $password = substitutions( getPrefix(), $trueUser ) . "$password" . substitutions( getSuffix(), $trueUser ); break; } // after that, both methods just calculate the md5 hash // and return that. return array( $trueUser, md5( $password ) ); } // comma separated lists of methods you support. If, for example, // you cannot generate the hash for the bmd5 method, just // remove it from this list. function getMethods() { return "md5, bmd5"; } //////////////////////////////////////////////////// // The rest of the script should not be changed, //////////////////////////////////////////////////// // Of course, the AA password query passes in some variables. // The first is the query type; it can either be // 'methods' for a list of supported methods, // 'params' for a list of method parameters, or // 'check' to check a user's identity. $query = @strtolower($_REQUEST['query'] . ''); switch ( $query ) { case "methods": // give lists of supported methods. It's supposed to be "methods", // followed by a comma and/or whitespace separated list of the methods. conclude(200, 'METHODS '. getMethods() ); break; // the other two queries pass in more parameters, both have // the 'method' parameter that tells you which method should // be used. Well behaved servers will pick one of the methods // you support. case "params": $method = @strtolower($_REQUEST['method'] . ''); // give method parameter info if ( $method == 'md5' ) { // give prefix and suffix conclude( 200, "PREFIX " . getPrefix() . "\nSUFFIX " . getSuffix() ); } if ( $method == 'bmd5' ) { // bmd5 does not support or need extra parameters. conclude(200 , '' ); } // we know nothing about this. conclude(404 , 'UNKNOWN_METHOD' ); break; case "check": $method = @strtolower($_REQUEST['method'] . ''); // the last query passes in the username to check, $user = @$_REQUEST['user'] . ''; // a salt value (128 bit hexcoded) $salt = @$_REQUEST['salt'] . ''; // and a hash value the AA client has computed. $hash = @$_REQUEST['hash'] . ''; // we're supposed to check whether that hash is correct; // to do so, we need to do the same operations to the // password the client has done. // first, the client computed a hash of the password // with method-specific rules. we have // already prepared that here. . $userInfo = getPasswordHash( $user, $method ); // check if user exists in the first place. if ( $userInfo == NULL ) { conclude(404, 'UNKNOWN_USER ' . $user ); } // unpack user info $trueUser = $userInfo[0]; $correctPasswordHash = $userInfo[1]; // the operations the AA client did were not on the hex-encoded // hashes we have so far, but on binary packed variants thereof: $packedSalt = pack("H*", $salt); $correctPackedPasswordHash = pack('H*', $correctPasswordHash); // the client then simply calculated the MD5 sum of the two // concatenated packed values. $correctHash = md5($correctPackedPasswordHash . $packedSalt); // well, let's see if the client got it right! if (strcasecmp($hash, $correctHash) === 0) { // he did! Return OK, followed by the user's full name. // You can also append "blurb" messages in subsequent lines. // Those messages will be transformed a little (the first word gets // AUTHORITY_BLURB_ prepended to it and the user's authenticated name // is added as a second token) and written to the server's ladder log. conclude(200, 'PASSWORD_OK ' . $trueUser . '@' . $authority . "\nFOO baz" ); // A useful blurb example would be a line containing: // ALIAS oldusername@oldauthority // It would get logged as // AUTHORITY_BLURB_ALIAS user@authority oldusername@oldauthority // and nice ladder log parsing scripts can choose to believe your // authority and assume user@authority and oldusername@oldauthority // are the same person. It is a matter between ladderlog parser writers // and authority implementers to define more useful standard blurb messages. } // he didn't. conclude(401, 'PASSWORD_FAIL' ); // That's it. Note that any response other that a text beginning // with "PASSWORD_OK" and a 200 return code will be interpreted // by the server as an error and authentication will fail. // String comparisons for the control words (METHODS, PASSWORD_OK) // are case-insensitive on the server. We just like to return them // as caps becasue that looks more like CONTOL_CODES. break; default: // we don't know what the server wants from us // if execution ends up here. conclude(404, 'UNKNOWN_QUERY'); } ?>