Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKA
(this is maybe too edge-case to be worth looking at)
A couple circumstances cause repeated instances of \001 and any
instances of \177 to be removed from as string:
$ a=$'<\001\001><\177\177>'
$ z=$(compgen -W "$a"); echo "${z@A}"
z=$'<\001><>'
$ declare -A A=(); printf -v "A[$a]" X; declare -p A
On 9/20/18 6:57 PM, ga...@pie-dabas.net wrote:
>
> Thanks for pointing to old threads.
> I was able to find root cause of this issue, somewhere in LKML.
> And was forced to patch and recompile some more freeware tools, like "tar"
> and "make", used in our development environment.
>
> Sad truth ab
Thanks for pointing to old threads.
I was able to find root cause of this issue, somewhere in LKML.
And was forced to patch and recompile some more freeware tools, like "tar"
and "make", used in our development environment.
Sad truth about all that - lack of consistent LARGEFILE support in GNU
h
I was testing out this new feature and I can't figure out how to handle
certain characters in subscripts when the option is on. Without the
option,
it is possible to escape the `$' in the subscript to achieve the desired
result but obviously that does not work if the option *is* on -- is there a
d
On 9/20/18 5:40 AM, ga...@pie-dabas.net wrote:
> Hello all,
>
> I have collection of some AIX specific patches, to fix wildcards and path
> completion, if used on NFS mounted filesystems.
>
> As a beginner in GNU contributions, i was not able to format in proper
> way. Sorry about that. Anyway, i
Hello all,
I have collection of some AIX specific patches, to fix wildcards and path
completion, if used on NFS mounted filesystems.
As a beginner in GNU contributions, i was not able to format in proper
way. Sorry about that. Anyway, i will put my work here, and if possible,
format it better in
On 9/20/18 3:45 AM, Eduardo A. Bustamante López wrote:
> Found by fuzzing with AFL.
Thanks for the report.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRUc...@case.eduhttp://tiswww.cwru
On 9/20/18 4:23 AM, Eduardo A. Bustamante López wrote:
> Found using AFL. The following causes bash 5.0 to get into an infinite loop:
>
> (sorry for the junk reproducer, I don't know how to minimize non-crashing
> inputs)
Thanks for the report. It's a pretty obscure case.
Chet
--
``The lyf so
Found using AFL. The following causes bash 5.0 to get into an infinite loop:
(sorry for the junk reproducer, I don't know how to minimize non-crashing
inputs)
bash-5.0$ IFS= read -r < <(base64 -d <<<
'QCgusbGxw7GxsbGxsbGxsbGxKyQoKChzc3NzcwRpc3Nzc3Nzc3NzdnNzKSMpBymxsbGxsbGxsbGxsR4oGCgoVQ==');
:
Found by fuzzing with AFL.
$ base64 -d >i
MDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwEzAwMDAwMDAA
MDAwMDAwMDAwMDAwMDAwMDAw/zAwMDAwMDAwMDAwMDAwMDAwMDABExMZMDAw86Iw
$ cat -A i
^S000^@00M-^?000^A
11 matches
Mail list logo