Comments in the shipped AppArmor profile state that fwknopd is assumed to be built with 'localstatedir=/var', which is misleading for several reasons: * AppArmor profile assumes that fwknopd's pidfile and digest cache are under /run/fwknop by the looks of it, i.e. 'localstatedir' is '/run'. * By default these files are placed under /var/run/fwknop. Thus this profile implicitly relies on the existence of '/var/run -> /run' symlink and won't work otherwise when 'localstatedir' is '/var' Since GitHub PR#152 was merged, 'localstatedir' can be simply set to '/run' for AppArmor users to avoid this confusion. This changeset does it. If anyone had it working before, they should have it working now as the shipped AppArmor profile required /run existence before as well.
…hreads for libfiu support)
…cting this in source files
This fix was submitted by Raybuntu through github.
…knop with args that AppArmor expects
…ode to the no-pw homedir
…ontributed an fwknop-2.0.4 OpenBSD port
This change allows fwknopd to write syslog messages to traditional syslog files while running under upstart. Not forking into the background resulted in messages meant for syslog were captured under /var/log/upstart/fwknop.log.
For the upstart config make sure only start fwknopd after a non-loopback network interface is brought up. Also added a commented post-start script to send an email whenever fwknopd is (re)started.
(Vlad Glagolev) Submitted an OpenBSD port for fwknop-2.0.3, and this has been checked in under extras/openbsd/.
The myip.c file is deployed at http://www.cipherdyne.org/cgi-bin/myip for fwknop client IP resolution.