There are very few OSX servers on the Internet, most of the OS computers on the Internet are PC. So, I fail to see how this could be as big as Heartbleed.
The Bash vulnerability is not limited to OS X. Almost all Linux servers have Bash installed.
There are very few OSX servers on the Internet, most of the OS computers on the Internet are PC. So, I fail to see how this could be as big as Heartbleed.
The big difference is that heartbleed affected web servers, so computers that are facing attacks on a daily basis and where a single attack can compromise thousands of users. There are very few OSX servers on the Internet, most of the OS computers on the Internet are PC. So, I fail to see how this could be as big as Heartbleed.
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?
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?
Why would Apple have included a fix in previous updates for a bug that was reported on today?
The Bash vulnerability is not limited to OS X. Almost all Linux servers have Bash installed.
You did not read the memo: http://www.openwall.com/lists/oss-security/2014/09/24/11: "public disclosure is scheduled for Wednesday, 2014-09-24 14:00 UTC."
That means the bug was found and reported to several companies (RedHat, SuSE, Ubuntu, ... (1)) before that date! And those companies have been working on a patch since then.
Of course it bloody is. If it’s something they can fix they should regardless of who designed the core of the OS.
If you bought a brand new car that had a faulty battery and the car dealer said he could temporarily fix it rather than have you wait for an item from Varta you’d take it right?
The Bash vulnerability is not limited to OS X. Almost all Linux servers have Bash installed.
thatsthejoke.png
Bash is Open Source as well.
Just a snide remark to the "open source is more secure because people can see the source code" crowd.![]()
You can't really blame Apple for this one, since it's not specific to OSX. It's present in other "Nix" systems too...
But have not been able to produce a working patch, so what is the difference.
Are you now talking about Apple and their iOS 8.0.1 disaster?
This article seems to have more info:
http://www.theglobeandmail.com/tech...igger-threat-than-heartbleed/article20781350/
Just a snide remark to the "open source is more secure because people can see the source code" crowd.![]()
No, as far as I have seen so far the first initial patch didn't actually fix the problem. The fact is that the bug was publicly disclosed yesterday, and you are ranting because there is no patch today, as of yet.
No, as far as I have seen so far the first initial patch didn't actually fix the problem. The fact is that the bug was publicly disclosed yesterday, and you are ranting because there is no patch today, as of yet.
Wow. This will effect a lot of OSs. Ironically enough however, Windows is secure from this exploit.![]()
thatsthejoke.png
Bash is Open Source as well.
Just a snide remark to the "open source is more secure because people can see the source code" crowd.![]()
Seriously how has apple not updated bash in such a long time?
Also currently bash has received an incomplete patch so the the patched bash is still vulnerable until the complete fix is pushed out.
.
I worry more about NSA backdoors in our hard- and software.
We are finally (most likely) going to get an update to the system bash in over 7 years!
Seriously how has apple not updated bash in such a long time?
It's a lot younger. The last bugfix came on 17-Mar-2010
More seriously, the problem is GPL v3. With the release of Bash Version 4 GNU changed the license to GPL v3.
Apple does not want to (or can't? I'm no GPL expert) use GPL v3, so they are stuck with old versions. That was the case with gcc, and it's the case with bash and many other shell tools.
Apple will not switch to Bash 4.0. So you are still stuck with the 7 year old shell with bugfixes. Thankfully homebrew comes to the rescue.
This arstechnica article provides a Terminal command test. According to that test, Mountain Lion is also vulnerable.
http://arstechnica.com/security/201...big-security-hole-on-anything-with-nix-in-it/
Ok, now what? What do we do, short of waiting for Apple to fix it?