Slashdot Mirror
Security Upgraded For NetBSD-amd64 with Kernel ASLR Support (netbsd.org)
24 years after its release, NetBSD is getting a security upgrade -- specifically, Address Space Layout Randomization (ASLR). An anonymous reader writes:
Support for Kernel ASLR was added on NetBSD-amd64 a few weeks ago. KASLR basically randomizes the address of the kernel, and makes it harder to exploit several classes of vulnerabilities [including privilege escalations and remote code execution]. It is still a work-in-progress, but it's already fully functional, and can be used following the instructions on this post from the NetBSD blog. It will be available starting from NetBSD 9, but may be backported to NetBSD 8 once it is stabilized.
NetBSD says they're the first BSD system to support ASLR.
NetBSD says they're the first BSD system to support ASLR.
it's one of the reasons Linux is being phased out. It will eventually be an app that runs inside the much more secure systemd framework.
OpenBSD doesn't have KASLR. It recently got KARL, but that's different. OpenBSD has had ASLR support for userland (PIE and PIC binaries and libs).
The scary thing is that some Rust advocates actually say stuff like this without any sense of irony, not as a troll.
Sadly, similar to JavaScript, Rust has enough marching morons behind it to stick around for a long time to come.
I'm not 'trolling'. I'm completely serious. Maybe you haven't used Rust yet but it's the next generation of programming. It offers unparalleled safety without sacrificing performance. That's the beauty of Rust's zero cost abstractions. Rust is what languages like C, C++, Java and C# should have been. It's still a young language but as more people learn about it we're seeing its usage skyrocket. Mozilla is already using Rust for parts of Firefox. I think we will see the same thing happen to most software projects. They will gradually use more and more Rust until all of the original C or C++ or Java or C# code is gone. If you're a programmer and you're not using Rust already, then you likely soon will be. Rust is taking the programming world by storm.
You will be glad to know that I've taken your words, pasted them into MS Word, prettied them up with a fancy font, printed them on a nice piece of paper, framed that paper and hanged it the wall of my office for the years to come. Thank you for this inspiration.
Your Friend in Rust,
FootNipple
That statement may be debatable for some languages. But I've looked at Rust. It can't do what C can. Sorry. You can't write low level code (and I don't mean something as high level as the Linux kernel) in it. Go ahead, try writing a bootloader in Rust. Let me know how it turns out.
The reality is that most good C programmers rarely have pointer fumbles. The fact of the matter is that lots of software we rely on (both open source and closed) are not written by even marginal programmers. There is this philosophy that if a good programmer writes the foundation the less skilled can follow along and product good software. It kinda works; to a point.
But even if all pointer bugs magically go away to equate this with "more secure" software is insane. The security hole landscape is vast. Really vast: Timing attacks, hardware flaws, surprising backchannels, social engineering. Yes, ASLR is a good defense. But claiming that Rust is going to fix security or just pushing it in this marketing style hype-fest is a detriment to just how hard getting security right is.
PHP is way more popular. Why not go the popularity route? It means there are more people proficient in the language!
No it's not scary. Every language, OS and many other projects when new have some people who are very enthusiastic and that's a good thing. It's understandable and normal in a growing thriving community.
The Rust community at large usually says that if you have a large existing code base it is maybe not worth rewriting. However Rust integrates well into existing C projects and sometimes it's worth considering replacing problematic components in a larger project with Rust implementations, sometimes not. One example is Dropbox that's mostly a Go shop and will remain so, but they rewrote the bits that do bulk data transfers in Rust.
Just get over the few super enthusiasts, be happy for them and if you are starting a new project make an informed decision, as opposed to one based on defensiveness or entrenching. Rust have many impressive features it's well worth considering.
It's hard to follow others when you're in a constant state of dying.
#DeleteFacebook
Make it PHP + Javascript to be absolutely sure it's 100% safe.
#DeleteFacebook
So what's the alternative to Javascript for the Web? Java, Flash and Silverlight are not valid options.
#DeleteFacebook
PIC binaries? What about ATmega or at least ATtiny?
#DeleteFacebook
Now I can stop worrying about my toaster getting hacked - no, the bread kind, not these.
It must have been something you assimilated. . . .
The Linux kernel finally has KASLR enabled by default in the 4.12 kernel – in July 2017 [1]
The Fine Summary is poorly written, making it sound like NetBSD is way behind the times. But the truth is it's only three months later than Linux. Not bad IMO when you consider how many people work on the NetBSD kernel versus how many work on the Linux kernel.
[1] https://kernelnewbies.org/Linu...
One can absolutely write low level code in Rust. There are examples available. Most parts of Linux are high-ish level but many parts are low level - or if doing actual interfacing with hardware isn't low level I wonder what you consider low enough. Microcode? That would be a table for hardware to interpret.
I am a Mac user, yes; I've used Macs for about 19 years, including pre-OS X.
I'm also a developer with over 24 years of linux experience, with a half decade of solaris in there too.
I'm not a fanboi. But I am pointing out that macOS is a BSD derivative with KASLR (unless there is some subtlety in the implementation that NetBSD is claiming is unique, or that there is some limitation in the macOS implementation I don't know about; either or both seem possible.)
Glad to see you can do HTML though; get you with your bolds and italics. When you're older they will let you write little programs.
https://hardenedbsd.org/conten...
AFAIK, this ALSR-thingy was the reason it was originally forked-off.
Windows 2000 - from the guys who brought us edlin
Sorry, but that's not how it works. Linus doesn't decide what gets enabled, the distribution developers do. Your statement is literally nonsensical.
Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
Mmmm... KASLR...
Escher was the first MC and Giger invented the HR department.
So what's the alternative to Javascript for the Web? Java, Flash and Silverlight are not valid options.
The future seems to be WebAssembly. Essentially it'll make the web more desktop-like, write in the language you want and compile. You'll still need some Javascript to interact with the assembly, but much less.
Live today, because you never know what tomorrow brings
ASLR in userspace increases work factor, but attacks such as BROP and successors can bypass it. It can also suffer from various weakness - for example the StageFright vulnerability on Android was made worse by the fact that, on 32-bit systems, jemalloc allocated in large chunks (and didn't randomise within a chunk) and so you ended up with 8 bits of entropy, and the automatic restart meant that, on average, you could guess (and get root privilege arbitrary code execution) in 128 attempts.
KASLR, in contrast, is entirely snake oil. Kernel interfaces were never designed to avoid leaking kernel addresses to unprivileged code, because kernel security doesn't rely on addresses being secret, it relies on kernel addresses being unusable from userspace. The kernel-userspace interfaces (system calls and ioctls) provide a large number of ways of finding kernel addresses from userspace. If your threat model is protecting the OS from a malicious device via DMA or a malicious hypervisor, then it's even weaker.
I am TheRaven on Soylent News