The error message means exactly what it says: You have a Unicode string. You can’t SHA-256-hash a Unicode string, you can only hash bytes. But why do you have a Unicode string? Because you’re opening a file in text mode, which means you’re implicitly asking Python to decode the bytes in that file (using your …
using hashlib: from hashlib import sha256 input_ = input(‘Enter something: ‘) print(sha256(input_.encode(‘utf-8’)).hexdigest())
The crypto/sha256 godoc actually has a snippet that shows how to do that (it’s basically the same code as James): package main import ( “crypto/sha256” “fmt” “io” “log” “os” ) func main() { f, err := os.Open(“file.txt”) if err != nil { log.Fatal(err) } defer f.Close() h := sha256.New() if _, err := io.Copy(h, f); …
I know this post is old, but it took me forever to figure this out, so I thought I would share. To test I created RSA keys using OpenSSL: openssl genrsa -out privateKey.pem 512 openssl rsa -in privateKey.pem -pubout -out publicKey.pem You will need the following 2 nuget packages: https://github.com/dvsekhvalnov/jose-jwt http://www.bouncycastle.org/csharp/ Test Code public static …
Don’t use a simple hash, or even a salted hash. Use some sort of key-strengthening technique like bcrypt (with a .NET implementation here) or PBKDF2 (with a built-in implementation). Here’s an example using PBKDF2. To generate a key from your password… string password = GetPasswordFromUserInput(); // specify that we want to randomly generate a 20-byte …
Switching to SHA512 will hardly make your website more secure. You should not write your own password hashing function. Instead, use an existing implementation. SHA256 and SHA512 are message digests, they were never meant to be password-hashing (or key-derivation) functions. (Although a message digest could be used a building block for a KDF, such as …
Yes, a SHA256 is always 256 bits long, equivalent to 32 bytes, or 64 bytes in an hexadecimal string format. You can even use char(64) instead of varchar(64) since the size won’t change.
There is technically a limit, but it’s quite large. The padding scheme used for SHA-256 requires that the size of the input (in bits) be expressed as a 64-bit number. Therefore, the maximum size is (264-1)/8 bytes ~= 2’091’752 terabytes. That renders the limit almost entirely theoretical, not practical. Most people don’t have the storage …
Could this be a typo? (two Ps in ppasscode, intended?) $_POST[‘ppasscode’]; I would make sure and do: print_r($_POST); and make sure the data is accurate there, and then echo out what it should look like: echo hash(‘sha256’, $_POST[‘ppasscode’]); Compare this output to what you have in the database (manually). By doing this you’re exploring your …
This is what I’m using for SHA1: #import <CommonCrypto/CommonDigest.h> + (NSData *)sha1:(NSData *)data { unsigned char hash[CC_SHA1_DIGEST_LENGTH]; if ( CC_SHA1([data bytes], [data length], hash) ) { NSData *sha1 = [NSData dataWithBytes:hash length:CC_SHA1_DIGEST_LENGTH]; return sha1; } return nil; } Replace CC_SHA1 with CC_SHA256 (or whichever you need), as well as CC_SHA1_DIGEST_LENGTH with CC_SHA256_DIGEST_LENGTH.