he clearly mentions that in the script he has given you need not to do that…

Backbone said:
As far as I see through this method there is no SQL Injection possibility, no need of mysql_real_escape_string() or to worry about hex encoded strings, etc

and he is trying to implement security through obscurity…

Yes you are right he could have used the method you suggested (and most of the developers use it the same way) but it opens up the chances of sql injection..

where as the script written by backbone reduces that risk but on the other hand this script lacks performace… As this script gonna give a shocking performance on a table with 1000s of users….

irony is …. he got a prize for this script… but still its a good try from his side

$build = "SELECT * FROM usr WHERE uname='".$uname."' AND passwd='" .md5($passwd). "';

If zero rows returned, done. Else 1 row returned, done.

1. Loop through the results like the person said above.

2. Use mysql_real_escape_string() Like someone else said

3. or, don’t allow anything except for word chars in their username, and use preg_replace(’/[^\w]/’, ”, $usr);

That will strip any non-word chars out thus sanitizing it on the way in, which is a technique used time and time again.

I admit though, it is pretty clever.

moved on to data centre management.

oh and my login script was for an intranet environment,
just to be clear on the query mess.
Still, I think this is an ok solution, for some situations.
And creativety should be sponsored and welcomed with open arms.
There aren’t enough developers and designers and some them lack proper guidans thru proper management and training.

Some employees had the same password.
That was a sad day for me
I solved it by comparing an array of userids in a loop.
until the userid was found or the array was empty.

set your $ok=0; in the loop, this helps against
login.php?$ok=1

stay creative