Re: Here strings and brace expansion not working as per man page

On 9 February 2017 at 20:55, Chet Ramey wrote: > On 2/8/17 3:04 PM, Conor McCarthy wrote: > >> Bash Version: 4.4 >> Patch Level: 12 >> Release Status: release >> >> Description: >> Here strings are documented as: >> >>[n]<<> >> The word undergoes brace expansion, tild

Re: Does bash treat segment fault causing by scripts as security bugs ?

On 2/15/17 9:45 AM, Pierre Gaston wrote: > I'm re-adding the list. > > On Wed, Feb 15, 2017 at 4:34 PM, kkk K <3n4t...@gmail.com > > wrote: > > What If I find a bug bypassing the FUNCNEST limitation ? > I mean I found a bug which about some paser logic in bash, >

Re: Does bash treat segment fault causing by scripts as security bugs ?

I'm re-adding the list. On Wed, Feb 15, 2017 at 4:34 PM, kkk K <3n4t...@gmail.com> wrote: > What If I find a bug bypassing the FUNCNEST limitation ? > I mean I found a bug which about some paser logic in bash, > finially It will crash bash, And FUNCNEST cannot stop it from crashing > bash. > > I

Re: Does bash treat segment fault causing by scripts as security bugs ?

On 02/15/2017 07:01 AM, Pierre Gaston wrote: > If you can run arbitrary code in a shell (or even if your script doesn't > validate its input), your security is already compromised. Or put another way, bash CVEs are rare, and exist primarily when the shell can be made to run arbitrary code without

Re: Does bash treat segment fault causing by scripts as security bugs ?

On Wed, Feb 15, 2017 at 11:44 AM, kkk K <3n4t...@gmail.com> wrote: > for example, > simple bash recur function call: > > == > #!/bin/bash > > function test() > { > test $1 > } > > test 1 > == > > sincerely for your reply > > bash has a special variable FUNCN

Does bash treat segment fault causing by scripts as security bugs ?

for example, simple bash recur function call: == #!/bin/bash function test() { test $1 } test 1 == sincerely for your reply