WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/libexec/spamlogd/Makefile?h=jd%2Fsimplify-queueing 2019-07-25T14:53:21Z 2019-07-25T14:53:21Z brynet brynet@openbsd.org 2019-07-25T14:53:21Z urn:sha1:4053af6133ce1545a5e87acec29fae4cbe62e66a Add an internal version of pcap_open_live that ensures bpf(4) devices are opened read-only before locking. Neither pflogd(8) or spamlogd(8) require write access to bpf(4). Inspired by similar solution in OpenBSD tcpdump(8). pflogd(8) was safe since being unveiled last year, but spamlogd(8) was having /dev/bpf opened O_RDWR. Issue discovered by bluhm@'s unveil(2) accounting commit. ok deraadt@, mestre@ (thanks for testing spamlogd!) 2018-06-28T02:23:27Z gsoares gsoares@openbsd.org 2018-06-28T02:23:27Z urn:sha1:e88f0f1e5d17ee9b610eb62651aff392a239f2f6 OK deraadt@ millert@ jca@ 2013-08-21T16:13:29Z millert millert@openbsd.org 2013-08-21T16:13:29Z urn:sha1:51210d5c4143f40e4bb22955bd7f630657489cf1 with backwards compatibility for records with 32-bit times. OK deraadt@ beck@ 2007-03-04T03:19:41Z beck beck@openbsd.org 2007-03-04T03:19:41Z urn: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@ 2006-11-26T11:31:08Z deraadt deraadt@openbsd.org 2006-11-26T11:31:08Z urn:sha1:5c9d13eb7bde08d6011d72c074f54f401b96a9dd 2006-11-03T19:39:33Z henning henning@openbsd.org 2006-11-03T19:39:33Z urn:sha1:e106bcd2e02e2e611ed6ef1e574441a5a0c45795 joint work with Berk D. Demir, ok beck deraadt 2005-05-24T22:23:04Z millert millert@openbsd.org 2005-05-24T22:23:04Z urn:sha1:b051393d7dd4f18c8c5c2603032c4db6eb790c0c 2004-02-27T19:41:39Z david david@openbsd.org 2004-02-27T19:41:39Z urn:sha1:e76bcb56db36bc9c03184398a5200041d74f3487 ok deraadt@ 2004-02-26T07:28:54Z beck beck@openbsd.org 2004-02-26T07:28:54Z urn:sha1:1f68c1d423a18ba467ea103f8d8bc128a0f56830 originates from a paper by Evan Harris which can be found at http://projects.puremagic.com/greylisting/. This implementation makes spamd allow for non-blacklisted addresses to be treated as "greylisted". where they are tracked in a db file, and whitelisted by addition to a pf table when the same envelope from and to are retried from the same source IP address. Testing by many, ok deraadt@