From owner-freebsd-stable Tue Sep 19 19:53:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from hitpro.hitachi.co.jp (hitpro.hitachi.co.jp [133.145.224.7]) by hub.freebsd.org (Postfix) with ESMTP id E36CB37B43C for ; Tue, 19 Sep 2000 19:53:44 -0700 (PDT) Received: from bisdgw.bisd.hitachi.co.jp by hitpro.hitachi.co.jp (8.9.3/3.7W-hitpro) id LAA00860; Wed, 20 Sep 2000 11:53:20 +0900 (JST) Received: from plum.ssr.bisd.hitachi.co.jp by bisdgw.bisd.hitachi.co.jp (8.9.3+3.2W/3.7W-bisdgw) with ESMTP id LAA00914; Wed, 20 Sep 2000 11:53:20 +0900 (JST) (envelope-from ume@bisd.hitachi.co.jp) Received: from localhost (IDENT:GHE0hsZGxqJfNkmmK7qGJ5btb9dHFlx652X3QwX4iwCr1Jo1I0MtewbqXhwkpvHW@localhost [::1]) by plum.ssr.bisd.hitachi.co.jp (8.11.0/8.11.0/plum) with ESMTP/inet6 id e8K2rJ725319; Wed, 20 Sep 2000 11:53:19 +0900 (JST) (envelope-from ume@bisd.hitachi.co.jp) Message-Id: <200009200253.e8K2rJ725319@plum.ssr.bisd.hitachi.co.jp> To: holtor@yahoo.com Cc: stable@freebsd.org Subject: Re: inetd internel auth problem From: Hajimu UMEMOTO In-Reply-To: <20000920010725.4489.qmail@web108.yahoomail.com> References: <20000920010725.4489.qmail@web108.yahoomail.com> X-Mailer: xcite1.20> Mew version 1.94.2 on Emacs 20.6 / Mule 4.0 (HANANOEN) X-PGP-Fingerprint: D3 3D D3 54 88 13 DE 22 3F 31 C4 4D A1 08 84 7B X-PGP-Public-Key: http://www.imasy.org/~ume/ume@bisd.hitachi.co.jp.asc X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 4.1-RELEASE Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 20 Sep 2000 11:53:19 +0900 X-Dispatcher: imput version 20000414(IM141) Lines: 29 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> On Tue, 19 Sep 2000 18:07:24 -0700 (PDT) >>>>> holtor@yahoo.com (Holtor) said: holtor> After reading the posting I've switched my fbsd holtor> machines from pidentd to this internal auth. Since holtor> that I have noticed one [problem/bug/mistake]. holtor> It provides the username well, the problem comes in holtor> when I simply do: holtor> telnet localhost 113 holtor> And then quit the telnet. Then I run "top" and i see holtor> inetd using almost 100% CPU. It stays at full CPU holtor> util the connection "times out" which is the default holtor> of 10 seconds. holtor> I'm certain this can't be normal behavior. I've been holtor> able to reproduce this on every single fbsd machine holtor> I have. Are you using client username lookup feature of tcp_wrapper something like `ALL : ALL@ALL : allow'? If so, make sure to disable it for `auth'. Put `auth : ALL : allow' line before every rule in /etc/hosts.allow. -- Hajimu UMEMOTO @ Business Solution System Development Div., Hitachi Ltd. E-Mail: ume@bisd.hitachi.co.jp ume@mahoroba.org ume@FreeBSD.org URL: http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message