THESE FORUMS NOW CLOSED (read only)

Fun Stuff => CLIKC => Topic started by: pwhodges on 22 Feb 2014, 15:36

Title: iOS (and OS X) security bug
Post by: pwhodges on 22 Feb 2014, 15:36
How simple a bug can be!  And with what severe effects!

https://www.imperialviolet.org/2014/02/22/applebug.html (https://www.imperialviolet.org/2014/02/22/applebug.html)
Title: Re: iOS (and OS X) security bug
Post by: snalin on 22 Feb 2014, 17:46
This is why you always add brackets to single-line if-statements. Because then you don't make these kinds of mistakes.

Also goto needs to die forever.
Title: Re: iOS (and OS X) security bug
Post by: Masterpiece on 23 Feb 2014, 02:08
This is why you always add brackets to single-line if-statements.
I was surprised to find that single line if statements were a thing. I found them hugely destroying the flow.
Title: Re: iOS (and OS X) security bug
Post by: pwhodges on 05 Mar 2014, 05:36
And now, in GNU!

http://arstechnica.com/security/2014/03/critical-crypto-bug-leaves-linux-hundreds-of-apps-open-to-eavesdropping/ (http://arstechnica.com/security/2014/03/critical-crypto-bug-leaves-linux-hundreds-of-apps-open-to-eavesdropping/)

Quote
The coding error, which may have been present in the code since 2005,
causes critical verification checks to be terminated,
[...]
It's significant that no one managed to notice such glaring errors,
particularly since they were contained in code that anyone can review.

I'm not saying open source is a bad thing, but it certainly isn't looking effective either!