From owner-freebsd-hackers Sun Jun 1 16:13:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA12736 for hackers-outgoing; Sun, 1 Jun 1997 16:13:06 -0700 (PDT) Received: from labs.usn.blaze.net.au (labs.usn.blaze.net.au [203.17.53.30]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA12729 for ; Sun, 1 Jun 1997 16:12:59 -0700 (PDT) Received: from labs.usn.blaze.net.au (local [127.0.0.1]) by labs.usn.blaze.net.au (8.8.5/8.8.5) with ESMTP id JAA02089 for ; Mon, 2 Jun 1997 09:13:10 +1000 (EST) Message-Id: <199706012313.JAA02089@labs.usn.blaze.net.au> X-Mailer: exmh version 2.0gamma 1/27/96 To: hackers@FreeBSD.ORG Subject: Re: uucp uid's In-reply-to: Your message of "Sat, 31 May 1997 09:07:33 +0200." <19970531090733.HH04622@uriah.heep.sax.de> X-Face: (W@z~5kg?"+5?!2kHP)+l369.~a@oTl^8l87|/s8"EH?Uk~P#N+Ec~Z&@;'LL!;3?y Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 02 Jun 1997 09:13:07 +1000 From: David Nugent Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > think Taylor's possibility to limit a particular system name to a > distinct account, too (though i've never been using this). I do. :) I don't particularly like the idea of granting permissions to the local filesystem based on the remote system name while letting any uucp dialin identify themselves as any system they like. If all uucp clients shared the same access, then I'd be less inclined to be as strict, but the only reason I'd still keep this setup is to prevent one client from stealing another's mail. Regards, David David Nugent - Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/