mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Jon Ringle <jon@ringle.org>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] BASH_FUNC_set_shell_label() not a valid identifier
Date: Thu, 9 Oct 2014 12:50:57 -0400	[thread overview]
Message-ID: <CAMwGMjxGmvUtXGZ0e1AT_=hhJEr66SqTPaMLy3qfvs5Zgevu+Q@mail.gmail.com> (raw)
In-Reply-To: <2238EDC6081C944E97E4EE915AE5CBEC51F61095@EXCHANGE-B.raylase.de>

This page has a good explanation of shellshock, including where
BASH_FUNC_ prefix comes from. It appears that there are variations on
the prefix and suffix that is added to an exported function's name

http://www.dwheeler.com/essays/shellshock.html


On Thu, Oct 9, 2014 at 3:50 AM, Spriggs, Jim <J.Spriggs@raylase.de> wrote:
> Hi Guys,
>
> just confirming this, because it has been puzzling me also for the last week or so.
>
>> bash --version
> GNU bash, version 4.2.47(1)-release (i586-suse-linux-gnu)
>
>> type mc
> mc is a function
> mc ()
> {
>     . /usr/share/mc/mc-wrapper.sh
> }
>
>> ./p --version
> ./p: line 2115: unset: `BASH_FUNC_mc()': not a valid identifier
> 2014.07.0
>>
>
> MfG,
> --
> jim
>
> -----Ursprüngliche Nachricht-----
> Von: ptxdist-bounces@pengutronix.de [mailto:ptxdist-bounces@pengutronix.de] Im Auftrag von Tim Sander
> Gesendet: Montag, 6. Oktober 2014 11:19
> An: ptxdist@pengutronix.de
> Betreff: Re: [ptxdist] BASH_FUNC_set_shell_label() not a valid identifier
>
> Hi
>> >> I'm not sure why I'm getting this message, but speculatively it
>> >> seems to have started appearing after I updated Ubuntu-14.04 with
>> >> bash shellshock patches... ?
> It might have s.th. to do with the ShellShock patches, have not seen this error before but I think this is only for older repositories like 2014.06.0 i don't see this error with 2014.09.0.
>
> Best regards
> Tim
>
> --
> ptxdist mailing list
> ptxdist@pengutronix.de
>
> ________________________________
>
> RAYLASE AG
> Argelsrieder Feld 2+4
> 82234 Wessling
> Germany
> Tel.: +49-(0)8153/88 98-0
> Fax: +49-(0)8153/88 98-10
> http://www.raylase.de
>
> District Court Munich, HRB 131450
>
> Board: Peter von Jan (CEO)
>
> Supervisory Board: Dr. Ulrich Lohmann (Chairman)
>
>
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
>
> This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
>
> --
> ptxdist mailing list
> ptxdist@pengutronix.de

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2014-10-09 16:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-05  4:47 Jon Ringle
2014-10-06  8:07 ` Alexander Dahl
2014-10-06  8:32   ` Bruno Thomsen
2014-10-06  9:19     ` Tim Sander
2014-10-09  7:50       ` Spriggs, Jim
2014-10-09 16:50         ` Jon Ringle [this message]
2014-10-07  9:31 ` Michael Olbrich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAMwGMjxGmvUtXGZ0e1AT_=hhJEr66SqTPaMLy3qfvs5Zgevu+Q@mail.gmail.com' \
    --to=jon@ringle.org \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox