Md5() is One Way Function Mean you can Encrypt Something But After that you can not decrypt it :). thats y its most secure .suppose you want to Encrypt password information then By using MD5 You can encrypt Password and Store it in Database like Encrypted String like for example (DFGDFdFDGDFGDFGDFGDFGDFBCVB) now when user login user entereds its password in Simple Text and Software Again Convert User Entered SimpleText To (DFGDFdFDGDFGDFGDFGDFGDFBCVB) and then Encrypted String in Database and encrypted String of User entered Password are Matched if they are Same User is allowed :) is this way MD5 is used :)
In theory, hash algorithms are one-way and not subject to decryption. How hash algorithms become vulnerable is by what is called collisions using collision attacks. For example, if someone figured out your password and for the sake of this example your password was "password". The MD5 cryptographic hashing algorithm will always have the result; 5f4dcc3b5aa765d61d8327deb882cf99. So, the object here would be to use a dictionary attack to guess your password, use brute force or simply compare this hash to any hash in the database. Encryption on the other hand (PKI) involves a private and public key like OpenPGP. The public key is just that, public and anyone can have it, use it but without the private key. No one can decrypt the information that the public key encrypted. The output is always different. To find out more you can simply do a Google search for MD5 and SHA1 collision vulnerabilities and OpenPGP. Hope this helps.
YOU DON’T ENCRYPT PASSWORDS. For the billionth time, you HASH a password, preferably with a 256-bit random salt. Encryption uses a secret key to encrypt and decrypt a message, hashing uses no keys and can’t be reversed- they are totally different things.
They hash in this tutorial, but there are certainly situations you want to encrypt. Right now Im developing a system tray application that should have next to no user interaction. That means I need to save the credentials to get a new token from my api from time to time. Hashing makes no sense, since I need to actually send the credentials.
Thank you for the tutorial!
You're welcome & Thank you :)
Great 👍👍👍
Thank you for making this video!
Nice!
Can a tool be created to decrypt that password?
Thanks
moedaturk you neither encrypt nor decrypt a password. You hash it, and you can’t (easily) undo a hash.
@@gregoryfenn1462 yeah you can, and if the password is easy, you can crack it under 2 hours
@@gregoryfenn1462 You need to decrypt it, however, if you're creating some sort of passwordmanager.
Speechless!
thank you !
How to make the form's text come in between you?
Can you describe more details. thank you !
nice, it works!
Great. Thank you !
that is good. But now ehat can we decrypt it ?
Hi, You can't decrypt md5 but you can view th-cam.com/video/Lu4ZT9oKwTw/w-d-xo.html to know how to encrypt & decrypt a string or password. thanks
sha256?
OK. Thank you for your suggestion
thx
Can this be decrypted?
Hi. Yes. You can encrypt or decrypt. I'll make the tutorial as soon as possible. Thanks
Md5() is One Way Function
Mean you can Encrypt Something But After that you can not decrypt it :). thats y its most secure .suppose you want to
Encrypt password information then By using MD5 You can encrypt Password and Store it in Database like Encrypted
String like for example (DFGDFdFDGDFGDFGDFGDFGDFBCVB) now when user login user entereds its password in
Simple Text and Software Again Convert User Entered SimpleText To (DFGDFdFDGDFGDFGDFGDFGDFBCVB) and then
Encrypted String in Database and encrypted String of User entered Password are Matched if they are Same User is
allowed :) is this way MD5 is used :)
Is your voice ?
how to decrypt this?
OK. Thank you for your suggestion. I'll upload soon !
@@foxlearn Thank you so much :D
keep up the good work! Love this channel, so helpful :D
In theory, hash algorithms are one-way and not subject to decryption. How hash algorithms become vulnerable is by what is called collisions using collision attacks. For example, if someone figured out your password and for the sake of this example your password was "password". The MD5 cryptographic hashing algorithm will always have the result; 5f4dcc3b5aa765d61d8327deb882cf99. So, the object here would be to use a dictionary attack to guess your password, use brute force or simply compare this hash to any hash in the database.
Encryption on the other hand (PKI) involves a private and public key like OpenPGP. The public key is just that, public and anyone can have it, use it but without the private key. No one can decrypt the information that the public key encrypted. The output is always different.
To find out more you can simply do a Google search for MD5 and SHA1 collision vulnerabilities and OpenPGP.
Hope this helps.
YOU DON’T ENCRYPT PASSWORDS. For the billionth time, you HASH a password, preferably with a 256-bit random salt. Encryption uses a secret key to encrypt and decrypt a message, hashing uses no keys and can’t be reversed- they are totally different things.
They hash in this tutorial, but there are certainly situations you want to encrypt.
Right now Im developing a system tray application that should have next to no user interaction.
That means I need to save the credentials to get a new token from my api from time to time.
Hashing makes no sense, since I need to actually send the credentials.
Who came here because they forgot their password?