A one-line comment in "Security requirements", or even an option to read from /dev/random, may be a good idea.
Good point. I'm used to FreeBSD, where /dev/urandom and /dev/random are the same device.
you should probably #include <string.h> in lib/events/events_network.c for memset() as used in FD_ZERO
POSIX says that <sys/select.h> is all you need.
OpenBSD has no -lrt either, so I just removed that.
POSIX says that -lrt must work (having a librt isn't required, but if you don't have one the compiler must ignore -lrt).
Hopefully these will either get fixed in OpenBSD or as patches in ports/security/spiped if someone decides to add spiped to the OpenBSD ports tree.
Re:The spiped secure pipe daemon
by tedunangst on Monday July 04, 2011 @04:09PM
(#2727702)
Thanks for pointing these things out. We can probably fix it.
A one-line comment in "Security requirements", or even an option to read from /dev/random, may be a good idea.
I tried compiling it on OpenBSD; you should probably #include <string.h> in lib/events/events_network.c for memset() as used in FD_ZERO (see OpenBSD select(2)). OpenBSD has no -lrt either, so I just removed that. It compiles and passes a quick localhost test with these changes.