Releases: pi-hole/FTL
FTL v2.3.1
Bugfix release
- Increase maximum length of parsed lines in
setupVars.conf
to 100000 (fixes pi-hole/web#471) - Correct computation of blocked percentage in statistics (fixes issue reported in Discourse)
FTL v2.3
FTL v2.2
This release contains a lot of improvements in terms of invalid memory access detection. We add a new access validation subroutine that checks for out-of-bounds accesses of the struct data structure before accessing the data. Also, we add a magic byte comparison to possibly detect if things get still written to places where they should not be. Also, we increase the verbosity of FTL
's log output when running in debug
mode.
FTL v2.1
New
- Don't use PID file for detection of another
pihole-FTL
process is running. Instead, access/proc
sub-system and try to find other runningpihole-FTL
binaries. If we find them we try to kill them by sendingSIGTERM
d37cdfb - Try to detect who is sending
SIGTERM
/SIGINT
signals 1de8fc4
Tweaks
- Parse time stamp earlier so that it is included in debug output of queries struct re-allocation b8f0e2f
- Don't compute log of zero 992f16b
- Resize structs one counter value earlier (just to not access the last portion of allocated memory) 6da22c1
Bugfixes
- No explicit bug fixes, however a fix for the
service
file is pending: pi-hole/pi-hole#1379
FTL v2.0
FTL v1.11.1
-
Allow re-binding to the used port in case FTL is restarted in short intervals. This is common practice in server programs
-
Improve several log messages
-
Log to
/var/log/syslog
for critical errors (usually write/read permission issues), e.g.
pi@raspberrypi:~ $ sudo tail -n2 /var/log/syslog
Apr 8 22:21:05 raspberrypi pihole-FTL: WARNING: Writing to FTL's log file failed!
FTL v1.11
FTL v1.10.3
- Don't try to obtain process group if PID cannot be read
FTL v1.10.2
- Increase verbosity
- Don't exit if PID file is empty
FTL v1.10.1
Log warning if pihole-FTL
is called directly (not through systemctl
/ service
) but don't force exit.