> I will like to know exact MD5 hash conversation for this number 81dc9bdb52d04dc20036dbd8313ed055
Just be warned: there are different ways of formatting that result, and it assumes no salt. Best practices for authentication are to prepend a per-user salt before creating each hash value. And really, best practices say not to use md5 for passwords at all. It's too weak, almost to the point where you may just as well store your passwords in plain text. A better option is bcrypt, which is now supported by koha. > how I can decode md5 hash encryption hashes are not encryption. The difference between a hash and encryption is that hashes are* one way*: *they cannot be decrypted/decoded*. Joel Coehoorn Director of Information Technology York College, Nebraska 402.363.5603 [email protected] *The mission of York College is to transform lives through Christ-centered education and to equip students for lifelong service to God, family, and society* On Mon, Feb 17, 2014 at 11:19 AM, geromoselle <[email protected]> wrote: > I am doing bulk uploading for our library patrons for the first time. I > set a default password for all my patrons to be 1234 which they can change > on their own at the OPAC page. Please, I will like to know exact MD5 hash > conversation for this number or precisely how I can decode md5 hash > encryption. > > > Sent from Samsung Mobile > _______________________________________________ > Koha mailing list http://koha-community.org > [email protected] > http://lists.katipo.co.nz/mailman/listinfo/koha > _______________________________________________ Koha mailing list http://koha-community.org [email protected] http://lists.katipo.co.nz/mailman/listinfo/koha
