gsoc2014#bug-tracking -- http://www.openbsdfoundation.o...
What's FIPS?
Who requires FIPS?
Think geography. (-:
I'm too lazy to find the source right now, but my recollection was that Mozilla was first to make a stance against H.264 (in order to not partition the Linux out), prior all those stories of Google dropping support for H.264 in Chrome (which I guess they never did, after all).
So funny. Just a few short years ago, Mozilla explicitly declined to support H.264 on Windows, even if there was a free native plugin, since it'll partition the Linux users.
And now they're deciding to support DRM, just to keep the market share?
OpenSSL has basically wrote their own version of libc, and all the functions they've introduced differ is some very subtle ways from what appears in libc used by the rest of the world.
Rest assured, OpenBSD is no stranger to portable code. Just take a look at the number of platforms they support -- http://www.openbsd.org/plat.ht....
Like the big-endian x86 support in OpenSSL?
OpenBSD's OpenSSH has a separate portability layer, and they're doing just fine without the extra malloc wrappers. And no big-endian x86 support, either!
Fast, cheap, good: pick two.