[英]File hash (Crypto-JS): same result in Chrome & Firefox / different result in Safari
I'm trying to make a hash of a file, through Crypto-JS
. 我正在尝试通过Crypto-JS
对文件进行哈希处理。
The idea is to make a hash of the first bytes (ie from 10
to 100
). 这个想法是对第一个字节进行哈希处理(即从10
到100
)。
The result is not the same in Safari (last), as in Chrome & Firefox (both last): any idea about what's wrong in Safari? 结果在Safari(最后)中的结果与在Chrome和Firefox(两者均在最后)中的结果不同:关于Safari中出了什么问题的任何想法?
Hash function 哈希函数
const hashthefile = (filetoHash) => {
return new Promise((resolve, reject) => {
var start = 10;
var stop = 100;
// set reading operations through the FileReader API
var reader = new FileReader();
reader.onloadend = function(event) {
// when the entire read request has been completed
if (event.target.readyState == FileReader.DONE) {
var data = event.target.result;
var encrypted = CryptoJS.SHA256(data).toString();
resolve(encrypted);
}
}
// handle error
reader.onerror = function(event) {
reject('reading error')
};
// slice the file according to first and last bytes defined
// complete API there: https://developer.mozilla.org/en-US/docs/Web/API/Blob/slice
var blob = filetoHash.slice(start, stop + 2);
// launch the file sliced reading as a base64 encoded string
reader.readAsDataURL(blob);
});
}
I think I figure out how to have a consistent hash across Chrome, Firefox & Safari : 我想我想出了如何在Chrome,Firefox 和Safari之间保持一致的哈希值:
readAsDataURL
而不是readAsDataURL
readAsArrayBuffer
使用readAsArrayBuffer
Open to more advices and precisions of wiser coders (still don't know why using readAsDataURL
produce a Safari-specific result). 对明智的编码器提出更多建议和精确度(仍然不知道为什么使用readAsDataURL
产生特定于Safari的结果)。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.