Clarify ambigious check wrt return codes

This commit is contained in:
Joost Rijneveld 2019-02-28 16:36:45 +01:00
джерело 66f0ba9d95
коміт ed8e845f77
Не вдалося знайти GPG ключ що відповідає даному підпису
Ідентифікатор GPG ключа: A4FE39CF49CBC553

@ -44,9 +44,7 @@ _The checking of items on this list is still being developed. Checked items shou
* [x] `sha2.c`
* [ ] `aes.c`
* [x] `randombytes.c`
* [ ] API functions return `0` on success, negative on failure
* [x] 0 on success
* [ ] Negative on failure (within restrictions of FO transform).
* [x] API functions return `0` on success
* [x] No dynamic memory allocations
* [ ] No branching on secret data (dynamically checked using valgrind)
* [ ] No access to secret memory locations (dynamically checked using valgrind)