Earlier quoted context omitted.
Wait, what? No they don't. The author is an OpenBSD person and calls out several mitigations as clever and worthwhile.
No, the author isn't an "OpenBSD person".
OpenBSD 7.9
231–240 of 314 posts
Re: OpenBSD 7.9
#232With all the security issues constantly being uncovered in other Operating Systems - which will only accelerate with Ai - it’s time everyone considers OpenBSD. Their decades-long security-focus is second to none. We have fully converted from Ubuntu/Debian to OpenBSD. No looking back.
Is OpenBSD actually more secure than Linux? I have not been able to find any data to support this—only some vague opinions.
Re: OpenBSD 7.9
#233Earlier quoted context omitted.
Is OpenBSD actually more secure than Linux? I have not been able to find any data to support this—only some vague opinions.
No, not really. Linux has better options available and is significantly stronger when configured correctly. The OpenBSD approach ls largely based around eliminating bugs in the first place, but isn't as strong at limiting an attacker that successfully exploited a bug they missed or weren't responsible for.
OpenBSD has a pretty long history of eg. limiting attacks through compile time mitigations while making them more usable for every day use compared to specialized "high security" Linux distributions. This can also be seen in patches of third party software (in the ports (packages) system) that often have patches so the code can live with these limitations.
One example of such a mitigation is W^X. Implemented in OpenBSD in 2003, copied later by Windows, Linux and the other BSDs (incl. macOS).
https://en.wikipedia.org/wiki/W%5EX
More recently of course pledge and unveil were also added.
Also in 2003 OpenBSD was also the first mainstream (no research or test OS) that implemented strong ASLR that in 2005 was supported in Linux through third party patch sets.
For a list, see here:
https://www.openbsd.org/innovations.html
Many things were later picked up by Linux distributions, kernel patchsets, compilers, etc.
Re: OpenBSD 7.9
#234OpenBSD 7.9 release artwork by Lyra Henderson https://www.openbsd.org/images/PinkPuffy.png https://www.openbsd.org/images/puffy79.gif Release song is "Diamond in the Rough" - Composed & produced by Bob Kitella. https://www.openbsd.org/lyrics.html#79 Apparel (t-shirts, so far): https://openbsdstore.com/
Re: OpenBSD 7.9
#235Re: OpenBSD 7.9
#236Earlier quoted context omitted.
Interesting to see OpenBSD continuing to gain hardware support. I've been running it on a small home server for DNS/DHCP and the stability is remarkable. The man years of auditing really show.
"Interesting" Is this an AI-generated comment It was originally [flagged] and [dead]
FWIW my guess is you're right - this user looks like a bot based on this comment and their other one; I've noticed that somewhat-vacuous praise for a post is a bot tendency. Although it's also a human tendency, so maybe too soon to tell. What a world.
Re: OpenBSD 7.9
#237The big news for some of us is that Exim has been dropped from ports. Here is a good article about transitioning from Exim to OpenSMTPD: https://nxdomain.no/~peter/time_for_opensmtpd.html I tried using OpenSMTPD a long time ago, shortly after it came out, but things were not stable enough. I guess it is time to give it another go...
I'm happy with it. Been running OpenSMTPd for many years at this point, on both OpenBSD and Linux, and I have no complaints.
Re: OpenBSD 7.9
#238Earlier quoted context omitted.
The Data: Compare the number of CVE vulnerability trends over time between Linux: https://www.cvedetails.com/vendor/33 and OpenBSD: https://www.cvedetails.com/vendor/97 It's not even close! It's nearly two orders of magnitude higher for Linux. This isn't anecdotal or “vague opinion” CVEs are facts. You can ask the follow-up question: Why is that? And there are many reasons. It could just be that Linux having more use…
> This isn't anecdotal or “vague opinion” CVEs are facts No they aren't, they're data. Your source shows the amount of Linux CVEs in 2024 are an order of magnitude higher than the amount of Linux CVEs in 2023. Does that mean Linux became way more insecure in 2024? You imply it does, but that's obviously not true. What happened is that Linux changed how they report CVEs [0]. Just like your source doesn't say anything…
The OP stated they couldn’t find any data to compare the relative security of Linux vs. OpenBSD.
CVEs are independently, objectively verifiable and provable data. This is the dictionary definition of a verified “fact”. It’s not anyone’s opinion. You don’t have to like it or me.
Love you all.
Re: OpenBSD 7.9
#239Earlier quoted context omitted.
My point is that you shouldn't have to do this! I've already done this twice for this box. Its disk is half empty, and the used space is 75% compounding useless bloat: - 50% of the used space are package sets I never asked for. - The stuff I did ask for is somehow 2x larger than it needs to be, since they don't randomize binaries in place. - If they'd actually follow their own filesystem hierarchy standards, and stop…
Yeah it sucks when partitions that were sized 8-10 years ago are no longer adequate. I've hit the "/usr is too small to complete an upgrade" trap myself. When that happened I rejected the installer's partition suggestions and made /usr substantially larger (this is also necessary if you're going to be building large ports, which also happens under /usr). So far that has worked for me. Some people would also argue tha…
Similarly, if fsck -y is frequently required, maybe just run that way all the time instead of failing to boot, or fix the root problem. I doubt many sers are taking block level backups for forensic repair in case they need to hand assemble inodes.
Anyway, I wish them well. I want a simple, correct and rock solid OS for this sort of use case. The three pillars of computer security are confidentiality, integrity and availability. Hopefully they’ll focus a bit more on the latter two things than they have recently.