aboutsummaryrefslogtreecommitdiff
path: root/core/crypto/sha3
Commit message (Collapse)AuthorAgeFilesLines
* core/crypto/sha3: API cleanupYawning Angel2023-11-171-52/+60
| | | | - sha3.Sha3_Context -> sha3.Context
* core/crypto: Add more assertions to the low level APIYawning Angel2023-11-171-1/+1
| | | | | Assertions here are "fine" and it matches what the code that has the checks in init/update/final already does.
* core/crypto: Change hash asserts to panicsYawning Angel2023-11-171-17/+1
| | | | | | | | | | Assertions can be disabled, but at the point where cryptographic anything is involved, a single branch has an infinitesimally small performance impact. The correct thing to do is to punch the caller in the face if they do something that is blatantly incorrect, especially in a security critical setting.
* core/crypto/sha3: odinfmt (NFC)Yawning Angel2023-11-171-180/+192
|
* Just make the `io.Reader` etc aliasesgingerBill2023-06-081-4/+4
|
* Update to new io interfacegingerBill2023-06-081-4/+4
|
* Strip unneeded semicolonsgingerBill2022-01-251-4/+4
|
* Extended crypto API by variants that write the result into a destination ↵zhibog2021-12-311-36/+125
| | | | buffer, instead of returning it
* Removed context switching system from the crypto library to simplify the codezhibog2021-11-091-284/+127
|
* Remove the read_entire_file from the crypto utils and now use the one within ↵zhibog2021-10-161-5/+4
| | | | core:os
* Improved API. hash_file procs now just take a file handle instead of a pathzhibog2021-10-151-52/+41
|
* Add crypto library. Additional information is included in the README.mdzhibog2021-10-141-0/+440