Bug#612752: Bind fails to start if $OPENSSL_CONF is set

2011-02-26 Thread Olaf van der Spek
On Fri, Feb 25, 2011 at 9:55 AM, Peter Palfrader wea...@debian.org wrote: We should probably start a campaign in Debian to have all init scripts sanitize the environment of daemons they start. I usually run initscripts using env -i /etc/init.d/$foo start to achieve exactly that, but ideally

Bug#612752: Bind fails to start if $OPENSSL_CONF is set

2011-02-25 Thread Peter Palfrader
On Thu, 10 Feb 2011, Ben Hutchings wrote: Package: bind9 Version: 1:9.7.2.dfsg.P3-1.1 I'm not sure whether this is a bug or my own configuration error. In interactive shells, I set $OPENSSL_CONF to point to the configuration file for my local CA. BIND should not use this, and indeed does

Bug#612752: Bind fails to start if $OPENSSL_CONF is set

2011-02-25 Thread Timo Weingärtner
Am Freitag, 25. Februar 2011 schrieb Peter Palfrader: On Thu, 10 Feb 2011, Ben Hutchings wrote: Package: bind9 Version: 1:9.7.2.dfsg.P3-1.1 I'm not sure whether this is a bug or my own configuration error. In interactive shells, I set $OPENSSL_CONF to point to the configuration

Bug#612752: Bind fails to start if $OPENSSL_CONF is set

2011-02-25 Thread Don Armstrong
On Fri, 25 Feb 2011, Peter Palfrader wrote: Maybe start-stop-daemon should have an option to delete all but a specified set of environment variables, maybe even enabled by default. The problem is in cases where you actually want to pass environmental variables to the daemon from within the

Bug#612752: Bind fails to start if $OPENSSL_CONF is set

2011-02-25 Thread Don Armstrong
On Fri, 25 Feb 2011, Don Armstrong wrote: On Fri, 25 Feb 2011, Peter Palfrader wrote: Maybe start-stop-daemon should have an option to delete all but a specified set of environment variables, maybe even enabled by default. The problem is in cases where you actually want to pass