First world problems maybe.
Thermo-nuclear fallout if you read the press.
First world problems maybe.
Actually .. they do. Just like all major OS vendors do too.
Often enough security flaws are found by third party researchers or companies. Usually it is good practice to inform the vendors security team ahead of a public statement to give the vendor time to roll out a fix before the bug hits the streets.
It seems in this case, most major Linux vendors responded with a quick fix. Apple (so far) didn't. It is however not clear whether or not they where informed.
So coming back to your point. Often enough vendors can only start investigating bugs after they have been publicly discussed on the internet because they simply do not know of them before.
T.
I guess this could be the one time that Microsoft fans can say to OS X and Linux (really any 'NIX) fans that Windows DOESN'T have a flaw that IS present on OS X, Linux and any other Unix-based OS.
The bug is fixed. The patch is available. Apple could have rolled it out by now.
The GNU people even were so nice to backport the fixes to the ancient version Apple is using because Apple doesn't want code that's licensed with GPL v3.
http://ftp.gnu.org/gnu/bash/bash-3.2-patches/bash32-052
Apple just has to apply the patch and provide a new bash binary through software update. Apple does not have to identify the bug, they don't have to come up with a solution, they don't have to verify the fix. Everything is done already.
Stupid politics are the only thing that prevent the release of this bugfix. Probably because they like to bundle patches so people think their software is more secure because it isn't patched that often.
You mean like OpenSSL? Which is basically an unmaintainable and undocumented mess of code? Where you are free to search for bugs in the source code, but have no chance to find them, and even less of a chance to fix them?
I guess this could be the one time that Microsoft fans can say to OS X and Linux (really any 'NIX) fans that Windows DOESN'T have a flaw that IS present on OS X, Linux and any other Unix-based OS.
This is incorrect. The patch they released is incomplete: http://seclists.org/oss-sec/2014/q3/685. There's a new version as of a couple of hours ago, but that one still needs to be tested, let alone ported to Apple software.
Nope. The fact that windows doesn't even have a terminal is a flaw in itself. And nope, windows power shell is a joke.
The perks of having a perfectly robust computer paired with software to use offline.
If you're going to be a certified Apple basher, you need to keep track of all the Apple badness from Mobile Me to iPhone 4 antenna gate and forward. The real question is what's the impact; probably minor since the only current issue that can't readily be fixed is the iPhone 6 plus design flaw but the same happened with the iPhone 4 - they'll end up giving out a free case for those who jam their giant phones in their skinny jeaned fat bodies.
I'm not - I love Apple - but this week they've been to hell and back!
Why is everyone so desperate to cover up that fact?
I more or less agree with all your points excluding the "bendgate" one: according to the various (admittedly unscientific) tests I've seen the iPhone 6+ compared to other smartphones bends far too easily.
The smaller iPhone 6 is much more resilient which can only be in part due to its smaller size: it looks more like that the larger iPhone 6+ has a weak point near the volume buttons which the smaller iPhone 6 lacks.
The smaller iPhone has a weak point there too; it's because of the buttons which of course require a hole in the case. That's a natural weak point.
As for why the plus bends more easily than the non-plus, I'm not sure. Of course it being smaller means it's harder to bend unintentionally (smaller size means less force) but it also seems to be harder to bend intentionally. Which, given that it's also slightly thinner than the 6 plus, I can't really explain.
Relax, people, the sky is not falling.
This problem primarily affects things running a (web) server.
Your home Mac might technically be affected, but you're likely not running anything that exposes the bug to an attacker.
strike three. you're out...
now what?
*still waiting for iPhone + Apple Watch*
strike three. you're out...
now what?
*still waiting for iPhone + Apple Watch*
Actually the patch that I used as I noted in the above message worked great and the terminal test for showing the vulnerability (env x='() { :;}; echo vulnerable' bash -c "echo this is a test") showed the patch worked.