From owner-freebsd-current Fri Apr 19 18:22: 5 2002 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id 1A5BD37B419 for ; Fri, 19 Apr 2002 18:22:01 -0700 (PDT) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.2/8.12.2) with ESMTP id g3K1LliJ066610 for ; Sat, 20 Apr 2002 05:21:50 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.3/8.12.2/Submit) id g3K1Lk6A066609 for current@freebsd.org; Sat, 20 Apr 2002 05:21:46 +0400 (MSD) Date: Sat, 20 Apr 2002 05:21:42 +0400 From: "Andrey A. Chernov" To: current@freebsd.org Subject: SSH: LOGIN_CAP limits & ~/.login.conf not processed now Message-ID: <20020420012140.GA66589@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Well, who damages LOGIN_CAP processing in sshd now? It not reads ~/.login_conf anymore and not sets LOGIN_CAP limits. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message