As best I understand, it allows statements after a bash environment variable declaration to be executed as root, without superuser access?
Maybe something like installing a package from an unchecked repo, which contains a shell script that runs something nasty like rm -rf /* (or something more subtle if the hacker isnt just an annoying troll).
Im not sure how this could affect a server, since I dont know much about how networking works, but wouldnt a potential hacker need login info to even start communicating remotely with a server through ssh or the like?
Rather disturbing news though.
Very likely not as bad. "Shellshock" is a bad flaw, but unless you have a terribly botched Linux system, it should work fine. The worst scenario that I can find there is sneaking some code into all shell scripts executed by root.
env = x '() {:;}; Echo vulnerable 'bash c "echo this is a test"




I can't hear a bloody thing, but goddamn was that awesome.

Sounds like a great gig![]()
It was. The first opening act, Skeletonwitch were meh at best, but Sabaton turned it around, and Amon Amarth absolutely killed it. 10/10 would head bang again.
Start a terminal and enter the following command:
Code:env = x '() {:;}; Echo vulnerable 'bash c "echo this is a test"
x='() { :;}; echo "VULNERABLE"' bash -c "echo this is a test"
That only took 10min and a little research so why can't journalists do it....
Donno, DC-3 variant?
Lockheed Martin F-35
If I saw it in Switerland, I would at first assume a Ju-52. But while much of the shilouette would match, the windows aren't in the right place, and there's one too few of them...
Damn it, shilouettes. You sure this isn't an F-18? I could swear it's an F-18, the only thing speaking against it is missing missile pylons on the wingtips, but then again, how accurately are these things drawn?
And the outline of those goofy shaped intakes. I'm sure the labcoated dudes have a reason for them, but they look so very strange.