Online SHA1 hash Generator

What I'm trying to do is use SHA1 UTF-8 encryption and then base64 encoding and on a password string value. However, I needed to do the encryption first, then the encoding, but I did it the other way around.

Here is the code:

# Create Input Data $enc = [system.Text.Encoding]::UTF8$string1 = "This is a string to hash" $data1 = $enc.GetBytes($string1) # Create a New SHA1 Crypto Provider $sha = New-Object System.Security.Cryptography.SHA1CryptoServiceProvider $# Now hash and display results $result1 = $sha.ComputeHash($data1) 

So, when I went to do the hashing I realized I had to have a byte[] from the string and I'm not sure how to do that. I'm thinking there is a simple way from the .Net libraries, but couldn't find an example.

So if I have a string, like:

$string = "password"

How do I convert that into a byte array that I can use on :: ComputeHash($string)?

So what I have to end up with is an encrypted SHA-1 and base 64 encoded UTF-8 password, which the code above does, but it's coming back different than when I coded this same thing in java, where I encrypted it first, then converted that result to base 64 encoding.

I'm making the assumption that while encrypting a string directly isn't supported in the api, there may be a work-around that will allow you to do this. That is what I'm attempting to do.

So I'm assuming my issue with the code is that I had to encrypt it first and then encode it to get the correct value. Correct or am I missing something here?

Here is the pertinent java code that does work:

//First method call uses a swing component to get the user entered password.String password = getPassword(); //This line is where the work starts with the second and third methods below.String hashed = byteToBase64(getHash(password));//The second method call here gets the encryption.public static byte[] getHash(String password) {      MessageDigest digest = null;      byte[] input = null;      try {             digest = MessageDigest.getInstance("SHA-1");      } catch (NoSuchAlgorithmException e1) {             e1.printStackTrace();      }      digest.reset();      try {             input = digest.digest(password.getBytes("UTF-8"));      } catch (UnsupportedEncodingException e) {             e.printStackTrace();      }      return input;}//Then the third method call here gets the encoding, FROM THE ENCRYPTED STRING.public static String byteToBase64(byte[] data){    return new String(Base64.encodeBase64(data));

When I run the java code with the password string of "password" I get

[91, -86, 97, -28, -55, -71, 63, 63, 6, -126, 37, 11, 108, -8, 51, 27, 126, -26, -113, -40]which is the encryption.

Then I when the encoding in java I get this:W6ph5Mm5Pz8GgiULbPgzG37mj9g=

but when I run it in PowerShell I get this because it's encoded first for UTF8:

91 170 97 228 201 185 63 63 6 130 37 11 108 248 51 27 126 230 143 216

Then when I run this line of code to convert it I get an error:

$base64 = [System.Convert]::FromBase64String($result)

Exception calling "FromBase64String" with "1" argument(s): "Invalid length for a Base-64 char array."At line:1 char:45

However, if I run the new line of code to make it hex from below I get:

$hexResult = [String]::Join("", ($result | % { "{0:X2}" -f $_}))PS C:\Program Files (x86)\PowerGUI> Write-Host $hexResult

5BAA61E4C9B93F3F0682250B6CF8331B7EE68FD8

but I need to end up with this value:

W6ph5Mm5Pz8GgiULbPgzG37mj9g=

Again, this may not even be possible to do, but I'm trying to find a work-around to see.

I have the following PHP function

public function encodePassword($raw, $salt)    {        return hash_hmac('sha1', $raw . $salt, $this->secret);    }

which I need to translate to Go. I found the following example, but it doesn't involve secret key.https://gobyexample.com/sha1-hashes

How can I create a function in Go, that produces exactly same result as PHP's hash_hmac?

Update: After Leo's answer, found this resource with hmac examples in many languages: https://github.com/danharper/hmac-examples. Can be useful to somebody.

I have a simple question which occured when I wanted to store the result of a SHA1 hash in a MySQL database:

How long should the VARCHAR field be in which I store the hash's result?

I am trying to figure out why I am not getting the same hash when running a string through the sha1 algorithm.

Please consider these results:

echo moosecodes | shasum538f5d940a8f1aeabde1d5c6da4ebae1230ba5da  -echo -n moosecodes | shasum  c09129372713d1c7005f4aa1d50bf598912c473a  -

temp.txt contains the string moosecodes with no new line, but the hash is different when the string is echoed from a file:

echo temp.txt | shasumc3ec5f2c30a4198dc4e0323101441da0bcdd2aa9  -echo -n temp.txt | shasum45ebed19db9cfb3cea503d6b62a50ffe6b30247c  -

Can anyone explain to me why this is happening? At first I thought it had to do with the fact that the file has meta-data attached to it, but in this case I am just echo-ing its contents to the hasher, so wouldn't it be the same as the first two examples I show above?

When I run this command:

tar -xOzf oresoftware-npp-0.0.1002.tgz | sort | sha1sum

I get this:

fadc89dd523fd54299aed689a90f73243c5336b8  -

does anyone know what the trailing dash - is supposed to represent?