Your message dated Thu, 03 Jan 2019 17:22:21 +0100
with message-id <[email protected]>
and subject line Closing bugs reported against unsupported versions
has caused the Debian Bug report #728349,
regarding Asterisk res_security_log.so module unable to catch security events
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
728349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728349
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: Asterisk
Version: 1:1.8.13.1~dfsg-3+

When I enable module res_security_log.so i should be able to enable
security logging in logger.conf.
Enabled security in logger.conf like this:
security => security

This should write all the security events to the logfile "security"

This catches nothing and no errors are reported when i load the module.

Debug info:
*CLI> logger show channels
Channel                             Type     Status    Configuration
-------                             ----     ------    -------------
/var/log/asterisk/full              File     Enabled    - DEBUG NOTICE
WARNING ERROR VERBOSE DTMF SECURITY
/var/log/asterisk/security          File     Enabled    - SECURITY
/var/log/asterisk/messages          File     Enabled    - NOTICE WARNING
ERROR
                                    Console  Enabled    - NOTICE WARNING
ERROR SECURITY

I'm using Debian Wheezy with all the latest package updates.

--- End Message ---
--- Begin Message ---
Dear user,

thanks for helping us making Debian better by reporting this bug. Unfortunately it could not be dealt with in time. We lack the manpower to check all currently open bugs whether they still apply for the current version. Therefor we are closing old issues hoping that the documented problem has already been resolved.

If you can still reproduce this issue with a supported version of Debian/Asterisk

- 13.14 in Debian Stretch
- 13.23.1 in Debian Buster/Sid (right now)
- 16.1.0 in Experimental (soon in buster/sid I hope)

please feel free to reopen this bug.

Thanks,
Bernhard

--- End Message ---

Reply via email to