Project

General

Profile

Feature #10865

squidGuard lacks options to send traffic action logs to syslog server

Added by Kris Phillips about 2 months ago. Updated about 2 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
squidguard
Target version:
-
Start date:
09/04/2020
Due date:
% Done:

0%

Estimated time:

Description

squidGuard has options to send logs to squid's logs, but these don't seem to arrive at a syslog server and are only logged locally.

squidGuard has an option for "enable syslog" that can be added to the SquidGuard.conf file, but it's value is overwritten when any changes are made to the squidGuard config from the GUI.

It would be helpful if the logs sent to squid could be shuttled off via syslog messages or if squidGuard could send its logs directly.

History

#1 Updated by Jim Pingle about 2 months ago

  • Project changed from pfSense to pfSense Packages
  • Category set to squidguard

#2 Updated by Viktor Gurov about 2 months ago

This is supported only by squidGuard-1.5-beta, see https://fossies.org/linux/www/squidGuard-1.5-beta.tar.gz/squidGuard-1.5-beta/CHANGELOG:

2009-09-15     Added a feature to send log messages to syslog based on the
                    patch from Jun Jiang (thank you). (bug 42)  In order to use
                    syslog you have to run configure with the new option
                    "--with-syslog". In the configuration file you need to add
                    a line "syslog enable". If any other value but "enable" is
                    used syslog is disabled and logging to squidGuard.log takes
                    place as usual.
                    The following log level are used: DEBUG, NOTICE, WARN, ERROR
                    and EMERG. The local4 syslog facility is used by default.
                    If you want to change this, use the configure option
                    "--with-syslog-facility=<facility>".

but the current FreeBSD port version is 1.4_15: https://www.freshports.org/www/squidguard/

Also available in: Atom PDF