From owner-freebsd-security@FreeBSD.ORG Fri Oct 8 10:22:55 2004 Return-Path: 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 466CE16A4CE for ; Fri, 8 Oct 2004 10:22:55 +0000 (GMT) Received: from highland.isltd.insignia.com (highland.isltd.insignia.com [195.74.141.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9553643D1D for ; Fri, 8 Oct 2004 10:22:54 +0000 (GMT) (envelope-from subscriber@insignia.com) Received: from dailuaine.isltd.insignia.com (dailuaine.isltd.insignia.com [172.16.64.11])i98AMr00018059 for ; Fri, 8 Oct 2004 11:22:53 +0100 (BST) (envelope-from subscriber@insignia.com) Received: from speyburn.isltd.insignia.com (speyburn [172.16.64.16]) i98AMrgF006991 for ; Fri, 8 Oct 2004 11:22:53 +0100 (BST) (envelope-from subscriber@insignia.com) From: Jim Hatfield To: freebsd-security@freebsd.org Date: Fri, 08 Oct 2004 11:22:53 +0100 Organization: Insignia Solutions Message-ID: References: <3203DF3DDE57D411AFF4009027B8C36760563C@exchange-uk.isltd.insignia.com> In-Reply-To: <3203DF3DDE57D411AFF4009027B8C36760563C@exchange-uk.isltd.insignia.com> X-Mailer: Forte Agent 2.0/32.640 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Scanned-By: MIMEDefang 2.44 Subject: Re: Question restricting ssh access for some users only X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Security issues [members-only posting] List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Oct 2004 10:22:55 -0000 On Thu, 7 Oct 2004 21:14:07 +0100 , in local.freebsd.security you wrote: >Jim Hatfield wrote: >> Now I want to create a new account on one machine which will be >> accessible from the Internet as a whole, to be used for tunnelling of >> SMTP and POP3. I can't predict what the client IP address will be so I >> will have to remove the hosts.allow restriction. Is there any way I >> can: > >have you tried using /etc/login.access? I didn't know about this - thanks. In fact thanks to everyone for the many helpful replies, I have lots of solutions to choose from now! Jim