Hello Sugumar, There are sites that store the commonly used strings and hashed strings. For example for hello sha2 hash is this 2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824 If you copy paste this in google, you would see hello they dont do reverse of this hash but they hashed some commonly used strings and kept in their DB, using this only they give the original string. That is why we need to use a salt string along with your original string. regards, James On Tue, Apr 5, 2016 at 11:44 AM, Sugumar <sugu.ece28 at gmail.com> wrote: > Thanks for all the information provided. Really its very nice information. > > And one more question, if i am using a salt with the password for computing > a hash value i need to store the salt for future reference and what about > the scenario when attacker gets that salt and hash. That time it may be > reversible right? > > Please tell me the correct method to use a salt with password for storing a > passwords in a secure manner. > > > > -- > View this message in context: > http://openssl.6102.n7.nabble.com/Is-SHA-hashing-algorithm-reversable-tp65408p65439.html > Sent from the OpenSSL - User mailing list archive at Nabble.com. > -- > openssl-users mailing list > To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mta.openssl.org/pipermail/openssl-users/attachments/20160405/cf318920/attachment.html>
