12.05.2013, 11:53
Hashes are not meant to be decoded/decrypted/hacked. That's the point of hashes. They're one way only. If you need to compare passwords, then hash the input password and compare it with what's stored in the database.
That said, num_hash (a.k.a. Adler32) can't be considered a decent form of security. It is in fact a checksum algorithm rather than a hashing algorithm. If you're just a little bit serious about security then you should rid yourself of dini and dutils. I don't know whether you're using files or MySQL, but both systems have far better hashing algorithms available. For a file based system you can use Whirlpool, for a MySQL based system you can use (a combination of) md5, sha1 or sha2.
That said, num_hash (a.k.a. Adler32) can't be considered a decent form of security. It is in fact a checksum algorithm rather than a hashing algorithm. If you're just a little bit serious about security then you should rid yourself of dini and dutils. I don't know whether you're using files or MySQL, but both systems have far better hashing algorithms available. For a file based system you can use Whirlpool, for a MySQL based system you can use (a combination of) md5, sha1 or sha2.