Pw md5? :t

[Szaer]

What is wrong with the md5 encoding? >:C

Using the same md5 from the register script I used to create the test account, it comes OUT differently. The executed md5 password makes more sense, because you can tell my the script it's supposed to be "0x#########", but when you pull a password from the database it comes up in characters like "(SÉA^˜ s ©". :T

I don't ever recall having this problem a couple years ago. I'm guessing the md5 has changed but why and how do you even get it to work.

The encoding script DIRECTLY from the basic register page reads

$Salt = $Login.$Pass;
$Salt = md5($Salt);
$Salt = "0x".$Salt; 

So yeah, Im not quite sure why in the database it's in characters instead of the 0x format.


... and why did it make the T in my title lower case ):

[MentaL]

[das7002]

What is wrong with the md5 encoding? >:C

Using the same md5 from the register script I used to create the test account, it comes OUT differently. The executed md5 password makes more sense, because you can tell my the script it's supposed to be "0x#########", but when you pull a password from the database it comes up in characters like "(SÉA^˜ s ©". :T

I don't ever recall having this problem a couple years ago. I'm guessing the md5 has changed but why and how do you even get it to work.

The encoding script DIRECTLY from the basic register page reads

$Salt = $Login.$Pass;
$Salt = md5($Salt);
$Salt = "0x".$Salt; 

So yeah, Im not quite sure why in the database it's in characters instead of the 0x format.


... and why did it make the T in my title lower case ):

md5($salt, true);

I believe it is just the md5 in binary before the hex convert, if you run bin2hex(md5("test" ,true)) it would be equal to md5("test")

Over in the aion section the server they made runs similarly in which it is just the sha1 in binary but base64 encoded