From owner-freebsd-isp Sun Dec 29 18:45:08 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA26477 for isp-outgoing; Sun, 29 Dec 1996 18:45:08 -0800 (PST) Received: from smtest.usit.net (smtest.usit.net [199.1.48.16]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA26466 for ; Sun, 29 Dec 1996 18:45:06 -0800 (PST) Received: from use.usit.net (use.usit.net [199.1.48.3]) by smtest.usit.net (8.7.5/8.6.12) with SMTP id VAA25808 for ; Sun, 29 Dec 1996 21:53:15 -0500 (EST) Date: Sun, 29 Dec 1996 21:44:34 -0500 (EST) From: "Troy W. Settle" To: FreeBSD-isp mailing list Subject: network configuration Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hey all, I needs some advice. I've got 3 machines, all running 2.1.6: prime, radford, and gizmo prime is the big boy, where I'd like to run ftp, httpd, samba, mail, as well as backup for named and radius. No user shell access. gizmo will be primary server for radiusd and named, as well as a backup mail exchanger, there will be no user shell access. radford will be availiable for my users, as a shell server, and user web server. Currently, the plan is to keep /home on prime, and use nfs to mount it on radford. All 3 machines will need to be able to authenticate users, and 2 of them will need to keep track of each user's $HOME What's the best way to go about doing this? I really don't think that manually updating /etc/passwd is an option, as it would have to be done after every time a user changes his password. There's lots of options, I'm wondering which offers the best security for the convenience, and which is easiest to install. Also, how do I restrict shell access to just the one machine? Thanks in advanced for any info you can offer, Troy