News for hackers. Stuff that matters.
Re:The spiped secure pipe daemon by cperciva on Monday July 04, 2011 @03:06PM (#2727476)
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.
Re:The spiped secure pipe daemon by cperciva on Monday July 04, 2011 @04:52PM (#2727833)
FWIW, Darwin also gets -lrt wrong, so you're not alone with that one. I was actually rather surprised when I found this stipulation.