At least on Linux, openntpd is unreliable - it might be secure but it fails to keep time properly unless it follows exactly one source or all sources agree perfectly (so I would assume it would equally fail on OpenBSD as well)
ntpd is indeed horrible; but chrony is the bees knees from both functionality and security standpoints - openbsd would do well to move to it.
"Size of stripped daemon binary in default configuration on Linux x86-64"
chrony: 210 KB
openntpd: 87 KB
I admit to feeling a little amusement at the complete horror expressed by timekeeping geeks when they discover how openntpd handles leap seconds. It doesn't and the developers don't care. The time just slews to the new time at no particular rate. Openntpd ends up being a political protest against the insanity of leap seconds...
At least on Linux, openntpd is unreliable - it might be secure but it fails to keep time properly unless it follows exactly one source or all sources agree perfectly (so I would assume it would equally fail on OpenBSD as well)
ntpd is indeed horrible; but chrony is the bees knees from both functionality and security standpoints - openbsd would do well to move to it.