NetBSD 9.0 Will Have Performance & Security Improvements

[phoronix]

Phoronix: NetBSD 9.0 Will Have Performance & Security Improvements

The recently releases of FreeBSD 12.0 and DragonFlyBSD 5.4 have been exciting in the BSD space while moving forward there is the NetBSD 9.0 release a ways out on the horizon...

http://www.phoronix.com/scan.php?pag...0-Feature-Plan

[tuxd3v]

ASLR is good,
But what if you have a static library,( without Position Independent Code)?
My opinion is that you will need full Libraries compiled with -fpic otherwise it will only work on Dynamic Linked Libraries..

[Weasel]

ASLR is good,
But what if you have a static library,( without Position Independent Code)?
My opinion is that you will need full Libraries compiled with -fpic otherwise it will only work on Dynamic Linked Libraries..

Then you use relocation.

[tildearrow]

a kernel lead detector,

Huh? The kernel has lead? Are they being eco-friendly now?

[aht0]

NetBSD 9.0 will be bringing updated ZFS file-system support, updated Intel/NVIDIA/Radeon graphics driver support,

Not just "yeah" but "Hell yeah". Now, if only OpenBSD would do it too..
Nvidia updated support has to be Nouveau updated port, it does not have binary driver support from Nvidia.

[brad0]

Not just "yeah" but "Hell yeah". Now, if only OpenBSD would do it too..

Won't happen. CDDL licensed code can't go into the OS.

[aht0]

Won't happen. CDDL licensed code can't go into the OS.

Yeah, just read about it. Well, Hammer 2 then.. whatever besides this sluggish ancient thing there..

[tuxd3v]

Then you use relocation.

Yes,
But IMO, you cannot have statically linked executables that way..they would be always dynamic linked, for relocation..
A static executable file type, can only be of type: 'ET_EXEC'

But when you go with position independent,
You will endup with a type 'ET_DYN', that would mean, be all the time dynamic linking binaries on execution.., for all programs, but even then there are some that you cannot use ASLR, because they need to be of type 'ET_EXEC'