When Porting LibreSSL, Don't Assume Your OS Is As Sane As OpenBSD (x-post from /r/OpenBSD) reddit / BSD ---------------------------------------------------------------------- undefined_conduct · 2014-05-05 07:15 OS designed largely to be most secure OS more secure than most other OSes. Who'd've thunk? ---------------------------------------------------------------------- [deleted] · 2014-05-05 07:24 [deleted] ---------------------------------------------------------------------- qci · 2014-05-05 07:59 So they admitted that they destroyed portability. Well done OpenBSD. Portability is a quality criterion. If you destroy it, you are as evil as Microsoft when they use they special APIs. OpenBSD is also turning evil. Theo allegedly knows a security bug in OpenSSH on FreeBSD and intentionally does not fix it and does not even want to tell what he has found. ---------------------------------------------------------------------- phessler · 2014-05-05 08:24 LibreSSL is a two stage process: Stage 1) Unfuck Stage 2) Port to other systems. Currently, the OpenBSD team is working on Stage #1. Additional volunteers are (somewhat) jumping the gun, and working on Stage #2, without thinking about the justifications of what they are doing. **That** is the problem the article is talking about. ---------------------------------------------------------------------- fwaggle · 2014-05-05 10:08 They admitted they were destroying portability before they started this project. One of the primary reasons OpenSSL is such a train wreck at the moment is because they refuse to give up support for platforms that NetBSD would turn their nose up at. ---------------------------------------------------------------------- CorinnaBrodez · 2014-05-05 11:46 Have you got a source for that SSH/FreeBSD non-disclosure? ---------------------------------------------------------------------- [deleted] · 2014-05-05 12:48 It is, I imagine, a reference to [this thread](http://marc.info/?t=139701505400004&r=1&w=2) However, it sounds presumptuous to say "intentionally does not fix it". To my eye, it reads that there is a bug in the OpenSSH implementation in FreeBSD, which exists in Juniper and other FreeBSD- derived products, and does NOT say it is unfixed in the OpenBSD versions. So if it's not in code under Theo et al's control, how could he fix it? As for telling about it, the reasons are given in the linked thread. ---------------------------------------------------------------------- qci · 2014-05-05 14:06 http://thread.gmane.org/gmane.os.openbsd.tech/35722/focus=35731 Theo writes: > Please ask Kirk McKusick, he knows the > story about why this is not being disclosed to FreeBSD. > Sometimes I feel a bit sorry for them (and for him), > but then the next minute I don't feel sorry because > there's damn good reasons they won't be > told about what I found. ---------------------------------------------------------------------- Tireseas · 2014-05-05 15:20 See, that's a common misconception. OpenBSD does in fact strive for code correctness in the *base* system and they are one of the most secure systems around in terms of default install, all of which are admirable... but people tend to forget that virtually nothing is turned on in that default install beyond SSH and the ports tree isn't covered by the same level of auditing as the base system. In other words, even though OpenBSD ships in a very sane state by default that shouldn't be misunderstood for a magical state of security regardless of admin actions. It's also worth noting that the Linux side of things has had more advanced security frameworks than OpenBSD available for a long time, they just don't ship with them enabled by default for the most part. A lot of that has to do with the difficulty in configuring them correctly. ---------------------------------------------------------------------- kurin · 2014-05-05 19:00 > So they admitted that they destroyed portability. You're welcome to stick with OpenSSL. I don't know why the OpenBSD guys should feel obligated to make sure the software they are adapting to their OS also remain compatible with other OSs. ---------------------------------------------------------------------- garja · 2014-05-05 21:34 > Kirk McKusick So you knew that Kirk McKusick (a major FreeBSD developer) also shouldered responsibility regarding this issue, but you still decided to flame with your "OpenBSD is evil" nonsense? ---------------------------------------------------------------------- qci · 2014-05-05 22:09 Huh? Have you even understood that Theo is blackmailing FreeBSD? He has some problems with what McKusick said before or simply wants money. This is a kind of revenge for something Theo doesn't want to speak publicly about, but is certainly not related to the API usage flaw that OpenSSH is using on OpenBSD but is not available on FreeBSD. ---------------------------------------------------------------------- garja · 2014-05-06 09:48 >Have you even understood that Theo is blackmailing FreeBSD? What supports this conclusion? I'll admit, the whole thread is *very* vague and confusing, but Beck's reply is a criticism of monetizing responsible disclosure and bug ransoming. If I had to guess, Theo and Beck are suggesting that [a sponsor](https://www.freebsdfoundation.org/donate/sponsors) is making FreeBSD "sit on" bugs, and not practice responsible disclosure: >"they're too busy being told to sit on it by their "sponsors" so full disclosure actually seems to happen a lot later." Therefore, Beck says Theo will not responsibly disclose their bug to them, and will sit on it: >"So, if you know of a bug in such an organization (that itself sits on bugs), what would you do? Tell the world for free? Monetize it? or Sit on it?" Theo's phrasing does suggest he feels his hand is forced: >"Sometimes I feel a bit sorry for them (and for him), but then the next minute I don't feel sorry because there's damn good reasons they won't be told about what I found." I'd still consider all this *pure speculation*, however, and Theo and Beck are fools for being so painfully fucking vague. ---------------------------------------------------------------------- qci · 2014-05-06 14:13 Not sure if you are right. We cannot verify either interpretation of us. I am considering that mine is simpler. And I also know how Theo and OpenBSD are handling security in their project. They also hide away fixes that are quite important using harmless commit messages just to make OpenBSD look better. You will certainly understand my scepticism because I saw this once when they produced a bugfix for my report.