bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bash --version issue


From: Allodoxaphobia
Subject: Re: Bash --version issue
Date: 26 Sep 2014 16:50:32 GMT
User-agent: slrn/1.0.1 (FreeBSD)

On Fri, 26 Sep 2014 10:25:32 -0400, Chet Ramey wrote:
> On 9/26/14, 10:15 AM, Allodoxaphobia wrote:
>
>> There was another bash upgrade in the FreeBSD ports this A.M.
>> Thinking it might resolve my bash --version problem, I applied it.
>> 
>> sigh...
>> 
>>  | [userid~]bash
>>  | /usr/local/bin/bash: warning: x: ignoring function definition attempt
>>  | /usr/local/bin/bash: error importing function definition for `x'
>>  | bash: warning: x: ignoring function definition attempt
>>  | bash: error importing function definition for `x'
>>  | [userid@vps ~]$   
>
> OK. What do
>
> type x
>
> and
>
> echo $x
>
> return when you run them in the shell that invokes bash, which then 
> throws the above error?

Ahhh!!!  I see it now.

Before I did the bash upgrade I had done the SHELLSHOCK test:
 | $ env x='() { :;}; echo vulnerable' bash -c "echo this is a test"
 | bash: warning: x: ignoring function definition attempt
 | bash: error importing function definition for `x'

Then, without logging out I did the (newest, 2nd) FreeBSD bash upgrade. 

And then -- still without logging out -- I would see the following for 
the she-bang in a script:

 | $ script.sh
 | /usr/local/bin/bash: warning: x: ignoring function definition attempt
 | /usr/local/bin/bash: error importing function definition for `x'

Simply logging out and back in again has cleared up this "new problem".
Sorry for the noise.

Jonesy
-- 
  Marvin L Jones    | Marvin      | W3DHJ  | linux
   38.238N 104.547W |  @ jonz.net | Jonesy |  OS/2
    * Killfiling google & XXXXbanter.com: jonz.net/ng.htm



reply via email to

[Prev in Thread] Current Thread [Next in Thread]