From owner-freebsd-questions@FreeBSD.ORG  Thu Mar  3 05:42:54 2005
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id BBEDC16A4CE
	for <questions@freebsd.org>; Thu,  3 Mar 2005 05:42:54 +0000 (GMT)
Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.205])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 411E643D48
	for <questions@freebsd.org>; Thu,  3 Mar 2005 05:42:54 +0000 (GMT)
	(envelope-from linicks@gmail.com)
Received: by rproxy.gmail.com with SMTP id 34so272660rns
        for <questions@freebsd.org>; Wed, 02 Mar 2005 21:42:53 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
	s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
	b=oip2eydusQMDOqPEBy9r/5pKq9IZVK0XDPz0NwUadE2zHYDLxZ1JBvC9qExn2a5JhYIEI4L775PqVg53jDw6rp9mMiLTavCiBeZPoc09WL8rurVjaNyGJuHbsyot643jK/I9B0IV5rtZsCe5ksdcCSrR3Tl29TJy8RawHYcvK54=
Received: by 10.38.206.49 with SMTP id d49mr159036rng;
        Wed, 02 Mar 2005 21:42:53 -0800 (PST)
Received: by 10.38.8.69 with HTTP; Wed, 2 Mar 2005 21:42:53 -0800 (PST)
Message-ID: <dc9ba04405030221425d16d980@mail.gmail.com>
Date: Wed, 2 Mar 2005 22:42:53 -0700
From: Nick Pavlica <linicks@gmail.com>
To: Chris Hodgins <chodgins@cis.strath.ac.uk>
In-Reply-To: <4226657B.4090604@cis.strath.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <20050301122927.C1E464BDAA@ws1-1.us4.outblaze.com>
	 <42246D72.2020504@landgren.net>
	 <dc9ba0440503020901273e6357@mail.gmail.com>
	 <20050302183758.N25321@mail.rot-1.de>
	 <dc9ba04405030216171531c783@mail.gmail.com>
	 <422661DD.1010909@daleco.biz> <4226657B.4090604@cis.strath.ac.uk>
cc: Stevan Tiefert <stevan@rot-1.de>
cc: questions@freebsd.org
Subject: Re: Default security: other users can ACCESS MY HOMEDIR?!
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: Nick Pavlica <linicks@gmail.com>
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Mar 2005 05:42:54 -0000

I will have to give this a try, it sounds like it will do the trick. 
Thanks for the info!

--Nick



On Thu, 03 Mar 2005 01:16:43 +0000, Chris Hodgins
<chodgins@cis.strath.ac.uk> wrote:
> Kevin Kinsey wrote:
> > Nick Pavlica wrote:
> >
> >> I was thinking along the lines of a scp server that would only allow
> >> the user to browse only there directories.
> >>
> >>
> >> On Wed, 2 Mar 2005 18:39:43 +0100 (CET), Stevan Tiefert
> >> <stevan@rot-1.de> wrote:
> >>
> >>
> >>> On Wed, 2 Mar 2005, Nick Pavlica wrote:
> >>>
> >>>
> >>>
> >>>> How would you restrict regular users from accessing any part of the
> >>>> file system accept there home dirs?  Is this even possible?
> >>>>
> >>>>
> >>>
> >>> Hello Nick,
> >>>
> >>> it is possible but why? The user must be able to access their shells,
> >>> configurations and so on!
> >>>
> >>> With regards
> >>> Stevan Tiefert
> >>>
> >
> >
> > You might look at MAC (Chapter 15 of the handbook).  I don't
> > grok it yet, so I can't say if it's exactly what you need.  It could
> > be a lot more ...
> >
> > Kevin Kinsey
> > _______________________________________________
> > freebsd-questions@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > To unsubscribe, send any mail to
> > "freebsd-questions-unsubscribe@freebsd.org"
> >
> 
> Also have a look at this:
> http://www.securityfocus.com/infocus/1404
> 
> Chris
>