1
0
mirror of https://github.com/ilyakooo0/urbit.git synced 2024-12-27 08:52:10 +03:00
An operating function
Go to file
2019-01-16 17:28:53 -08:00
include Simplify 2019-01-02 10:07:03 -08:00
src Add all config vars to config.h.in 2019-01-16 17:23:10 -08:00
.gitignore blargh fighting with meson 2018-12-27 10:27:28 -08:00
LICENSE Simplify 2019-01-02 10:07:03 -08:00
meson_options.txt Simplify 2019-01-02 10:07:03 -08:00
meson.build v0.1.4 2019-01-16 17:28:53 -08:00
README.md Update README.md 2019-01-02 12:57:37 -08:00
sample.c Simplify 2019-01-02 10:07:03 -08:00

libent is a cross-platform wrapper around getentropy(2). It exports one symbol, ent_getentropy. If getentropy is available, then it's just a shim around that. Otherwise, it uses getrandom(2) (available since kernel 3.17) on Linux, or /dev/urandom on other *nix.

Building

It uses meson. meson ./build && ninja -C build should do the trick.

Build options

It has one option, ent_compat, which tells it to be conservative. On Linux, this means using getrandom directly; on other *nix, it means reading from /dev/urandom. This may make sense if you want your binaries to run on older versions of the same OS. If your program is mostly built from source, don't bother.

Why?

getentropy is the wave of the future. It's the correct API for generating small amounts of entropy to create cryptographic keys or seed PRNGs. It's good and reasonable and true, it's on Linux, *BSD, and OS X, and it only took us fifty years of UNIX to get here.

Sadly, it only just arrived, so nobody has it yet. It didn't land in Linux until glibc 2.25, which seems to only have made it into Debian 10.

Once getentropy is everywhere you care about, you can just do a s/ent_//g on all the call sites and discard this shim.

This project began because Urbit's entropy-generation function was bothering me. Then it got out of hand.

References