du]
Sent: Monday, 24 May 2010 11:23 PM
To: Pitt, David
Cc: bug-bash@gnu.org; chet.ra...@case.edu
Subject: Re: Failed bash -r command returns 0 exit status
On 5/24/10 2:48 AM, Pitt, David wrote:
> Bash Version: 4.1
> Patch Level: 0
> Release Status: release
>
> Description:
>
M
To: Pitt, David
Cc: bug-bash@gnu.org
Subject: Re: Failed bash -r command returns 0 exit status
On Mon, May 24, 2010 at 02:48, Pitt, David wrote:
> However executing "/bin/ls && /bin/ls" under a restricted shell
> returns a zero exit
> status. This is
On 5/24/10 2:48 AM, Pitt, David wrote:
> Bash Version: 4.1
> Patch Level: 0
> Release Status: release
>
> Description:
> Prohibited restricted shell command doesn't always return
> non-zero exit
> status.
>
> Executing "/bin/ls" under a restricted shell returns a non-zero
On Mon, May 24, 2010 at 08:32, Greg Wooledge wrote:
> On Mon, May 24, 2010 at 04:25:48AM -0400, Dave Rutherford wrote:
>> On Mon, May 24, 2010 at 02:48, Pitt, David wrote:
>> > status. This is not expected (at least not by me!). Zero exit
>> > status is returned with
>> > any list o
On Mon, May 24, 2010 at 04:25:48AM -0400, Dave Rutherford wrote:
> On Mon, May 24, 2010 at 02:48, Pitt, David wrote:
> > status. This is not expected (at least not by me!). Zero exit
> > status is returned with
> > any list of commands, e.g. "/bin/ls && :".
>
> That one would, since
On Mon, May 24, 2010 at 02:48, Pitt, David wrote:
> However executing "/bin/ls && /bin/ls" under a restricted shell
> returns a zero exit
> status. This is not expected (at least not by me!). Zero exit
> status is returned with
> any list of commands, e.g. "/bin/ls && :".
Tha
