News for hackers. Stuff that matters.
Re:Apple's SSL/TLS bug by rdl on Saturday February 22, 2014 @10:08AM (#7282237)
Unfortunately OSX does not appear patched even in the latest developer center 10.9.2 build (13C62). Tested in both Safari and OS-distributed curl. Chrome/Firefox of course is still fine since it uses the NSS stuff, but plenty of OS services use the OS crypto. (I'm violating NDA by commenting on pre-release Apple stuff, of course.)

Windows or ubuntu bootcamp until they fix this, I think.

Re:Apple's SSL/TLS bug by modeless on Saturday February 22, 2014 @11:23AM (#7282503)
MITM of any SSL connection in Safari and other system apps, and they couldn't even bother to have an OS X patch ready at the same time as the disclosure for iOS? I think anyone relying on the security of OS X is going to have to seriously rethink their OS choice after this.
Re:Apple's SSL/TLS bug by catfoods on Saturday February 22, 2014 @12:42PM (#7282798)
Seriously, what were they thinking? They've announced you can attack ≈40% of OS X machines and then didn't provide a fix. Great.
Re:Apple's SSL/TLS bug by kps on Saturday February 22, 2014 @12:38PM (#7282786)

  > I think anyone relying on the security of OS X is going to have to seriously rethink their OS choice after this.
10.7.3 logging FileFault (that was a typo, but I think I'll keep it) passwords in plain text might have been a subtle hint in that direction.
Re:Apple's SSL/TLS bug by rdl on Saturday February 22, 2014 @01:01PM (#7282864)
They've honestly done a pretty great job on iOS security (at least since iPad 2/iPhone 3GS). OSX, not as much.
Re:Apple's SSL/TLS bug by brymaster on Saturday February 22, 2014 @01:50PM (#7283073)
Disagree. They can't even keep the lock screen secure. Any major or point release there's been a bypass exploit.
Re:Apple's SSL/TLS bug by dippyskoodlez on Saturday February 22, 2014 @07:10PM (#7284281)
Re:Apple's SSL/TLS bug by brymaster on Saturday February 22, 2014 @10:26PM (#7284794)
Who said anything about Android?

You might find this article a good read: http://www.theverge.com/2014/1/21/5307992/inside-the-mind-of...

Re:Apple's SSL/TLS bug by nfoz on Saturday February 22, 2014 @05:44PM (#7283973)
How can you know?
Re:Apple's SSL/TLS bug by chmars on Saturday February 22, 2014 @02:10PM (#7283148)
Is there a radar number for that?
Re:Apple's SSL/TLS bug by d0 on Saturday February 22, 2014 @01:05PM (#7282891)
This. Canned my MacBook Pro over this. It's been a bumpy relationship anyway. Just on Thursday Apple Mail stopped sending mail to my SMTP server. Final straw for me.

It's mainly an SSH and RDP terminal anyway.

OSX quality and QA is extremely bad.

Re:Apple's SSL/TLS bug by atmosx on Saturday February 22, 2014 @11:34AM (#7282550)
Indeed the only secure OS nowadays is Linux. Everything else should be considered compromised by default a priori.
Re:Apple's SSL/TLS bug by acdha on Saturday February 22, 2014 @12:12PM (#7282681)
> Indeed the only secure OS nowadays is Linux

Tell that to the people who generated keys on Debian.

Programmers are simply not good enough at writing secure code. Full stop. If you say anything else, you're just flaunting your own unreliability as a source of security advice.

Re:Apple's SSL/TLS bug by hueving on Saturday February 22, 2014 @02:01PM (#7283114)
At least that was public and fixed. I think the point is that keys could be completely deterministic on closed source systems and there is no way to know. It's very easy to have deterministic "random" sources that pass statistical tests for randomness.
Re:Apple's SSL/TLS bug by jey on Saturday February 22, 2014 @02:32PM (#7283240)
Not true. IIRC, the way the Debian bug was found was by some parties noticing a bunch of collisions of SSH public keys.

(For example, Github lets you push/pull via SSH as [email protected], and they determine your identity by the SSH key used.)

Re:Apple's SSL/TLS bug by hueving on Saturday February 22, 2014 @02:50PM (#7283312)
How is what I said not true? If the same thing as the Deb prng bug happened in a closed source system, it could sit for a couple of years exposing thousands/millions of systems and then be patched quietly to avoid embarrassment, leaving everyone vulnerable.
Re:Apple's SSL/TLS bug by lstamour on Saturday February 22, 2014 @05:41PM (#7283955)
FYI -- the source code here is public. Didn't help :D
Re:Apple's SSL/TLS bug by sneak on Saturday February 22, 2014 @07:05PM (#7284260)
It helped us realize how easy it would be to test for this, and that Apple isn't.
Re:Apple's SSL/TLS bug by lawnchair_larry on Saturday February 22, 2014 @08:09PM (#7284494)
I question your code comprehension. This is not easy to test for at all, and Chrome doesn't do it either. Do you understand how to exploit this issue?
Re:Apple's SSL/TLS bug by hueving on Saturday March 01, 2014 @03:44PM (#7326014)
Static analysis would have caught this immediately. It caused unreachable code that the compiler even recognized and optimized away.

You're saying Google Chrome doesn't test that an ephemeral key is actually signed by the cert's private key? If that's the case, that's completely unacceptable because it's the whole point of the protocol.

Re:Apple's SSL/TLS bug by rst on Saturday February 22, 2014 @12:13PM (#7282683)
Don't get too comfortable with linux --- Debian had its own openssl patch fiasco with consequences that were similarly nasty.

http://research.swtch.com/openssl

Re:Apple's SSL/TLS bug by Sanddancer on Saturday February 22, 2014 @01:23PM (#7282969)
I think the various BSD folks, especially those from the OpenBSD team, would like to have a word with you. There are many other unixes out there that put a strong, probably even stronger than linux, emphasis on security.
Re:Apple's SSL/TLS bug by Turing_Machine on Sunday February 23, 2014 @01:13AM (#7285116)
"Indeed the only secure OS nowadays is Linux."

You're kidding, right?

http://www.debian.org/security/

Edit:

There were multiple security issues in OpenSSL as recently as January.

http://www.debian.org/security/2014/dsa-2833

Re:Apple's SSL/TLS bug by sitkack on Sunday February 23, 2014 @02:49PM (#7287269)
We need to stop using OpenSSL. A new crypto stack coded in a provably secure language is sorely needed.
Re:Apple's SSL/TLS bug by ams6110 on Saturday February 22, 2014 @12:48PM (#7282821)
Every OS is compromised a priori. It's just a matter of when the compromises will be discovered. Linux has certainly had its share of flaws.
Re:Apple's SSL/TLS bug by lotsofmangos on Saturday February 22, 2014 @11:39AM (#7282570)
Linux is only secure if you secure it.
Re:Apple's SSL/TLS bug by atmosx on Saturday February 22, 2014 @11:45AM (#7282591)
Sure, but at least you have a say there.
Re:Apple's SSL/TLS bug by abalone on Saturday February 22, 2014 @12:09PM (#7282669)
If you need to say something to make it secure then wouldn't it also be compromised by default?

Security is not a Boolean. A better question is, which OS is more secure OOTB for a given user.

Re:Apple's SSL/TLS bug by lotsofmangos on Monday February 24, 2014 @06:51AM (#7290280)
For some users, none of them. Some users, no matter what, demand password as their password.
Re:Apple's SSL/TLS bug by matznerd on Saturday February 22, 2014 @11:57AM (#7282626)
Do you know of any good guides?
Re:Apple's SSL/TLS bug by eliasmacpherson on Saturday February 22, 2014 @02:56PM (#7283339)
This seems to be a reasonable starting point:

https://www.gov.uk/government/publications/end-user-devices-...

Re:Apple's SSL/TLS bug by rdl on Saturday February 22, 2014 @02:01PM (#7283115)
ChromeOS is by far the safest thing out of the box, IMO.
Re:Apple's SSL/TLS bug by lstamour on Saturday February 22, 2014 @05:43PM (#7283964)
Um, sure, after it updates. Assuming a similar bug isn't found there and exploited when it connects to the Internet. Since, you know, it can't do anything without a network connection. Just playing devils advocate here, I like ChromeOS too.
Re:Apple's SSL/TLS bug by lisper on Saturday February 22, 2014 @12:54PM (#7282842)
Since the source code is available, might it be possible to produce a hot patch to the binary so that those of us running Mavericks won't have to go through the next few days or weeks with our pants down? It would be a simple matter of finding the JMP instruction generated by the second GOTO and replacing it with no-ops. How hard could it be,at least for someone who actually knows their way around OS X binary file formats?
Re:Apple's SSL/TLS bug by gsnedders on Saturday February 22, 2014 @01:17PM (#7282936)
Likely the compiler will have optimized away the rest of the function as dead-code, so it's not as simple as just getting rid of the unconditional jump.
Re:Apple's SSL/TLS bug by lisper on Saturday February 22, 2014 @01:17PM (#7282940)
Ah, right. Good point.
Re:Apple's SSL/TLS bug by lunixbochs on Saturday February 22, 2014 @04:03PM (#7283582)
If the code to Security.framework is complete and builds, we might not need to patch the binary directly.
Re:Apple's SSL/TLS bug by lstamour on Saturday February 22, 2014 @05:44PM (#7283974)
It appears to be in a cursory glance. Loaded for me in Xcode. That said, signing the security framework would be another issue ;-) I can't imagine apple would let malware replace security binaries that easily.
Re:Apple's SSL/TLS bug by lunixbochs on Saturday February 22, 2014 @09:48PM (#7284706)
It's almost buildable for me: https://news.ycombinator.com/item?id=7283601

I think it'd break one of the binaries, but I could replace that with the real one.

Re:Apple's SSL/TLS bug by knweiss on Saturday February 22, 2014 @04:22PM (#7283661)
(Caveat: I haven't tried this myself!) Here's the analysis and an experimental patch from @i0n1c for the 64bit version of Mavericks' Security.framework (32-bit remains unpatched): http://sektioneins.de/blog/14-02-22-Apple-SSL-BUG.html
Re:Apple's SSL/TLS bug by coldtea on Saturday February 22, 2014 @12:51PM (#7282834)
>I'm violating NDA by commenting on pre-release Apple stuff, of course.

Not that we really care. And you could have gotten the beta off of some torrent or whatever, without ever agreeing to the NDA anyway...