SHA256 عبر الإنترنت تجزئة مولد

Over the last few days I have been studying how hashing algorithms like SHA-256 actually work. To get a better understanding for the process I decided to implement it in python (3.6). By stitching together concepts from various websites like wiki and NIST pages I constructed the following code. I know the process is close to what it should be but when I test it results vary slightly from what they should be. For example, 'a' hashed with SHA-256 should be 'ca978112ca1bbdcafac231b39a23dc4da786eff8147c4e72b9807785afee48bb' however, my program returns 'ca978112ca1bbdcafac231b319a23dc4da786eff81147c4e72b9807785afee48bb'. The answers are very similar but are not the same. What am i doing wrong. Thank you for your time looking into it.

def hash(string):    return(process(pad(string)))def pad(string):    data = ""    length = len(string) * 8    for c in string:        data += bin(ord(c))[2:].zfill(8)    data += "1"    while len(data)%512 != 448:         data += "0"    data += bin(length)[2:].zfill(64)    return datadef process(bins):    main_block=[        0x428a2f98, 0x71374491, 0xb5c0fbcf, 0xe9b5dba5, 0x3956c25b, 0x59f111f1, 0x923f82a4, 0xab1c5ed5,        0xd807aa98, 0x12835b01, 0x243185be, 0x550c7dc3, 0x72be5d74, 0x80deb1fe, 0x9bdc06a7, 0xc19bf174,        0xe49b69c1, 0xefbe4786, 0x0fc19dc6, 0x240ca1cc, 0x2de92c6f, 0x4a7484aa, 0x5cb0a9dc, 0x76f988da,        0x983e5152, 0xa831c66d, 0xb00327c8, 0xbf597fc7, 0xc6e00bf3, 0xd5a79147, 0x06ca6351, 0x14292967,        0x27b70a85, 0x2e1b2138, 0x4d2c6dfc, 0x53380d13, 0x650a7354, 0x766a0abb, 0x81c2c92e, 0x92722c85,        0xa2bfe8a1, 0xa81a664b, 0xc24b8b70, 0xc76c51a3, 0xd192e819, 0xd6990624, 0xf40e3585, 0x106aa070,        0x19a4c116, 0x1e376c08, 0x2748774c, 0x34b0bcb5, 0x391c0cb3, 0x4ed8aa4a, 0x5b9cca4f, 0x682e6ff3,        0x748f82ee, 0x78a5636f, 0x84c87814, 0x8cc70208, 0x90befffa, 0xa4506ceb, 0xbef9a3f7, 0xc67178f2]    h0 = 0x6a09e667    h1 = 0xbb67ae85    h2 = 0x3c6ef372    h3 = 0xa54ff53a    h4 = 0x510e527f    h5 = 0x9b05688c    h6 = 0x1f83d9ab    h7 = 0x5be0cd19    for c in chunks(bins, 512):        words = chunks(c, 32)        w = [0]*64        w[:15] = [int(n, 2) for n in words]        for i in range(16, len(w)):            tmp1 = rightRotate(w[i-15], 7) ^ rightRotate(w[i-15], 18) ^ rightShift(w[i-15], 3)            tmp2 = rightRotate(w[i-2], 17) ^ rightRotate(w[i-2], 19) ^ rightShift(w[i-2], 10)            w[i] = (w[i-16] + tmp1 + w[i-7] + tmp2) & 0xffffffff    a = h0    b = h1    c = h2    d = h3    e = h4    f = h5    g = h6    h = h7    for i in range(0, 64):        s1 = rightRotate(e, 6) ^ rightRotate(e, 11) ^ rightRotate(e, 25)        ch = g ^ (e & (f ^ g))        tmp1 = h + s1 + ch + main_block[i] + w[i]        s0 = rightRotate(a, 2) ^ rightRotate(a, 13) ^ rightRotate(a, 22)        maj = (a&b) ^ (a&c) ^ (b&c)        tmp2 = s0 + maj        h = g        g = f        f = e        e = d + tmp1 & 0xffffffff        d = c        c = b        b = a        a = tmp1 + tmp2 & 0xffffffff    h0 += a     h1 += b    h2 += c     h3 += d     h4 += e     h5 += f     h6 += g    h7 += h    return '%08x%08x%08x%08x%08x%08x%08x%08x' % (h0, h1, h2, h3, h4, h5, h6, h7) def rightShift(x, n):    return (x & 0xffffffff) >> ndef rightRotate(x, y):    return (((x & 0xffffffff) >> (y & 31)) | (x << (32 - (y & 31)))) & 0xffffffffdef chunks(l, n):        return [l[i:i+n] for i in range(0, len(l), n)]string = "a"print(hash(string))

here in Italy, we will need to digitally sign all invoices since January 2019.

