News for hackers. Stuff that matters.
Re:Why OpenBSD Rocks by snazz on Friday March 01, 2019 @09:20AM (#19280784)
Slightly slower? Mechanical hard drive boot times aren’t the best, but they’re quite acceptable with an SSD. For my desktop use, OpenBSD seems plenty fast.
Re:Why OpenBSD Rocks by futureastronaut on Friday March 01, 2019 @09:48AM (#19281075)
I think you're confusing topics, randomized address space != random disk reads.

Edit: To answer GP's question, you're probably already incurring a cache miss if you're pointer chasing so in most cases there should be no effect on performance.

Re:Why OpenBSD Rocks by oherrala on Friday March 01, 2019 @01:07PM (#19283621)
No, OpenBSD randomizes symbols on kernel and some libraries (for example libc). This randomization is done on boot.

From https://www.openbsd.org/innovations.html:

> Library order randomization: In rc(8), re-link libc.so, libcrypto, and ld.so on startup, placing the objects in a random order. Theo de Raadt and Robert Peichaer, May 2016, enabled by default since OpenBSD 6.0 and 6.2.

and

> Kernel relinking at boot: the .o files of the kernel are relinked in random order from a link-kit, before every reboot. This provides substantial interior randomization in the kernel's text and data segments for layout and relative branches/calls. Basically a unique address space for each kernel boot, similar to the userland fork+exec model described above but for the kernel. Theo de Raadt, June 2017.