Apple Fixes Major SSL Bug In OS X, iOS
Trailrunner7 writes: "Apple has fixed a serious security flaw present in many versions of both iOS and OS X and could allow an attacker to intercept data on SSL connections. The bug is one of many the company fixed Tuesday in its two main operating systems, and several of the other vulnerabilities have serious consequences as well, including the ability to bypass memory protections and run arbitrary code. The most severe of the vulnerabilities patched in iOS 7.1.1 and OSX Mountain Lion and Mavericks is an issue with the secure transport component of the operating systems. If an attacker was in a man-in-the-middle position on a user's network, he might be able to intercept supposedly secure traffic or change the connection's properties."
Also fixed in Lion, according to the link, for those of us still using older Macs.
If it's for-profit but free, you're not the customer -- you're the product (e.g., the Slashdot Beta's "audience").
That's swell!
NOT fixed is the issue that IOS 7 does not work properly with authenticated proxy servers.
It forgets your password.
This means every service which uses the HTTP port needs you to enter your password. Got sick and tired of doing this dozens of times a day, every day so wifi gets turned off at work.
not bugs.
Geeze, they're getting rid of all the features now.
Tell me again how this whole issue with SSL is due to the nature of open source and how it's only the commie OpenSSL which can't be trusted...
Seems to me Apple's got a bit of a quality control issue itself.
What's Apple's excuse ?
"the ability to bypass memory protections and run arbitrary code"
I wish I could run arbitrary code on my iPhone without a developer account. Can I put in a feature request for them to unpatch it?
I have a perfectly good MBP of early 2007 vintage running Snow Leopard which can't be upgraded, and it still does the job I need of it today. I can't bring myself to 'upgrade' to the modern MBP's as I hate the chicklet keyboard, so I'm swinging back to windows laptops (linux+windows) to avoid Apple abandonware in the future.
For all the criticism Microsoft gets, at least they don't abandon semi-old stuff.
Seeing 90% packet loss betweet AT&T and something closer to Slashdot's end of the pipe than my end of the pipe.
5 10 ms 8 ms 9 ms 12.122.81.73
6 11 ms 11 ms 10 ms 192.205.33.98
7 12 ms 13 ms 12 ms 206.28.98.117
8 * 63 ms 63 ms 204.70.196.246
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 65 ms 63 ms * star.slashdot.org [216.34.181.48]
13 67 ms 85 ms * star.slashdot.org [216.34.181.48]
14 * * 64 ms star.slashdot.org [216.34.181.48]
Tests from a non-AT&T ISP show normal operation. The problem may be on AT&T's end and not Slashdot's, or it may be between AT&T and /.'s immediate upstream provider - but this has been an ongoing issue for about 8 hours so far today.
A ping reveals about 90% packet loss between here and Slashdot. (Again, no or negligible packet loss between a non-AT&T ISP). I have verified this with as many IPs as I can get from my own netblock, but they all funnel through the same rout past 12.83.88.173
Impact: An attacker with a privileged network position may capture
data or change the operations performed in sessions protected by SSL
Description: In a 'triple handshake' attack, it was possible for an
attacker to establish two connections which had the same encryption
keys and handshake, insert the attacker's data in one connection, and
renegotiate so that the connections may be forwarded to each other.
To prevent attacks based on this scenario, Secure Transport was
changed so that, by default, a renegotiation must present the same
server certificate as was presented in the original connection.
Hardly anyone serious uses Apple's server OS, especially in datacenters, so the footprint affected would most likely be super tiny.
Just here to scoff at Apple *again* feel free to mod down.
"If any question why we died, Tell them because our fathers lied."
Why add gender to this statement?
Sadly, VMS support for VAX ended around 7.1 or 7.3 or something - it was in the late nineties. But every alpha ever made (at least "that ever ran VMS in the first place") can run the latest version.
All UltraSPARCS can run solaris 10.X. Hardware from this millenium is required for Solaris 11.X (more or less). Pre-Ultra machines are kind of limited - A microsparc machine (sparcStation 5 and similar) is supported on 2.9, but unless you max out the RAM you're better off at 2.8. Sparcs with VME busses (4/110, 4/280, etc) are stuck further back - maybe Solaris 2.4, but I'm not sure. These are better off running OpenBSD anyway. :-)
Yeah, I get a laugh out of what constitutes "support" these days. :-)
I have a perfectly good MBP of early 2007 vintage running Snow Leopard which can't be upgraded.
A Macbook pro of that "vintage" can be upgraded Lion, for a grand total of $20.
Just goes to show.
FU
I also jerked off into the ear holes of a corpse.
Cook want to be Gay, because in Federal Employment, 'Gay' is the new 'Black.'
Let's help !
Kidnap Cook.
Stick a stick of dynamite wrapped in a Trojen Condum up Cook's ass !
Apply SuperGlue to the "Hams" generously.
Apply Duck Tape around the butt and pelvis tightly.
Light Up.
Retreat to a protected bunker.
"BLOUIE BAM"
Wooooooooo ! What a fucker fire cracker !
Just goes to show.
Ha ha
The Russkie and the FtMeade Mafia will never lower themselves to the use of a powerful assembly-debugger or a decompiler. We know that. Neither will the North Korean Long Range Recon Forces do that.
doesn't surprise me that apple finally "fixes" a longstanding security issue.
it also would not surprise me if there are others, yet undiscovered (by the PUBLIC), present.
Apple's a small company, they can't afford to offer long term support.
oh...
Heartbleed affects clients, too. Android phones running 4.1.1, for example. http://www.bloomberg.com/news/...
Clear, Dark Skies
when you try to put windows 8.1 on a 7 year old computer.
Clear, Dark Skies