Prev | Current Page 427 | Next

L. McColl-Sylvester and F. Ponticelli

"Professional haXe and Neko"


Cryptographic hashes are commonly used as digital fingerprints to identify file binaries and securely
store user passwords. The first most common case is to ensure that a transmitted file has been received
untempered or uncorrupted; on the source of the hash the file is produced and distributed along with
the binary file. A client receives the file and makes its own hash encoding; if the result matches with the
original hash the file has been received unchanged.
The other very common use in user access management is to store the user password cryptographic
hashes instead of the real password; needless to say, it can be dangerous having all the user passwords
stored in one place and bi - direction cryptography is only a small step better. Each time a user attempts a
log in, the provided password is encoded in its hash form and matched against the hash stored in the
users ??™ database.
The haxe.Md5 class provides just one single public static method encode() that accepts a single string
argument, the value to encode, and returns a string result, the hash.


Pages:
415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439