bug in dojox/encoding/digests/SHA256,SHA512, _hmac result is incorrect.

[swaron]

the bug is relative to sha256,sha224,sha384,sha512. in version 1.9.2. take sha256._hmac for example:

here is the last part of /dojox/encoding/digests/SHA256.js

make the final digest var r1 = sha32.digest(ipad.concat(sha32.toWord(data)), 512 + data.length * 8, hash, 256);

swaron: 512 + 160 is incorrect, because the length of sha256 is 256bit, should be 512+256, var r2 = sha32.digest(opad.concat(r1), 512 + 160, hash, 256);

swaron: the r2 should be return instead of wa. assign r2 to wa will fix it. wa = r2;

return the output. switch(out){

case sha32.outputTypes.Raw: {

return wa;

} case sha32.outputTypes.Hex: {

return sha32.toHex(wa);

} case sha32.outputTypes.String: {

return sha32._toString(wa);

} default: {

return sha32.toBase64(wa);

}

}

[Jason Cheatham]

I have also experienced this problem with SHA256, and I confirm that the provided fix appears to work - return r2 instead of wa and use 512 + 256 rather than 512 + 160 for the r2 input length.

Some comments might clear up where theses numbers come from. Assuming we're using the 32-bit version of the algorithm, 512 is ipad.length * 32 (and opad.length * 32), and 256 is r1.length * 32.

[Jason Cheatham]

​https://github.com/dojo/dojox/pull/132

[Colin Snover <[email protected]…>]

In f8273c955e892ec21fbe10322508ddb362051a60/dojox:

Error: Processor CommitTicketReference failed

Unsupported version control system "git": Can't find an appropriate component, maybe the corresponding plugin was not enabled? 

[Colin Snover <[email protected]…>]

In 22b4fd095c53bfef5644b2afeef823f4524af127/dojox:

Error: Processor CommitTicketReference failed

Unsupported version control system "git": Can't find an appropriate component, maybe the corresponding plugin was not enabled? 

[Colin Snover <[email protected]…>]

In d6cea8e80f1587c94b90b97b288a40e29c8a4dea/dojox:

Error: Processor CommitTicketReference failed

Unsupported version control system "git": Can't find an appropriate component, maybe the corresponding plugin was not enabled?