boost/hash2
2
0
Fork 0
mirror of https://github.com/boostorg/hash2.git synced 2026-01-19 04:12:12 +00:00
Code Issues Projects Releases Wiki Activity

Merge pull request #42 from striezel-stash/fix-typos

Browse Source 
Fix two typos
This commit is contained in:
Peter Dimov
2025-05-05 17:50:08 +03:00
committed by GitHub
parent 98eee3d263 d6105b2a34
commit 9a59f06db3
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
doc/hash2/hashing_bytes.adoc
View File

@@ -314,7 +314,7 @@ a digest of 256 bits.
BLAKE2 is also designed explicitly with keyed hashing in mind, making it functionally equivalent to a Message Authentication Code (MAC). The seeded constructors act as the
keys, BLAKE2b using a maximum of the first 64 bytes of input as the key and BLAKE2s using a maximum of the first 32 bytes. Excess input is handled by passing it to the `update()` function
and then `result()` is called. HMAC typedefs are still provided for convenience and for compatiblity with existing protocols such as https://noiseprotocol.org/noise.html[Noise]. BLAKE2
and then `result()` is called. HMAC typedefs are still provided for convenience and for compatibility with existing protocols such as https://noiseprotocol.org/noise.html[Noise]. BLAKE2
behaves as all other cryptographic hash functions do when used with `hmac<H>`.
### RIPEMD-160, RIPEMD-128

2
doc/hash2/reference/sha3.adoc
View File

@@ -39,7 +39,7 @@ The only differences between them are the size of the message digest and the siz
which is by truncating the bottom portion of the 1600-bit state.
The `shake_128` and `shake_256` functions are similar to the fixed-digest functions except they use a different delimiter to denote finalization of the
digest and extending the output has defined behavior, unlike the default pseudorandom behavior used elsewhere in the library. But they work similary
digest and extending the output has defined behavior, unlike the default pseudorandom behavior used elsewhere in the library. But they work similarly
in that truncations of the 1600-bit state are returned as the digest.
## sha3_256