Practically every OpenSSL bug posted here gets the standard "Luckily LibreSSL isn't affected by this kind of thing" response. On a couple of occasions I've taken the bait and linked to the LibreSSL source to show that the relevant bits are in fact not changed at all, so they were both vulnerable.

Not saying LibreSSL isn't doing good stuff, I just wish people would actually check if it's affected before using any opportunity to jump on the let's-hate-on-openssl bandwagon.

(I haven't looked into these bugs in the LibreSSL code since I don't have time for it right now, but I'm sure some message is forthcoming).

That's not a bulletproof way to assess bugs in LibreSSL because its authors also removed vulnerabilities from general helpers functions, proactively fixing issues in the code that uses them.

Well it looks like that has just changed: https://marc.info/?l=libressl&m=147454940615412&w=2

You say this like LibreSSL has been out for a long time. It's just barely crossed it's 2 year mark... and for most of it's life, it's difficult to call it "production ready".

Coupled with its low adoption rate (really only some select BSD's, and some adventurous linux folks), it's not surprising more vulnerabilities haven't been discovered (yet).

The OpenBSD folks do good work, but let's not pretend they are infallible.

For now, watch this spot:

https://marc.info?l=libressl&r=1&b=201609&w=2

Where did you get that impression?

https://github.com/libressl-portable/openbsd/commits/master shows an actively developed project

If we still stay with C, Ring would be a good replacement, which is partially/primarily written in Rust.

That said, LibreSSL's TLS abstractions look like a welcome improvement if you need a C API.

Google don't recommend you do this.

https://boringssl.googlesource.com/boringssl/

  BoringSSL is a fork of OpenSSL that is designed to meet Google's needs.
  
  Although BoringSSL is an open source project, it is not intended for general
  use, as OpenSSL is. We don't recommend that third parties depend upon it.

LibreSSL has taken fixes from BoringSSL but it has the aim of maintaining API compatibility to the point where most applications using OpenSSL should "just work" for the most part. I've not tried building against BoringSSL but form reading their documentation it seems like the API is very much a moving target.

Then there's ocaml-tls which aims to provide a drop-in implementation of the OpenSSL API too.

We're finally seeing much activibity, and in that sense, I'm glad that Heartbleed happened, but it should have been earlier :).

Yes.