From owner-freebsd-security Mon May 31 19:24:14 1999 Delivered-To: freebsd-security@freebsd.org Received: from mail.hamptons.com (mail.hamptons.com [204.141.112.204]) by hub.freebsd.org (Postfix) with ESMTP id 186DE14BC9 for ; Mon, 31 May 1999 19:24:01 -0700 (PDT) (envelope-from timothy@hamptons.com) Received: from [204.141.112.245] ([204.141.112.245]) by mail.hamptons.com with ESMTP (IPAD 2.06) id 5557000 ; Mon, 31 May 1999 21:15:08 EST Message-Id: In-Reply-To: <37534264.6D29110A@tdnet.com.br.> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 31 May 1999 22:24:04 -0500 To: freebsd-security@freebsd.org From: "Timothy R. Platt" Subject: Re: Shell Account system Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Install tripwire, it's in the ports. Better install a traffic logger, or better yet ipfw. You'll need them to log and report all the smurfs, fraggles, and synks you're going to get. Tim >Yeah, thanks, but the system is for anyone able to pay, so, you can say >i trust nobody. > >Kris Kennaway wrote: >> >> On Mon, 31 May 1999, Joe Gleason wrote: >> >> [Snip] >> >> Good advice, but running a shell account for people who you don't really >>trust >> is still not a wise move for the inexperienced, and not something you can >> easily document in a webpage. UNIX security is a way of life - there are any >> number of things which the unwary can trip over which could potentially >> compromise your machine. >> >> If it's for a small group of users who you trust fairly well, you >> probably should be okay, though. > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-security" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message