Log files opened before dropping privileges
Log files are opened while parsing the configuration file. This is to transition from logging to console stderr to the configured error log as soon as possible. Unfortunately the means that a newly created log file is owned by root rather than the configured user which causes the reload test to fail since the file is created owned and only writable by root, but during the reload the log file can not be reopened by the unprivileged user.
Additionally an attacker might be able to take advantage of this behavior in some deployment where the config file was writable by an unprivileged user to append to a file there were not otherwise authorized to by modifying the logging configuration and waiting for the sniproxy daemon to be restarted.
This has caused test failures when the test suite is run as root: see #251 and #256.