History log of /openbsd/libexec/spamlogd/Makefile (Results 1 – 9 of 9)
Revision Date Author Comments
# 4053af61 25-Jul-2019 brynet <brynet@openbsd.org>

Yet another workaround for crappy libpcap API design

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)
requi

Yet another workaround for crappy libpcap API design

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!)

show more ...


# e88f0f1e 28-Jun-2018 gsoares <gsoares@openbsd.org>

add missing ${LIBCRYPTO} to DPADD
OK deraadt@ millert@ jca@


# 51210d5c 21-Aug-2013 millert <millert@openbsd.org>

Remove the use of time_t in the greylist db file and use int64_t instead
with backwards compatibility for records with 32-bit times.
OK deraadt@ beck@


# 98babcad 04-Mar-2007 beck <beck@openbsd.org>

Database synchronizaton for spamd/spamlogd

This adds an HMAC protected synchronization protocol for use by spamd and
spamlogd.

- spamd can receive updates from other hosts for GREY, WHITE, and TRAP

Database synchronizaton for spamd/spamlogd

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@

show more ...


# 5c9d13eb 26-Nov-2006 deraadt <deraadt@openbsd.org>

repair missing DPADD requests


# e106bcd2 03-Nov-2006 henning <henning@openbsd.org>

donot for tcpdump, use libpcap directly.
joint work with Berk D. Demir, ok beck deraadt


# b051393d 24-May-2005 millert <millert@openbsd.org>

Remove -ansi as that means expose only C89 interfaces.


# e76bcb56 27-Feb-2004 david <david@openbsd.org>

fix CFLAGS -I
ok deraadt@


# 1f68c1d4 26-Feb-2004 beck <beck@openbsd.org>

Add -g option for greylisting support for spamd. The greylisting techinque
originates from a paper by Evan Harris which can be found at
http://projects.puremagic.com/greylisting/. This implementation

Add -g option for greylisting support for spamd. The greylisting techinque
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@

show more ...