Bash Bug Report
Configuration Information [Automatically generated, do not change]:Machine:
x86_64OS: linux-gnuCompiler: gccCompilation CFLAGS: -DPROGRAM='bash'
-DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu'
-DCONF_MACHTYPE='x86_64-pc-linux-gnu' -DCONF_VENDOR='p$uname output: Linux
LFS-BUI
Not a bug.
This is a well known issue with restricted mode. You as a sysadmin must provide
a very restricted PATH that contains only secure programs. For example, you
have to avoid: GNU sed, nvi, vim, ed, emacs, ...
Perhaps this *should* be documented under RESTRICTED SHELL in the bash manual.
-
On Sat, Apr 4, 2015 at 8:22 AM, David Bonner wrote:
> Bash Bug Report
>
> Configuration Information [Automatically generated, do not change]:
> Machine: x86_64
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
> -DCONF_OSTYPE='linux-gnu' -DCONF_MACHT
David Bonner writes:
> Repeat-By:1:Open a restricted shell2:Test with 'cd ..'
> 3:Use 'chroot / bash'4:Test that you are no longer restricted with
> 'chroot / bash'
You can even call bash directly. Go figure!
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
