Search the archives!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[linux-security] Re: Problem with TCP_wrappers
- From: Chris Evans <chris@xxxxxxxxxxxxxxxxxxx>
- Subject: [linux-security] Re: Problem with TCP_wrappers
- Date: Thu, 6 Aug 1998 11:55:21 +0100 (GMT)
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
- References:
- [linux-security] Re: Problem with TCP_wrappers
- From: Wietse Venema
- [linux-security] Re: Problem with TCP_wrappers
- Prev by Date: "mailbox vulnerable" messages
- Next by Date: [linux-security] Re: IP Security for Linux (IPSec)
- Previous by thread: [linux-security] Re: Problem with TCP_wrappers
- Next by thread: [linux-security] Re: Problem with TCP_wrappers
- Index(es):