News for hackers. Stuff that matters.
Re:CVE-2014-6271: Remote code execution through bash by chjj on Wednesday September 24, 2014 @01:11PM (#8362674)

    $ x='() { :;}; echo vulnerable' bash -c 'echo test'
    vulnerable
    test
    $ pacman -Syu
    ...
    $ x='() { :;}; echo vulnerable' bash -c 'echo test'
    bash: warning: x: ignoring function definition attempt
    bash: error importing function definition for `x'
    test
Benefits of using an OS with a real package manager.
Re:CVE-2014-6271: Remote code execution through bash by tinco on Wednesday September 24, 2014 @01:19PM (#8362717)
Just don't turn it off after you've ran `pacman -Syu`, it will never boot again ;)
Re:CVE-2014-6271: Remote code execution through bash by thevdude on Wednesday September 24, 2014 @02:18PM (#8363132)
I know you're just teasing, but I've got a machine with an arch install from over two years ago that's still running great. Just did an -Syyu to get bash updated.
Re:CVE-2014-6271: Remote code execution through bash by antocv on Wednesday September 24, 2014 @05:41PM (#8364312)
The trick is to keep up with the updates, do pacman -Syu every two weeks or so, and not wait months.
Re:CVE-2014-6271: Remote code execution through bash by alexbecker on Wednesday September 24, 2014 @04:00PM (#8363762)
After it happened 5 times in a row, I finally just aliased pacman -Syu to "breakX".