cheng/libsodium
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Explain that sodium_misuse() still aborts by default

Browse Source
This commit is contained in:
Frank Denis 2017-08-16 20:16:19 +02:00
parent 901c49203d
commit c654261477
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
ChangeLog
View File

@ -6,10 +6,11 @@
- Internal consistency checks failing and primitives used with
dangerous/out-of-bounds/invalid parameters used to call abort(3).
Now, a custom handler *that doesn't return* can be set with the
`set_sodium_misuse()` function. This is not a replacement for
non-fatal, expected runtime errors. This handler will be only
called in unexpected situations due to potential bugs in the
library or in language bindings.
`set_sodium_misuse()` function. It still aborts by default or if
the handler ever returns. This is not a replacement for non-fatal,
expected runtime errors. This handler will be only called in
unexpected situations due to potential bugs in the library or in
language bindings.
- `*_MESSAGEBYTES_MAX` macros (and the corresponding
`_messagebytes_max()` symbols) have been added to represent the
maximum message size that can be safely handled by a primitive.