5 added 167 characters in body
source | link

The function name was crafted by bash updated as a response to the shellshock vulnerability.

There was a function named mc that was exported and your bash version is renaming it by prepending BASH_FUNC_ and replacing () by %%.

$ d() { date ; }
$ export -f d
$ env | grep %%
BASH_FUNC_d%% { date

Here is the bash patch by Florian Weimer that introduced this fix, dated Sept 25 2014:

http://seclists.org/oss-sec/2014/q3/att-693/variables-affix.patch

Note that a function name can contain almost any characters in bash just like a command name in general (i.e. a file name) so %% is definitely valid here.

The function name was crafted by bash updated as a response to the shellshock vulnerability.

There was a function named mc that was exported and your bash version is renaming it by prepending BASH_FUNC_ and replacing () by %%.

$ d() { date ; }
$ export -f d
$ env | grep %%
BASH_FUNC_d%% { date

Note that a function name can contain almost any characters in bash just like a command name in general (i.e. a file name) so %% is definitely valid here.

The function name was crafted by bash updated as a response to the shellshock vulnerability.

There was a function named mc that was exported and your bash version is renaming it by prepending BASH_FUNC_ and replacing () by %%.

$ d() { date ; }
$ export -f d
$ env | grep %%
BASH_FUNC_d%% { date

Here is the bash patch by Florian Weimer that introduced this fix, dated Sept 25 2014:

http://seclists.org/oss-sec/2014/q3/att-693/variables-affix.patch

Note that a function name can contain almost any characters in bash just like a command name in general (i.e. a file name) so %% is definitely valid here.

4 deleted 3 characters in body
source | link

The function name was crafted by bash updated as a response to the shellshock vulnerability.

There was a function named mc that was exported and your bash version is renaming it by prepending BASH_FUNC_ and replacing () by %%.

$ d() { date ; }
$ export -f dated
$ env | grep %%
BASH_FUNC_d%% { date

Note that a function name can contain almost any characters in bash just like a command name in general (i.e. a file name) so %% is definitely valid here.

The function name was crafted by bash updated as a response to the shellshock vulnerability.

There was a function named mc that was exported and your bash version is renaming it by prepending BASH_FUNC_ and replacing () by %%.

$ d() { date ; }
$ export -f date
$ env | grep %%
BASH_FUNC_d%% { date

Note that a function name can contain almost any characters in bash just like a command name in general (i.e. a file name) so %% is definitely valid here.

The function name was crafted by bash updated as a response to the shellshock vulnerability.

There was a function named mc that was exported and your bash version is renaming it by prepending BASH_FUNC_ and replacing () by %%.

$ d() { date ; }
$ export -f d
$ env | grep %%
BASH_FUNC_d%% { date

Note that a function name can contain almost any characters in bash just like a command name in general (i.e. a file name) so %% is definitely valid here.

3 added 2 characters in body
source | link

The function name was crafted by bash updated as a response to the shellshock vulnerability.

There was a function named mc that was exported and your bash version is renaming it by prepending BASH_FUNC_ and replacing () by %%.

$ d() { date ; }
$ export -f date
$ env | grep %%
BASH_FUNC_d%% { date

Note that a function name can contain almost any characters in bash just like a command name in general (i.e. a file name) so %%%% is definitely valid here.

The function name was crafted by bash updated as a response to the shellshock vulnerability.

There was a function named mc that was exported and your bash version is renaming it by prepending BASH_FUNC_ and replacing () by %%.

$ d() { date ; }
$ export -f date
$ env | grep %%
BASH_FUNC_d%% { date

Note that a function name can contain almost any characters in bash just like a command name in general (i.e. a file name) so %% is definitely valid here.

The function name was crafted by bash updated as a response to the shellshock vulnerability.

There was a function named mc that was exported and your bash version is renaming it by prepending BASH_FUNC_ and replacing () by %%.

$ d() { date ; }
$ export -f date
$ env | grep %%
BASH_FUNC_d%% { date

Note that a function name can contain almost any characters in bash just like a command name in general (i.e. a file name) so %% is definitely valid here.

2 added 95 characters in body
source | link
1
source | link