Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

10
  • 3
    Comparison of Command Shells: ( en.wikipedia.org/wiki/Comparison_of_command_shells ) Advanced Guide to Bash Scripting: ( tldp.org/LDP/abs/html ) ZSH Manual: ( zsh.sourceforge.net/Guide/zshguide.html ) MirBSD Shell Manual: ( mirbsd.org/htman/i386/man1/mksh.htm ). I'm sorry, but this question is too complex. Perhaps you should be asking how to patch bash to fix the vulnerability within for your specific distribution of Linux? Commented Oct 2, 2014 at 16:30
  • 3
    There isn't a shell that can function as a drop in replacement of bash, mksh and zsh can function as /bin/sh with various levels of correctness, but not bash. Commented Oct 2, 2014 at 16:32
  • 2
    The whole shellshock thing seems to have nothing to do with the core question and is just distracting people, so I removed it Commented Oct 2, 2014 at 17:21
  • 3
    The whole question is overly broad. Perhaps you should remove it. Commented Oct 2, 2014 at 17:24
  • 1
    The only concern I really have is that BASH is well maintained by the Free Software Foundation (FSF). My contacts there tell me that the revelation of the, "fundamental flaw," within BASH will only lead to a stronger, more secure implementation. There are so many alternative shells that even beginning to recommend one for your requirement, I would require a solid understanding of your use case. Then on the O/S side... So many things are tied to Bash that you may end up rewriting your entire O/S calls to BASH. The best solution I can see is to choose a distribution with a maintained alt-shell. Commented Oct 2, 2014 at 18:25