From owner-freebsd-security Sun Nov 21 9:28:19 1999 Delivered-To: freebsd-security@freebsd.org Received: from funky.monkey.org (funky.monkey.org [63.77.239.12]) by hub.freebsd.org (Postfix) with ESMTP id A716E14D34 for ; Sun, 21 Nov 1999 09:28:10 -0800 (PST) (envelope-from dugsong@monkey.org) Received: by funky.monkey.org (Postfix, from userid 1001) id 7349A15188; Sun, 21 Nov 1999 12:24:27 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by funky.monkey.org (Postfix) with ESMTP id 5CFC814A01; Sun, 21 Nov 1999 12:24:27 -0500 (EST) Date: Sun, 21 Nov 1999 12:24:27 -0500 (EST) From: Dug Song To: Tomaz Borstnar Cc: freebsd-security@freebsd.org Subject: Re: OpenSSH & AllowHosts In-Reply-To: <4.2.2.19991121180438.021c3840@193.189.189.100> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 21 Nov 1999, Tomaz Borstnar wrote: > OpenSSH is nice, works fine, but I miss AllowHosts feature. actually, AllowHosts/DenyHosts was specifically removed in favor of tcp-wrappers LIBWRAP support, which provides a more standard interface for access control. see hosts_access(5) for details. > I know it can be done via packet filtering, but 100% compatibility > with usual ssh would be nice. Anyone knows if this will be added? OpenSSH intentionally deviates from the original SSH in many ways - see http://violet.ibs.com.au/openssh/files/UPGRADING for a brief summary. -d. --- http://www.monkey.org/~dugsong/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message