Re: Race in bash-4.3 'typeset'?

2016-10-24 Thread Martijn Dekker
Op 25-10-16 om 00:42 schreef Stuart Shelton: > Failing this, is there any alternative to ‘typeset’ to list a > variable declared as local to a function but which has not yet been > assigned a value? Try simply testing the exit status of 'typeset -p' or 'declare -p'. If the variable is not declared

Race in bash-4.3 'typeset'?

2016-10-24 Thread Stuart Shelton
I have some code which evals a configuration file - but before doing so attempts to validate the content. It does this by taking each potential keyword from the file and then doing: if typeset -p | grep -q "^declare -. ${var}$”; then … to determine whether the keyword in question exists as a

Re: 4.4 change in behavior from 4.3: how to catch unset when using ${#length}

2016-10-24 Thread L. A. Walsh
Chet Ramey wrote: On 10/21/16 5:41 PM, L. A. Walsh wrote: [previously] one could have the illusion of this working w/o complaint -- and returning 0 when the array was 0-len or unset, or the array length, otherwise: echo ${#array[@]:-0} But I note it only seemed to work in arrays, and in

Re: Correction of CVE-2016-7543 is incomplete

2016-10-24 Thread Ola Lundqvist
Hi Thank you for the information. Good to know that I'm not the only one that have seen this problem. One can of course argue that the attack vector is a little odd. That is a setuid binary making system. I thought system was safe enough, but now I have learnt otherwise. Anyway I do not think di

Re: for Chet Ramney in Born Againe

2016-10-24 Thread Dan Douglas
On Mon, Oct 24, 2016 at 8:33 AM, Корень Зла wrote: > Can u re:coded BASH for Power Shell features to fully intagrated with Linux > enviroments Directly supporting features in a compatible way would not be easy. Powershell is a completely different language, and bash isn't yet implemented on the

[PATCH] multiline syslog patch

2016-10-24 Thread Czichy, Thoralf (Nokia - FI/Espoo)
hi, attached a patch that builds on the existing "log interactive commands to syslog" bash feature (SYSLOG_HISTORY). This capability is used in some of our devices to be able to track which management operations were executed on them using bash (with appropriate legal information at login). Th

Re: Correction of CVE-2016-7543 is incomplete

2016-10-24 Thread up201407890
Quoting "Ola Lundqvist" : This is known. I "complained" at the time, as it can be seen here: https://lists.gnu.org/archive/html/bug-bash/2015-12/msg00112.html Version: all (see note below) Hardware: all Operating system: Debian GNU Linux (but all should be affected) Compiler: gcc Hi In CVE-

Re: bash history / ssh+sudo+reverse-i-search will execute the command found if the ssh process is killed

2016-10-24 Thread Chet Ramey
On 10/19/16 1:46 PM, Stein Arne Storslett wrote: > Bash Version: 4.2 > Patch Level: 46 > Release Status: release > > Description: > Bash history / reverse-i-search will execute the command found > if the ssh process is killed. > This happens with the combination of: > - s

Correction of CVE-2016-7543 is incomplete

2016-10-24 Thread Ola Lundqvist
Version: all (see note below) Hardware: all Operating system: Debian GNU Linux (but all should be affected) Compiler: gcc Hi In CVE-2016-7543 a problem was reported that it is possible to privilege escalate to root. The correction as seen here http://lists.gnu.org/archive/html/bug-bash/2016-10/ms

for Chet Ramney in Born Againe

2016-10-24 Thread Корень Зла
Hello developers. Few mounth ago microsoft released sources of Power Shell. Can u re:coded BASH for Power Shell features to fully intagrated with Linux enviroments for more dinamicly DE objects stuff usefull without terminal. Now i seen intagrated of thats kind on GTK tools and others,done any of

Re: 4.4 change in behavior from 4.3: how to catch unset when using ${#length}

2016-10-24 Thread Chet Ramey
On 10/21/16 5:41 PM, L. A. Walsh wrote: > On 4.3 and earlier, at least on arrays, one could have > the illusion of this working w/o complaint -- and returning > 0 when the array was 0-len or unset, or the array length, > otherwise: > > > echo ${#array[@]:-0} > > But I note it only seemed to wor

Re: 4.4 change in behavior from 4.3: how to catch unset when using ${#length}

2016-10-24 Thread Greg Wooledge
On Fri, Oct 21, 2016 at 09:19:08PM -0700, L. A. Walsh wrote: > Eduardo Bustamante wrote: > >what's wrong with?: > >echo ${#array[@]} > Not when "-u" is set, which I often have on to help catch misspellings. > > set -u > echo ${#array[@]} > bash: array: unbound variable See http://mywiki.wooledge