aboutsummaryrefslogtreecommitdiff
path: root/core/crypto/rand_linux.odin
Commit message (Collapse)AuthorAgeFilesLines
* base/runtime: Add `rand_bytes` and `HAS_RAND_BYTES`Yawning Angel2025-11-291-40/+0
| | | | | | Having the OS/runtime provide a cryptographic entropy source is the right thing to do, and we need it to initialize the default random number generator.
* Replace `panic(fmt.tprintf(` antipattern with `fmt.panicf`gingerBill2024-06-111-1/+1
|
* core/crypto: Add a `HAS_RAND_BYTES` constantYawning Angel2024-04-231-4/+4
|
* Core Foundation and Security vendor libraries.Vitalii Kravchenko2024-04-131-1/+1
|
* core/crypto: Add `has_rand_bytes`Yawning Angel2024-04-091-0/+4
| | | | | This allows runtime detection as to if `rand_bytes` is supported or not, and lets us enable the test-case on all of the supported targets.
* Implement new sys/unix packageflysand72023-10-271-22/+21
|
* cleanup of os/linuxColin Davidson2023-02-281-1/+1
|
* crypto: Add rand_bytesYawning Angel2021-11-171-0/+37
This adds `rand_bytes(dst: []byte)` which fills the destination buffer with entropy from the cryptographic random number generator. This takes the "simple is best" approach and just directly returns the OS CSPRNG output instead of doing anything fancy (a la OpenBSD's arc4random).