Xojo SHA1 different than MySQL SHA1

[Brock_Nash]

Isn’t SHA1 like a standard. Why do I get different result when I do it in Xojo versus MySQL? Am I doing something wrong?

dim sha1 as string = EncodeBase64(Crypto.SHA1("1234567890'"))

NRHAju1scRWuELagZpnGvT9vMRs=

In MYSQL

SELECT SHA1('1234567890')

01b307acba4f54f55aafc33bb06bbbf6ca803e9a

[Kem_Tekinay]

Try EncodeHex instead of EncodeBase64.

[Brock_Nash]

@489357:@Kem Tekinay

Try EncodeHex instead of EncodeBase64.

In Xojo I then get “3511C08EED6C7115AE10B6A06699C6BD3F6F311B” which is still different than the MySQL DB

[Jay_Madren]

@489358:@Brock Nash

In Xojo I then get “3511C08EED6C7115AE10B6A06699C6BD3F6F311B” which is still different than the MySQL DB

If you’re using the above code verbatim, you have an anomalous apostrophe character in the Xojo string.

[Kem_Tekinay]

Jay spotted that fast, and I can confirm that that must be the issue.

[Brock_Nash]

@Jay Madren catching the extra apostrohpe and
@Kem Tekinay saying to use the EncodeHex instead was the magic!

Thanks Guys!