From owner-freebsd-bugs Tue Jun 8 5:10: 5 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 8D82C14BD3 for ; Tue, 8 Jun 1999 05:10:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id FAA35408; Tue, 8 Jun 1999 05:10:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Tue, 8 Jun 1999 05:10:03 -0700 (PDT) Message-Id: <199906081210.FAA35408@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: David Malone Subject: Re: bin/11960: inetd built in wrapping doesn't log like tcpd does. Reply-To: David Malone Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/11960; it has been noted by GNATS. From: David Malone To: Sheldon Hearn Cc: freebsd-gnats-submit@freebsd.org Subject: Re: bin/11960: inetd built in wrapping doesn't log like tcpd does. Date: Tue, 08 Jun 1999 13:07:49 +0100 > The code as it stands sets the severities once. You're proposing to set > the severities every time hosts_access() is called, but always to the > same values that they were set to at the beginning. :-) > > Doesn't the tcp_wrappers library offer an interface for finding out what > severity a particular service likes to be reported with? Calling hosts_access is the only way of finding out, 'cos the severity might depend on any of the things on which tcp wrappers can match on. I think we need to reset them each time 'cos otherwise if we don't set the severity in /etc/hosts.allow for the current service we'll just get the last used severity. I think resetting each time is the correct behavior... David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message