From owner-freebsd-security Fri Aug 16 7:53:42 2002 Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E108337B400; Fri, 16 Aug 2002 07:53:39 -0700 (PDT) Received: from obsidian.sentex.ca (obsidian.sentex.ca [64.7.128.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4316843E70; Fri, 16 Aug 2002 07:53:39 -0700 (PDT) (envelope-from mike@sentex.net) Received: from simian.sentex.net (pyroxene.sentex.ca [199.212.134.18]) by obsidian.sentex.ca (8.12.5/8.12.5) with ESMTP id g7GErbCo087954; Fri, 16 Aug 2002 10:53:37 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <5.1.1.6.0.20020816104955.03cdcc98@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Fri, 16 Aug 2002 10:53:52 -0400 To: stable@freebsd.org From: Mike Tancsa Subject: login.access no longer works with default sshd Cc: security@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: By Sentex Communications (obsidian/20020220) Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I noticed that /etc/login.access is no longer consulted with sshd by default. Are there any dangers/caveats of turning on UseLogin yes ? As the default behavior has changed, perhaps a note in UPDATING ? I am cross posting as I think this issue is relevant to both lists. ---Mike -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet since 1994 www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message