41–50 of 208 posts
Earlier quoted context omitted.
All the OS X users seem to be content running Docker in a Linux VM. It's more secure that way too, fitting with OpenBSD mentality :) Doesn't help with the desktop OS part though.
OpenBSD does not yet have kvm support, so you can run qemu, but it'll be very slow.
Earlier quoted context omitted.
Does this mean that I can’t startx on a machine that I rarely use X on? Is a display manager now required for running X? From a security standpoint this makes sense, of course, but how are you supposed to deal with a half-desktop-half-server system?
No. It just means that startx no longer requires root to start X. It removes setuid root from one more executable.
https://www.mail-archive.com/tech@openbsd.org/msg49128.html
Does anyone know if that driver eliminates the need for doing NTP sync in the guest VM?
Still no unified buffer cache. :-( The lack of coherence and memory reuse between mmap(2) and read(2) is my single biggest beef with OpenBSD right now. It's a great system in terms of robustness, documentation, and philosophical unification. It's a shame its kernel still thinks Ronald Reagan is president.
> First release of unwind(8), a validating, recursive nameserver for 127.0.0.1. It is particularly suitable for laptops moving between networks. When systemd-resolvd was first released it was the biggest mistake ever to write a new recursive resolver instead of using unbound or dnsmasq. Also since DNS ".. wasn't broken, so it did not need fixing". I wonder if unwind will be received with the same hostility.
OpenBSD has done a few of these daemons over the years, where they reject existing popular implementations to do their own with their own priorties. I started typing a list but really there are too many, big and small. They tend to have the OpenBSD minimalist, security focused, "no bullshit" approach. It's not very much like systemd.
I'm of the opinion that using C and C++ for future major work where there's not good reasons forcing you to is more trouble than it's worth, but I wouldn't mind if it was all done with the care and attention the OpenBSD developers put into their projects.
Of all of the places a Bee and Puppycat fan might expect to find Natasha Allegri's work ... release art (?!) for OpenBSD 6.5 is perhaps the last I would have expected.
> ROP mitigations in clang(1) have been improved, resulting in a significant decrease in the number of polymorphic ROP gadgets in binaries on i386/amd64. Does anybody know if there's a writeup somewhere? Or what are the commits to look at.
Slides: https://www.openbsd.org/papers/asiabsdcon2019-rop-slides.pdf
Paper: https://www.openbsd.org/papers/asiabsdcon2019-rop-paper.pdf
What!? They don't have OpenBSD t-shirts anymore !?!?!?!?! My old OpenBSD 2.3 tshirt (the wireframe daemon) will die soon and I need a replacement!
https://www.openbsd.org/artwork.html > [...] This artwork emblazoned CDs and posters up until version 6.0, after which we stopped producing product and only release software on the internet. See also [0]; you should be able to make your own t-shirt with official logos, and donate as usual [1,2,3] [0] https://marc.info/?l=openbsd-misc&m=155439809001096&w=2 [1] https://www.openbsd.org/donations.html [2] https://www.ope…
Still no unified buffer cache. :-( The lack of coherence and memory reuse between mmap(2) and read(2) is my single biggest beef with OpenBSD right now. It's a great system in terms of robustness, documentation, and philosophical unification. It's a shame its kernel still thinks Ronald Reagan is president.
That's a feature.