>having just this evening updated Android to the current arc4random
>(https://android-review.googlesource.com/#/c/99052/), i was confused
>by the single use of explicit_bzero amongst the many calls to memset
>in the same file. as for portability, Linux requires MAP_PRIVATE
>anywhere you use MAP_ANO
Few things to note...
I suspect everyone working on LibReSSL is happy to hear the news about
BoringSSL. Choice is good!! Their priority is on safety, not on ABI
compatibility. Just like us. Over time, I suspect google's version
will also become 'reduced API', since they require less legacy
app
