4 ms·
A phenomenal resource on the same subject: https://isopenbsdsecu.re/mitigations/ https://isopenbsdsecu.re/mitigations/
by tptacek 2y ago
A phenomenal resource on the same subject:
https://isopenbsdsecu.re/mitigations/ https://isopenbsdsecu.re/mitigations/
- i80and 2y agoI like this -- despite the clown nose logo, it's actually fair to my eye and is respectful to parts of OpenBSD that are thoughtfully designed.
- chicom_malware 2y agoOpenBSD is thoughtfully designed because it is one of the best examples of "design by dictator" (Theo) - and a small core team - as opposed to design by committee like every other OS out there. Look me in the eye and tell me 90% of changes and unnecessary features in macOS aren't there because some team needs to justify their existence.
- arp242 2y agoI assume you meant to write "disrespectful"?
- i80and 2y agoWhile much of this document is openly disdainful, there are areas like the malloc implementation[1] and features like the atexit hardening[2] where OpenBSD is unambiguously excellent, and it says as much, noting that the latter is a "pretty cool mitigation". I used to do some OpenBSD ports work, and even got a tiny patch into the base system. I love OpenBSD! I don't have an axe to grind here! But it is not above reproach, and I think this site is overall harsh but fair. [1]: https://isopenbsdsecu.re/mitigations/malloc/ https://isopenbsdsecu.re/mitigations/malloc/ [2]: https://isopenbsdsecu.re/mitigations/atexit_hardening/ https://isopenbsdsecu.re/mitigations/atexit_hardening/
- jamal-kumar 2y agoBesides the clown nose on puffy it's honestly just realistic and not all just talking bad like I've seen some people do: https://isopenbsdsecu.re/mitigations/pledge/ https://isopenbsdsecu.re/mitigations/pledge/
- huang_chung 2y ago[flagged]
- tptacek 2y agoYeah I was worried for a second jcs might have something interesting to say about backward- and forward- edge CFI, but then I remembered he's woke and closed the tab before the mind virus could get me.
- huang_chung 2y ago[flagged]
- dcow 2y agoNot to mention that in the general case it seems desirable that a community can exist without needing a CoC. Being disappointed that some community out there is doing just fine without CoC is a /really weird/ point to make in a marketing piece evangelizing how secure OpenBSD is as a technology. To the extent that it feels out of place and yes detracts. Some would even go so far as to argue that OpenBSD is second to none in security because they don’t give a shit about politics and tone in their community. They swiftly dismiss the wasted cycles spent on those in other communities, instead spending their precious time focusing on just being really good. The author sorta misses the plot point there.
- hackernoops 2y ago> /really weird/ That's only if you take CoC enjoyers at their word. It makes perfect sense when you realize it's not about advancing project or community, but rather controlfreak ideology.
- butter999 2y agoa.) They found it off-putting that OpenBSD was "proud" not to have a CoC, in the context of whether they would choose to work with them or to host the website themselves. Consider taking a moment to read the passage in question: https://isopenbsdsecu.re/about/ https://isopenbsdsecu.re/about/ This idea they were surprised a project succeeded without having a CoC is an artefact of this particular discussion, not something the author ever said or implied. It was in the same category as de Raadt swearing at people over email - they didn't anticipate a productive exchange if they reached out. That's it. If someone declares they reserve the right to treat people however they please, and then you observe them treating people in a way you don't want to be treated, and your conclusion is, "I don't think emailing this person is a good use of my time, I'm just going to host this website myself" - I find it hard to understand how anyone would find that objectionable, that seems simple, common sense, and largely neutral. b.) Whenever you have a large group of people collaborating for an extended period of time, you have incidents. There's drama. There's inappropriate behavior. It's just how it goes. It's a Murphy's Law thing. Eventually people sit down and say, "we've gotta set some ground rules." You probably signed a code of conduct at every school you attended and every job you've accepted. I know I have. You can disagree with that without viewing it as a conspiracy. It's a predictable result of being in a large community, and about as ideological as traffic lights.
- justaj 2y agoThis looks quite concerning: https://isopenbsdsecu.re/mitigations/packages/ https://isopenbsdsecu.re/mitigations/packages/
- brynet 2y agoOutdated FUD, OpenBSD's Mozilla port maintainer regularly updates and backports non-ESR Firefox to the -stable tree. https://freshbsd.org/openbsd/ports?q=firefox https://freshbsd.org/openbsd/ports?q=firefox Tor browser bundle is also being updated consistently. https://freshbsd.org/openbsd/ports?q=tor-browser https://freshbsd.org/openbsd/ports?q=tor-browser
- mmooss 2y agoThey are very positive about some mitigations: https://isopenbsdsecu.re/mitigations/pledge/ https://isopenbsdsecu.re/mitigations/pledge/
- tptacek 2y agoSure. I like pledge --- though I think OpenBSD should just do eBPF too.
- mmooss 2y agoMaybe it's just limited resources? In a project that size, I can't imagine having to keep up with the resources of Linux (and to a degree with Apple, Google, and Microsoft) on one side and with all the attackers on the other side. And they want - their reason for being is - higher quality code and security than the rest. Their 'unusual' approach to security might be a distraction they don't need. But maybe it's the only way to hope to pull it off? Maybe they can't do it the GLAM (Google, Linux, Apple, Microsoft) way with OBSD's resources.