process substitution data corruption on FreeBSD 5.3

Configuration Information [Automatically generated, do not change]: Machine: i386 OS: freebsd5.3 Compiler: cc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386' -DCONF_OSTYPE='freebsd5.3' -DCONF_MACHTYPE='i386-portbld-freebsd5.3' -DCONF_VENDOR='portbld' -DLOCALEDIR='/usr/local/share/loc

printf builtin retains timezone from un-set TZ environment variable

"TZ: $TZ\n\t%(%+)T\n" $ env -i $(which bash) --norc --noprofile tzcache.sh 5.0.7(1)-release TZ: Antarctica/South_Pole Sun Jul 14 05:21:49 NZST 2019 TZ: Sun Jul 14 05:21:49 NZST 2019 TZ: Sat Jul 13 12:21:49 CDT 2019 Cheers, Travis

syntax errors produced by interaction between process substitution and a SIGCHLD trap

Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: darwin17.7.0 Compiler: clang Compilation CFLAGS: -g -O2 -Wno-parentheses -Wno-format-security uname output: Darwin 6841b968 18.6.0 Darwin Kernel Version 18.6.0: Thu Apr 25 23:16:27 PDT 2019; root:xnu-4903.261.4~

inconsistent readonly error behavior

Configuration Information [Automatically generated, do not change]: Machine: x86_64OS: darwin17.7.0 Compiler: clang Compilation CFLAGS: -g -O2 -Wno-parentheses -Wno-format-security uname output: Darwin ecf1160e 19.6.0 Darwin Kernel Version 19.6.0: Mon Aug 31 22:12:52 PDT 2020; root:xnu-6153.141.2~1

Re: inconsistent readonly error behavior

; On Tue, Dec 22, 2020 at 7:28 AM Travis Everett > wrote: > >> Configuration Information [Automatically generated, do not change]: >> Machine: x86_64OS: darwin17.7.0 >> Compiler: clang >> Compilation CFLAGS: -g -O2 -Wno-parentheses -Wno-format-security >> u

Re: inconsistent readonly error behavior

12:21 PM, Travis Everett wrote: > > I don't understand what distinction you're trying to make; any example > you > > can give? > > > > I added an extra near-copy of the script to the gist replacing the > > assignment with unset > > `unset' is a diff

Re: inconsistent readonly error behavior

Got it. Thanks. :) On Wed, Dec 23, 2020 at 10:19 AM Chet Ramey wrote: > On 12/23/20 11:10 AM, Travis Everett wrote: > > I think I'm missing or misreading something. If I understood, the > > assignment and expansion errors are both shell errors that should have > the

Security Vulnerability Reporting

Good Morning/Afternoon/Evening, Is there a set process in place for reporting security vulnerabilities against bash? If so, what might that process be? Thank you much! Regards, Travis Garrell