From owner-freebsd-security Wed Jun 7 10: 2:40 2000 Delivered-To: freebsd-security@freebsd.org Received: from penchev.staff.orbitel.bg (ns.orbitel.bg [195.24.32.2]) by hub.freebsd.org (Postfix) with SMTP id 8BF7E37BD96 for ; Wed, 7 Jun 2000 10:02:32 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 33165 invoked from network); 7 Jun 2000 17:02:07 -0000 Received: from localhost.staff.orbitel.bg (HELO localhost) (127.0.0.1) by localhost.staff.orbitel.bg with SMTP; 7 Jun 2000 17:02:07 -0000 Date: Wed, 7 Jun 2000 20:02:07 +0300 (EEST) From: Peter Pentchev X-Sender: roam@ringwraith.oblivion.bg To: Frank Bonnet Cc: andrew@scoop.co.nz, fran@reyes.somos.net, freebsd-security@FreeBSD.ORG Subject: Re: Restricting user to a directory In-Reply-To: <200006071649.e57GnEg12368@bart.esiee.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org not really. bash should be configured at runtime as to whether to *allow* invocation as a restricted shell; most precompiled versions of bash come with this capability. From there, just start it as rbash or bash -r, and it runs restricted. G'luck, Peter On Wed, 7 Jun 2000, Frank Bonnet wrote: > > well it "seems" that bash should be configured as a restricted shell > at compile time > see at > http://dept-info.labri.u-bordeaux.fr/~strandh/Teaching/USI/Common/Bash/bashref_65.html > > -- > Frank Bonnet > Groupe ESIEE Paris > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message