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

I'm working on asp.net mcv app where user can select and upload multiple file from UI.

When user upload file(s), I it will immediately uploaded using ajax.

1. I want to encrypt it on the fly while its uploading
2. I'm using sha256
3. constraint is time and performance for larger files (i'm not sure how big file sha256 supports)

what I've tried

How can I encrypt/decrypt arbitrary binary files using Javascript in the browser?

Create SHA-256 hash from a Blob/File in javascript

And I've tried to use following js lib. for that

js-sha256 and asmcrypto-lite

But I have no idea how to use it. I searched for examples and I found some but all are related to encrypt text and getting hash I don't where do I get my encrypted file(s) what is ceremony to follow in order to encrypt and generate hash, which function to call.

Here is code my js code sample

 function uploadFileInBlocks(ev) {      //....other code... //        ev.reader = new FileReader();        ev.reader.onloadend = function (evt) {            if (evt.target.readyState === FileReader.DONE) {                var uri = ev.submitUri + "&comp=block&blockid=" + ev.blockIds[ev.blockIds.length - 1];               //here I want encrypted data in "requestData" variable and hash in other variable                var requestData = new Uint8Array(evt.target.result);                 $.ajax({                    url: uri,                    type: "PUT",                    data: requestData,                    processData: false                }).done(function (data, status) {                   uploadBlock(ev);                }).fail(function (xhr, desc, err) {                    //TODO: error handling                });            };        }        uploadBlock(ev);    } function uploadBlock(ev) {        if (ev.totalBytesRemaining > 0) {            var fileContent = ev.selectedFile.slice(ev.currentFilePointer, ev.currentFilePointer + ev.maxBlockSize);            var blockId = blockIdPrefix + pad(ev.blockIds.length, 6);            //console.log('blockid: ' + blockId);            ev.blockIds.push(btoa(blockId));            ev.reader.readAsArrayBuffer(fileContent);            ev.currentFilePointer += ev.maxBlockSize;            ev.totalBytesRemaining -= ev.maxBlockSize;            if (ev.totalBytesRemaining < ev.maxBlockSize) {                ev.maxBlockSize = ev.totalBytesRemaining;            }        } else {            commitBlockList(ev);        }    }

I used js-sha256 example but its confusing. it returns hash not file

sha256(new Uint8Array(evt.target.result));

Any help would be appreciated.

I am creating a request xml with digital signature. Below is my code.

CryptoConfig.AddAlgorithm(typeof(RSAPKCS1SHA256SignatureDescription), "http://www.w3.org/2001/04/xmldsig-more#rsa-sha256");        var exportedKeyMaterial = cert.PrivateKey.ToXmlString( /* includePrivateParameters = */ true);        var key = new RSACryptoServiceProvider(new CspParameters(24 /* PROV_RSA_AES */));        key.PersistKeyInCsp = false;        key.FromXmlString(exportedKeyMaterial);        string tokenId = string.Format("X509-{0}", Guid.NewGuid());        string signatureId = string.Format("SIG-{0}", Guid.NewGuid());        string tokenRefId = string.Format("STR-{0}", Guid.NewGuid());        string kiId = string.Format("KI-{0}", Guid.NewGuid());        string bodyId = string.Format("id-{0}", Guid.NewGuid());        XmlNamespaceManager ns = new XmlNamespaceManager(xmlDoc.NameTable);        ns.AddNamespace("soapenv", "http://schemas.xmlsoap.org/soap/envelope/");        ns.AddNamespace("wsse", "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd");        ns.AddNamespace("wsa", "http://schemas.xmlsoap.org/ws/2004/08/addressing");        ns.AddNamespace("wsu", "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd");        XmlElement body = xmlDoc.DocumentElement.SelectSingleNode(@"//soapenv:Body", ns) as XmlElement;        if (body == null)            throw new ApplicationException("No body tag found");        body.SetAttribute("id", bodyId);        SignedXml signedXml = new SignedXml(body);        signedXml.Signature.Id = signatureId;        signedXml.SigningKey = key;        signedXml.SignedInfo.SignatureMethod = "http://www.w3.org/2001/04/xmldsig-more#rsa-sha256";        KeyInfo keyInfo = new KeyInfo();        keyInfo.Id = kiId;        SecurityTokenReference tokenRef = new SecurityTokenReference();        tokenRef.ValueType = "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3";        tokenRef.RelativeReference = tokenId;        tokenRef.Id = tokenRefId;        // Add Security Token reference        keyInfo.AddClause(tokenRef);        signedXml.KeyInfo = keyInfo;        signedXml.SignedInfo.CanonicalizationMethod = SignedXml.XmlDsigExcC14NTransformUrl;        XmlDsigExcC14NTransform canMethod = (XmlDsigExcC14NTransform)signedXml.SignedInfo.CanonicalizationMethodObject;        canMethod.InclusiveNamespacesPrefixList = "soap";        Reference reference = new Reference();        reference.Uri = string.Format("#{0}", bodyId);        reference.DigestMethod = "http://www.w3.org/2001/04/xmlenc#sha256";        reference.AddTransform(new Microsoft.Web.Services3.Security.Xml.XmlDsigExcC14NTransform());        signedXml.AddReference(reference);        signedXml.ComputeSignature();XmlElement signedElement = signedXml.GetXml(); string hash = CalculateDigestOfBody(body);public string CalculateDigestOfBody(XmlElement xmlDoc)        {            SHA256 algo = new SHA256CryptoServiceProvider();            byte[] byteHash = algo.ComputeHash(Encoding.UTF8.GetBytes(xmlDoc.OuterXml));            string hashString = Convert.ToBase64String(byteHash);            return hashString;        }

This produces the below soap header

<Signature Id="SIG-44779d9b-7d39-4c27-877b-a6de1d9365fc" xmlns="http://www.w3.org/2000/09/xmldsig#"><SignedInfo>    <CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#">        <InclusiveNamespaces PrefixList="soap" xmlns="http://www.w3.org/2001/10/xml-exc-c14n#" />    </CanonicalizationMethod>    <SignatureMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256" />    <Reference URI="#id-98b3d734-ee46-49bb-aee8-c151d41defe5">        <Transforms>            <Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />        </Transforms>        <DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256" />        <DigestValue>..</DigestValue>    </Reference></SignedInfo><SignatureValue>..</SignatureValue>

When I compare the digest value from ComputeSignature and manually calculated hash/digest, they are not equal.

As per my understanding they should be equal as both are calculated on body.

What am I missing here.

I have a table that is filled with some value, for setting the value I use a stored procedure that also calculate a hash function and save in database.In case of updating value hash should be recalculated. For recalculating hash I use the following procedure:

DELIMITER $$CREATE PROCEDURE `sp_UpdateHash`(IN rkey int)BeginDECLARE AuthCode VarChar(10);SET @input = concat('SELECT r_ac into @AuthCode    FROM table_rec    where r_key=',rkey);PREPARE squery FROM @input;EXECUTE squery;SET @hashed = SHA2(@AuthCode,256);select @hashed;DEALLOCATE PREPARE squery;end;

and procedure just for calculating hash:

CREATE PROCEDURE `sp_GetHash`(IN AuthCode VarChar(10))BEGIN    DECLARE hashed VarChar(64);    SET hashed = SHA2(AuthCode,256);    select hashed as 'Hash';END

AuthCode identical, but hash is different when I try to process value after select command I get a wrong code. If I compare two hashes with other results, for example from an online generator, the result is similar to the second function: sp_GetHash

Do you have any idea why?

In Node.js I use following code

hash = crypto.createHmac('sha256', SECRET).update(file).digest('hex');

to calculate HMAC. However Linux command line analog produces different hash code:

> openssl sha256 -hmac "SECRET" file

What is wrong in command line? What are correct arguments?

I am facing a very strange issue and have spent 3+ days on it. I am going through AWS's signing request version 4 documentation and am investigating their HMAC signing process.

I am using node-forge to calculate an HMAC-sha256 based upon a given string and key, using this AWS doc: https://docs.aws.amazon.com/general/latest/gr/signature-v4-examples.html

These are the exact same strings as the documentation encoded as the documentation says to UTF-8:

const hash_type = 'sha256';const hmac = forge.hmac.create();const key = forge.util.encodeUtf8('c4afb1cc5771d871763a393e44b703571b55cc28424d1a5e86da6ed3c154a4b9');const string = forge.util.encodeUtf8('AWS4-HMAC-SHA256\n' +  '20150830T123600Z\n' +  '20150830/us-east-1/iam/aws4_request\n' +  'f536975d06c0309214f805bb90ccff089219ecd68b2577efef23edd43b7e1a59');hmac.start('sha256', key);hmac.update(string);console.log('SIGNATURE: ' +  hmac.digest().toHex());

My function, along with every single HMAC calculator I use online give the caluclated hash as fe52b221b5173b501c9863cec59554224072ca34c1c827ec5fb8a257f97637b1

Even the AWS Code provided by them for both javascript and python derived the same values and calculates the same hash as I received.

However, according to the documentation in their doc's, it should be:5d672d79c15b13162d9279b0855cfba6789a8edb4c82c400e06b5924a6f2b5d7

I have tried over 10+ calculators that all return the same value I received until I found 1 online calculator, only 1, that calculates the same as amazon at https://cryptii.com/hmac

I know HMAC is a mathematical function that is absolute, the same input will give the same output, which means that the input is different or that it is transformed along the way in a way that is abstracted from me.

Any tips?