wireguard-openbsd/libexec/spamd/sync.h, branch jd/histogramWireGuard implementation for the OpenBSD kernelhttps://git.zx2c4.com/wireguard-openbsd/atom/libexec/spamd/sync.h?h=jd%2Fhistogram2008-05-22T19:54:11Zversion 2 of spamd sync protocol for two reasons:2008-05-22T19:54:11Zderaadtderaadt@openbsd.org2008-05-22T19:54:11Zurn:sha1:d72b910d458fb59eabd9ac259300a284a7483d5f
1) ip addresses were accidentally being sent in host-byte order, which
caused compatibility problems (spotted by jbg)
2) the sub-headers in the frame were not natively aligned, thus timeout
values were incorrectly sent by 64-bit machines
ok beck
As was done in dhcpd, insert pad blocks after sub-messages to keep the2008-05-09T07:09:17Zderaadtderaadt@openbsd.org2008-05-09T07:09:17Zurn:sha1:4aba4ff9a65bf5ef59be7df57da4de5c6d640729
structures aligned to 16 byte boundaries for maximum portability
(somewhat similar to CMSG's). Old spamd's and new spamd's can still
communicate with this change. It would be nice if someone tested spamd
on 64-bit unaligned architectures (with and without this change)
ok beck
Database synchronizaton for spamd/spamlogd2007-03-04T03:19:41Zbeckbeck@openbsd.org2007-03-04T03:19:41Zurn:sha1:98babcad66c249fea6b5d43e49c6cf1927a97ae9
This adds an HMAC protected synchronization protocol for use by spamd and
spamlogd.
- spamd can receive updates from other hosts for GREY, WHITE, and TRAPPED db
entries, and will update the local /var/db/spamd accordingly.
- spamd can send updates when it makes changes to the GREY or TRAPPED
entries in the db to other hosts running spamd. (Note it does not send
WHITE entries because the other spamd will see the GREY changes and have
complete information to make appropritate decisions)
- spamlogd can send updates for WHITE db entries that it performs on the local
db to other hosts running spamd, which will then apply them on remote hosts.
note that while this diff provides synchronization for changes made to the
spamd db by the daemons, it does *not* provide for sychonizing changes
to the spamd db made manually with the spamdb command.
Synchronization protocol and most of the work by reyk@,
with a bunch of the spamd, and spamlogd stuff by me.
testing mostly at the U of A, running happily there under big load.
ok reyk@ jmc@