News for hackers. Stuff that matters.
Re:Apple's SSL/TLS bug by jdsnape on Saturday February 22, 2014 @09:07AM (#7282067)
This shows another of the benefits for the community of open sourcing code - because we can see exactly where and what the bug was steps can be taken in other projects to stop it happening there (I think Adam mentioned he was going to check for a test case in Chrome).

If the code was closed all we would have is Apple's release note which just says validation steps were skipped...

[deleted]
Re:Apple's SSL/TLS bug by Schlaefer on Saturday February 22, 2014 @11:25AM (#7282510)
He didn't say it isn't OSS. He just pointed out that it is educational to see the actual code as we do in this OSS case.
Re:Apple's SSL/TLS bug by randomdrake on Saturday February 22, 2014 @12:19PM (#7282709)
You are probably right. The thread was so full of people making similar assumptions, my early morning brain lumped this in.
Re:Apple's SSL/TLS bug by ZoFreX on Saturday February 22, 2014 @02:00PM (#7283111)
The code in question is open source.
Re:Apple's SSL/TLS bug by ZoFreX on Sunday February 23, 2014 @09:13AM (#7285929)
Wish I could delete that comment - reading comprehension failure!