| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| configure-logging.patch | Tweak log destination and loglevel in ulogd.conf.in Send logging for ulogd itself to syslog rather than to file (not for iptables logging), and explicitly set loglevel to info. |
Chris Boot <bootc@debian.org> | not-needed | 2013-04-27 | ||
| enable-nflog-by-default.patch | Enable NFLOG => LOGEMU stack by default The simplest and likely most common usage scenario is to log packets to a logfile using NFLOG, bypassing the kernel ringbuffer. Enable this by default. |
Chris Boot <bootc@debian.org> | not-needed | 2013-04-27 | ||
| put-logfiles-in-var-log-ulog.patch | Update logfile paths to log to /var/log/ulog/* The standard configuration file sends logs to a number of files under /var/log/. To keep things tidy, including the logrotate script, move all the logs into a common parent directory. |
Chris Boot <bootc@debian.org> | not-needed | 2013-04-27 | ||
| ulogd8-ulogd2.patch | Correct ulogd(8) paths to /usr/share/doc/ulogd2 The paths in the ulogd(8) man page assume the package is called 'ulogd' and not 'ulogd2'. This patch updates the paths. |
Chris Boot <bootc@debian.org> | not-needed | 2013-11-14 | ||
| libpq-fall-back-fix.patch | in setting `libpq_CFLAGS` what we get from pg_config is the include-directory. This is in contrast the mysql_config and pcap_config. Therefore, the `-I` option needs to be added explicitly. |
Jeremy Sowden <jeremy@azazel.net> | yes | debian | 2022-12-11 | |
| simplify-opening-of-pcap-output-file.patch | simplify opening of pcap output file . Instead of statting the file, and choosing the mode with which to open it and whether to write the PCAP header based on the result, always open it with mode "a" and _then_ stat it. This simplifies the flow-control and avoids a race between statting and opening. |
Jeremy Sowden <jeremy@azazel.net> | yes | 2023-06-25 | ||
| pcap-null-outfile-fix.patch | prevent crashes when output `FILE *` is null . If ulogd2 receives a signal it will attempt to re-open the pcap output file. If this fails (because the permissions or ownership have changed for example), the FILE pointer will be null and when the next packet comes in, the null pointer will be passed to fwrite and ulogd will crash. . Instead, assign the return value of `fopen` to a local variable, and only close the existing stream if `fopen` succeeded. |
Jeremy Sowden <jeremy@azazel.net> | yes | 2023-06-25 |