The following is an example, written in Visual Basic, of how to compute the SHA-256 hash for the data string "myPassword" and display it in a label called Label1:
Public Class Form1
Private Function ComputeSHA256Hash(ByVal Password As String) As String
' Convert Password into a byte array.
Dim passwordBytes As Byte()
passwordBytes = Encoding.UTF8.GetBytes(Password)
' Initialize the SHA256 hashing algorithm class
Dim shaM As New SHA256Managed()
' Compute hash value of the password.
Dim hashBytes As Byte()
hashBytes = shaM.ComputeHash(passwordBytes)
' Convert hash into a base64-encoded string.
ComputeSHA256Hash = Convert.ToBase64String(hashBytes)
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
Label1.Text = ComputeSHA256Hash("myPassword")End Sub
The ComputeSHA256Hash function uses the .NET Framework Class Library System.Security.Cryptography class. It takes the string Password and turns it into a byte-array. It then runs those bytes through the SHA256Managed computation function provided by the class and returns a 44-bit string of the hash that's created. It finally displays via Labe1.Text. The hash for myPassword using this program is dlSbgn7EbnBf0DgxgT+lIXIzjw38vXEe1EuBqW2sUcY=. If you change the input to mzPassword, so just one character different, the hash changes to something completely different - XkdNLN2VuBgcMjhI/Dg0ioj4Eds6FLDF3lRlBxt+I4U=.
For security reasons, if you are using hash values to store passwords, you may well want to use a salt, as this makes a hashed-password less immune to dictionary attacks. Not only would the hacker have to develop a hash for every commonly known password, but also for every commonly known password multiplied by the nearly infinite number of possible salts.
Dig Deeper on Disk and file encryption tools
Related Q&A from Michael Cobb
WhatsApp vulnerabilities can enable hackers to bypass end-to-end encryption and spoof messages. Expert Michael Cobb explains how these attacks work ... Continue Reading
Disabling Google location tracking involves more than turning off Location History. Learn how to manage your account settings to stop tracking ... Continue Reading
Compared to TLS 1.2, TLS 1.3 saw improvements in security, performance and privacy. Learn how TLS 1.3 eliminated vulnerabilities using cryptographic ... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.