Re:How SSL Kill Switch works on iOS 12
by maallooc on Tuesday May 26, 2020 @08:56AM
(#23310511)
Why is Apple using BoringSSL on their OS?
[ Parent
| on HN ]
We switched to BoringSSL at Cloudflare (from OpenSSL) about 3 years ago.
A few reasons why can be found here: https://blog.cloudflare.com/make-ssl-boring-again/.
seems to be an ok choice. It's maintained by a very capable team that has a strong security focus, it's in use on the largest mobile platform (Android) and the motivations and focus behind its maintenance align well with Apple's.
What would you have chosen? And why?
Re:How SSL Kill Switch works on iOS 12
by tenebrisalietum on Tuesday May 26, 2020 @01:12PM
(#23313722)
There was the Heartbleed vulnerability which affected just about everything that used OpenSSL, which was a lot of things. There were some efforts to fork this codebase and simplify it. BoringSSL is one of those, LibreSSL another.
Summary I recall from looking into LibreSSL website some time ago: OpenSSL has a lot of cruft and does weird things like implements its own memory allocator. Most of this is because it supports an extremely wide variety of platforms (I think things like VAX and Amiga). This makes tools that try to detect things like buffer overflows not work properly, which is what Heartbleed was.
There have been many minor versions of OpenSSL released to update security vulnerabilities since Heartbleed.
Re:How SSL Kill Switch works on iOS 12
by colejohnson66 on Tuesday May 26, 2020 @04:48PM
(#23316203)
Why are those platforms still supported?
It seems like they use it after iOS 11[1],
Maybe they want to prevent another possible goto fail[2] bug?