BASH_ARG{C,V} set when sourcing, even without extdebug

It looks like the source builtin pushes its own argc and argv onto the arrays but only if it is called with no other arguments. $ cat /tmp/s fun() { declare -p BASH_ARGC BASH_ARGV; } fun arg $ shopt -u extdebug; source /tmp/s declare -a BASH_ARGC=([0]="1") declare -a BASH_ARGV=([0]="/tmp/s") $

Re: My System get vuln in Shellshock, what should i do ?

contact the people who support your distro, or whatever hosting company you might be using -mike signature.asc Description: Digital signature

Re: ${var@P} expansion includes 0x01 and 0x02

On Fri, Nov 6, 2015 at 7:51 AM, Chet Ramey wrote: > On 11/5/15 7:45 PM, Dennis Williamson wrote: > > > That's what the \[ and \] escape sequences expand to and use to > > communicate information to readline about invisible characters in the > > prompt (RL_PROMPT_START_IGNORE and RL_PR

Re: Proposed Prompt Escapes

On Thu, Nov 5, 2015 at 6:26 PM, Dennis Williamson < dennistwilliam...@gmail.com> wrote: > It might be handy to have some of the escapes that work in $'string' > quoting to also work in prompts especially now with the ${parameter@P} > transformation. > > Specifically the hex, unicode and control on

Re: Bug in bash 4.4-beta: suspending and restarting "man" program

I have some more information on this. In the latest test, the problem occurs when I run bash under rxvt, but not when I run it under xterm. Using strace, I've found a difference in a call to rt_sigaction(). It calls rt_sigaction(SIGTSTP, {SIG_DFL, ...}) under xterm (which works correctly), but

Re: Out of bounds heap read in function rl_tilde_expand

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/6/15 9:46 AM, Hanno Böck wrote: > Hi, > > While testing bash with address sanitizer I discovered a heap out of > bounds read. This affects bash 4.3 with the latest patchlevel 42. Thanks for the report. This will be fixed in the next release of

Re: My System get vuln in Shellshock, what should i do ?

On 11/9/15 6:03 AM, Muhammad Hafiz Izman Bin Ab Rahim wrote: > mhafizizman@ThinkspiratioN:~$ bash --version > GNU bash, version 4.3.0(1)-release (x86_64-unknown-linux-gnu) > Copyright (C) 2013 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later

Re: My System get vuln in Shellshock, what should i do ?

On Mon, Nov 09, 2015 at 06:03:29AM -0500, Muhammad Hafiz Izman Bin Ab Rahim wrote: > mhafizizman@ThinkspiratioN:~$ bash --version > GNU bash, version 4.3.0(1)-release (x86_64-unknown-linux-gnu) Upgrade to a newer (patched) version of bash. If you're building it yourself from source code, use ht

My System get vuln in Shellshock, what should i do ?

mhafizizman@ThinkspiratioN:~$ bash --version GNU bash, version 4.3.0(1)-release (x86_64-unknown-linux-gnu) Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software; you are free to change and redistribute

Re: Add -L to kill builtin to be more compatible to procps version of kill

On Mon, Nov 09, 2015 at 02:19:56PM +0100, Christian Ehrhardt wrote: > Hi everybody, > there was no further response since then. Since when? The kill -L synonym is in bash 4.4-beta.

Re: Add -L to kill builtin to be more compatible to procps version of kill

On 11/9/15 8:19 AM, Christian Ehrhardt wrote: > Hi everybody, > there was no further response since then. > > I checked if the patch would cleanly apply to the bash git as of today. > Other than a 7 line offset it does. > > I didn't find a savannah bug page for bash to open a more formal request.

Re: Add -L to kill builtin to be more compatible to procps version of kill

Hi everybody, there was no further response since then. I checked if the patch would cleanly apply to the bash git as of today. Other than a 7 line offset it does. I didn't find a savannah bug page for bash to open a more formal request. So I wanted to ask if you need more to consider the former