[2032] in linux-security and linux-alert archive
[linux-security] Re: Problem with TCP_wrappers
daemon@ATHENA.MIT.EDU (Chris Evans)
Thu Aug 6 07:35:45 1998
Date: Thu, 6 Aug 1998 11:55:21 +0100 (GMT)
From: Chris Evans <chris@ferret.lmh.ox.ac.uk>
To: Wietse Venema <wietse@porcupine.org>
cc: Jan Kasprzak <kas@informatics.muni.cz>, jpv@jvelders.tn.tudelft.nl,
linux-security@redhat.com
In-Reply-To: <19980805181441.458BFDA13E@spike.porcupine.org>
Resent-From: linux-security@redhat.com
Resent-Reply-To: linux-security@redhat.com
On Wed, 5 Aug 1998, Wietse Venema wrote:
> Jan Kasprzak:
> > the "setenv" keyword in the hosts.{allow,deny}. It simply does not
> > work for me. I have tried to use the "setenv" keyword for qmail's incoming
> > mail:
> >
> > tcp-env: ALL@.local.domain : setenv RELAYCLIENT
>
> In the HOSTS_OPTIONS(5) manual page, I wrote:
>
> setenv name value
> Place a (name, value) pair into the process envi-
> ronment. The value is subjected to %<letter> expan-
> sions and may contain whitespace (but leading and
> trailing blanks are stripped off).
Redhat-5.1 shipped a broken tcp_wrappers in which setenv does not work. We
discovered this the hard way when we upgraded 4.2->5.1.
RedHat released a rapid update when we traced our qmail problem to
tcp_wrappers. Get the tcp_wrappers update and you should be laughing.
Cheers
Chris
--
----------------------------------------------------------------------
Please refer to the information about this list as well as general
information about Linux security at http://www.aoy.com/Linux/Security.
----------------------------------------------------------------------
To unsubscribe:
mail -s unsubscribe linux-security-request@redhat.com < /dev/null
