On Fri, Dec 22, 2017 at 10:56:18AM -0800, Kevin Layer wrote:
> The man page says:
>
> The shell does not exit if the command that fails is part of the
> command list immediately following a while or until keyword,
> part of the test following the if or elif reserved words,
On 12/22/17 1:56 PM, Kevin Layer wrote:
> The man page says:
>
> The shell does not exit if the command that fails is part of the
> command list immediately following a while or until keyword,
> part of the test following the if or elif reserved words,
> part of any co
The man page says:
The shell does not exit if the command that fails is part of the
command list immediately following a while or until keyword,
part of the test following the if or elif reserved words,
part of any command executed in a && or || list except the
com
On Fri, Dec 22, 2017 at 1:39 PM, Kevin Layer wrote:
> The bug happens to me on
> GNU bash, version 4.1.2(2)-release (x86_64-redhat-linux-gnu)
> and
> GNU bash, version 4.4.12(1)-release (x86_64-apple-darwin16.4.0)
>
> The script is attached, but the function in question is this:
>
> function debu
The bug happens to me on
GNU bash, version 4.1.2(2)-release (x86_64-redhat-linux-gnu)
and
GNU bash, version 4.4.12(1)-release (x86_64-apple-darwin16.4.0)
The script is attached, but the function in question is this:
function debug1 {
[ "$debug" ] && echo "$(date "+%Y-%m-%d %H:%M:%S"): $@"
}
On 12/21/17 2:03 PM, Drew Parker wrote:
> Bash Version: 4.4
> Patch Level: 12
> Release Status: release
>
> Description:
> In rbash v4.4.12 it is possible to escape the restricted shell by
> running a program in the current directory
> by setting the BASH_CMDS variable. This had currently
