Ok, here's the question. I need a secured log-in page which is running on a DSN-less connection that confirms an unlinimted amount of usernames and passwords. That's the easy part, the hard part is that I want the password to be hashed so that the user may not intercept the transfer of the connection to read the password. At the same time, I want it to be hashed in the database with a different hash formula, so that if some lamer taken over control of my database, he/she cannot decode the username and password.
