Hi,
this is the strings output:
root@maya:~# strings /usr/sbin/postfix-policyd | grep LOG
LOG_EMERG
LOG_ALERT
LOG_CRIT
LOG_ERR
LOG_WARNING
LOG_NOTICE
LOG_INFO
LOG_DEBUG
LOG_KERN
LOG_USER
LOG_MAIL
LOG_DAEMON
LOG_AUTH
LOG_SYSLOG
LOG_AUTHPRIV
LOG_LOCAL0
LOG_LOCAL1
LOG_LOCAL2
LOG_LOCAL3
LOG_LOCAL4
Thanks, found the bug.
Upstream uses strcpy in incompatible way (on overlapping buffer).
I'll upload a fixed version to unstable, but it won't get to stable
since it's not really a security issue.
O.
On Wed, Mar 23, 2011 at 10:39, Viridiana Sala v...@messagenet.it wrote:
Hi,
this is the
Thanks very much!
Viridiana
On Wed, 23 Mar 2011, Ondřej Surý wrote:
Thanks, found the bug.
Upstream uses strcpy in incompatible way (on overlapping buffer).
I'll upload a fixed version to unstable, but it won't get to stable
since it's not really a security issue.
O.
On Wed, Mar 23, 2011
Package: postfix-policyd
Version: 1.82-2+b1
Severity: minor
Postfix-policyd exits at startup with this error message:
fatal: didn't find priority 'LOG_IFOO', exiting
Changing SYSLOG_FACILITY from LOG_MAIL | LOG_INFO to LOG_MAIL | LOG_ERR (or
remove LOG_INFO) makes postfix-policyd start
Are you sure you didn't make a typo when specifying the facility? It
seems a very unlikely that the policyd would rewrite INFO to IFOO.
O.
On Tue, Mar 22, 2011 at 17:35, Viridiana Sala v...@messagenet.it wrote:
Package: postfix-policyd
Version: 1.82-2+b1
Severity: minor
Postfix-policyd
It seems very strange to me also, but there's no reference to a
LOG_IFOO' in my configuration files (and the same file works with the 32
bit of the software)
The only place where I can set the facility is in the configuration files,
and using LOG_MAIL | LOG_INFO (as in the shipped
Could you do:
$ strings usr/sbin/postfix-policyd | grep LOG
On the failing binary and send here the output?
Also if you can attach a strace output, it could be helpful.
O.
On Tue, Mar 22, 2011 at 18:14, Viridiana Sala v...@messagenet.it wrote:
It seems very strange to me also, but there's
7 matches
Mail list logo
