-
Check for module_exist('challenge_response') was redundant. -
Check for existing challenge and deletion of challenge is now one atomic action. Using plain old 'DELETE', since it returns True on success, and NULL on failure.
-
README and INSTALL added. Very basic README - no explanation of how things work.
-
Fixed link in login error message (What is challenge/response authentiation?).
-
user.patch reflets coding standards. md5.js is required for client-side MD5 hashing.
-
Initial version of challenge_response module. Implements challenge/respon- se authentication using: one-time MD5 hash of "random" number; MD5 of users's password; client-side generated response. If the client-side resp- onse matches a response generated by the server, the user is granted access to the system.