I found a code that works well with sha-1, but I need to use sha256 as standard.The code below, after successfully detect USB key, and ask me for the certificate to use try to sign "NomeFile" file After and output in "NomeFile".p7m, when the line

signedCms.ComputeSignature(signer,false);

runs, it happens:1- if use sha-1 it asks me for the PIN and document is successfully created.2- if use sha-256 don't ask for PIN and gives me Unknown error -1073741275

I read a lot of posts that are all old (2011-2014). Other people have the same problem and seem that Microsoft has some bug using sha256.

Now we are at end of 2018 and I tried this code in .net 4, 4.6.1 and 4.7.2 but the error is the same.

Somebody can tell me if Microsoft corrects the problem with sha256 and what could be this strange error? (-1073741275) Error Stack

public String FirmaFile(String NomeFile, DateTime DataFirma, X509Certificate2 cert, out string RisFirma)        {            String NomeFirma = NomeFile + ".p7m";            RisFirma = "";            try            {                // content contiene il file da firmare                ContentInfo content = new ContentInfo((File.ReadAllBytes(NomeFile)));                // assegniamo content ad un oggetto di tipo SignedCms                SignedCms signedCms = new SignedCms(SubjectIdentifierType.IssuerAndSerialNumber, content, false);                // si instanzia un oggetto CmsSigner che espone i metodi di firma.                CmsSigner signer = new CmsSigner(cert);                signer.IncludeOption = X509IncludeOption.EndCertOnly;                //signer.DigestAlgorithm = new Oid("2.16.840.1.101.3.4.2.1");                signer.DigestAlgorithm = new Oid("SHA256");                signer.SignedAttributes.Add(new Pkcs9SigningTime(DataFirma));                try                {                    // Viene calcolata la firma del file (in formato PKCS7)                    signedCms.ComputeSignature(signer,false);                }                catch (CryptographicException CEx)                {                    RisFirma = "Errore: " + CEx.Message + " Stack: " + CEx.StackTrace;                    return RisFirma;                }                // si pone il file firmato in un array.                byte[] signature = signedCms.Encode();                File.WriteAllBytes(NomeFirma, signature);                RisFirma = "true";            }            catch (Exception Ex)            {                RisFirma = "Errore in FirmaFile: " + Ex.Message + " Stack: " + Ex.StackTrace;            }            return RisFirma;        }

NB: I tried 2 version of OIDsigner.DigestAlgorithm = new Oid("2.16.840.1.101.3.4.2.1");signer.DigestAlgorithm = new Oid("SHA256");

All 2 give the same error.

I USE an INFOCERT USB KEY with driver bit4id (https://www.bit4id.com/it/4identity/) that is contained in USB Drive.

I'm trying to port a crypto exchange API from JavaScript to Rust. The JavaScript version authenticates and connects. The payload and secret key are signed using Hmac Sha256 and encoded to Base64. Below is the working implementation in JavaScript.

var param = "test";var privateKey = "secret";var signature = crypto.createHmac('sha256', new Buffer(privateKey, 'utf8'))    .update(param)    .digest('base64');

It returns the following signature: Aymga2LNFrM+tnkr6MYLFY2Jou46h2/Omogeu0iMCRQ=

In Rust i'm using Hmac SHA256 and encoding the result back to Base64 yet i'm unable to get close to the expected signature. Here is my best 2 day attempt at this:

extern crate ring;extern crate data_encoding;extern crate hex;use ring::{digest, hmac};use data_encoding::BASE64;use hex::encode as hex_encode;fn main() {    let secret_key = "secret";    let payload = "test";    let signed_key = hmac::SigningKey::new(&digest::SHA256, secret_key.as_bytes());    let signature = hex_encode(hmac::sign(&signed_key, payload.as_bytes()).as_ref());    let b64_encoded_sig = BASE64.encode(signature.as_ref());    assert_eq!(b64_encoded_sig, "Aymga2LNFrM+tnkr6MYLFY2Jou46h2/Omogeu0iMCRQ=");}

This returns the following signature: MDMyOWEwNmI2MmNkMTZiMzNlYjY3OTJiZThjNjBiMTU4ZDg5YTJlZTNhODc2ZmNlOWE4ODFlYmI0ODhjMDkxNA==

Would really appreciate getting a point in the right direction, gone around in circles for days now and not sure where exactly i'm going wrong. Thanks.

I am looking for some function or a way that would return HMAC SHA256 hash in C++ using secret key. I have seen documentation of Crypto++ and OpenSSL but it does not accept an extra parameter of secret key for computation. Can someone help me by providing some info, code snippets or links.

I try to parse Bearer Tokens from a Http Request to get the client information in the next step. It works most of the time really well but sometimes sentry throws me an error: "The JWT string must have two dots".How can I prevent this case?

$bearerToken = Request::bearerToken();$parsedToken = (new Parser())->parse($bearerToken);