Differences From Artifact [43577ec262]:
- File
src/OFSHA384Or512Hash.m
— part of check-in
[951f530aee]
at
2016-07-24 00:06:30
on branch trunk
— Rename OFHash to OFCryptoHash
OFHash is too generic, as this protocol is for cryptographic hashes. It
also solves the ambiguity of the +[hash] method (which is now
+[cryptoHash]), which conflicted with -[hash] on the class itself,
resulting in classes conforming to OFHash not being able to be used as a
key in an OFDictionary. (user: js, size: 5670) [annotate] [blame] [check-ins using]
To Artifact [5c6c4dfe45]:
- File
src/OFSHA384Or512Hash.m
— part of check-in
[19f7dc67af]
at
2016-07-24 12:14:41
on branch trunk
— -[OFCryptoHash digest]: uint8_t -> unsigned char
While in practice they are usually the same, the C standard says that
only char does not have any alignment requirements. As (u)int*_t is
defined to be an integer type of the specified size, it does not mean
(u)int8_t needs to be char. (user: js, size: 5676) [annotate] [blame] [check-ins using]
︙ | ︙ | |||
184 185 186 187 188 189 190 | if (_bufferLength == 128) { processBlock(_state, _buffer.words); _bufferLength = 0; } } } | | | 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 | if (_bufferLength == 128) { processBlock(_state, _buffer.words); _bufferLength = 0; } } } - (const unsigned char*)digest { if (_calculated) return (const uint8_t*)_state; _buffer.bytes[_bufferLength] = 0x80; memset(_buffer.bytes + _bufferLength + 1, 0, 128 - _bufferLength - 1); |
︙ | ︙ |