From owner-freebsd-hackers  Tue Dec  3 02:36:56 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id CAA24174
          for hackers-outgoing; Tue, 3 Dec 1996 02:36:56 -0800 (PST)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA24160
          for <hackers@freebsd.org>; Tue, 3 Dec 1996 02:36:54 -0800 (PST)
Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.3/8.6.9) with ESMTP id CAA05206; Tue, 3 Dec 1996 02:35:47 -0800 (PST)
To: "Serge A. Babkin" <babkin@hq.icb.chel.su>
cc: hackers@freebsd.org
Subject: Re: Does anybody need it ? 
In-reply-to: Your message of "Tue, 03 Dec 1996 13:12:12 +0500."
             <199612030812.NAA00839@hq.icb.chel.su> 
Date: Tue, 03 Dec 1996 02:35:47 -0800
Message-ID: <5202.849609347@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> The idea is to limit certain logins to be accessible from
> certain hosts only. So I added a database that describes allowed
> hosts, say /etc/userhost.conf, in format like:

This sounds a lot like the functionality already provided by
tcpwrappers, though these admittedly are not a default part of the
system.  Have you looked into this?

					Jordan