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 at 10:39, Viridiana Sala <v...@messagenet.it> wrote:
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
LOG_LOCAL5
LOG_LOCAL6
LOG_LOCAL7
SYSLOG_FACILITY=
I'm using the default configuration file.
TIA
Viridiana
On Tue, 22 Mar 2011, Ondřej Surý wrote:
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 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 configuration) will
cause
the error.
I can replicate the problem with a fresh installation of postfix-policyd,
installing it via apt-get on another system (it fails with the LOG_IFOO
error just after installation, using the default configuration file).
Viridiana
On Tue, 22 Mar 2011, Ondřej Surý wrote:
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 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 correctly
The 32 bit version of the same software seems not affected.
-- System Information:
Debian Release: 6.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-2-xen-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages postfix-policyd depends on:
ii dbconfig-common 1.8.46+squeeze.0 common framework for
packaging dat
ii debconf [debconf-2.0] 1.5.36.1 Debian configuration
management sy
ii libc6 2.11.2-10 Embedded GNU C Library:
Shared lib
ii libmysqlclient16 5.1.49-3 MySQL database client
library
ii mysql-client 5.1.49-3 MySQL database client
(metapackage
ii mysql-client-5.1 [mysql 5.1.49-3 MySQL database client
binaries
ii zlib1g 1:1.2.3.4.dfsg-3 compression library -
runtime
Versions of packages postfix-policyd recommends:
ii mysql-server 5.1.49-3 MySQL database server
(metapackage
ii mysql-server-5.1 [mysql-serve 5.1.49-3 MySQL database server
binaries and
postfix-policyd suggests no packages.
-- debconf information excluded
--
Ondřej Surý <ond...@sury.org>
---
Viridiana Sala
Messagenet srl
Messaggistica e Telecomunicazioni
Tel: +39 02 48102000
Fax: +39 02 48026819
--
Ondřej Surý <ond...@sury.org>
---
Viridiana Sala
Messagenet srl
Messaggistica e Telecomunicazioni
Tel: +39 02 48102000
Fax: +39 02 48026819
--
Ondřej Surý <ond...@sury.org>
---
Viridiana Sala
Messagenet srl
Messaggistica e Telecomunicazioni
Tel: +39 02 48102000
Fax: +39 02 48026819
