Carlos F. Lange wrote:
I found this error message in my root mail today:
sh: line 77: syntax error near unexpected token `$'=\\(\\)\\ {\\ \\ eval\\ \\`/usr/share/Modules/\\$MODULE_VERSION/bin/modulecmd\\ bash\\ \\$\\*\\`"\n"}'' sh: line 77: `"}; export BASH_FUNC_module()'
Does this look like a script is trying to exploit the shellshock vulnerability?
Or is it a bug in the fix that now requires executable modules to start with BASH_FUNC_ ?
The fix DOES require adding an additional 10 characters to the beginning of every function name (in memory). The user function names won't change, but in memory they'll have the BASH_FUNC_ prepended. I tried to talk them out of it, or into something shorter, but was ignored. It looks like the above was trying to dynamically load a specific module from your /usr/share/Modules/VERSIONED/bin/modulecmd with arguments 'bash $*". The function did not terminal correctly because curly brackets are joined with adjacent text (they are not delimiters). I don't think that was always the case and I get caught by it now and then as I tend to place braces on the same lines... the above would have needed a "semicolon" between the "\n" and the '}'.... It looks accidental. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org