HardenedBSD Gains True Stack Randomization

When we first implemented ASLR for FreeBSD, we implemented the stack randomization portion as a random gap. This means that the base address for the stack remained constant, but where applications started utilizing the stack would change randomly. We have now implemented true stack randomization. The base address for the stack is now randomized. We still utilize a random stack gap on top of true stack randomization to provide further entropy and security. This means that we can effectively achieve 42 bits of entropy for the stack. Compare that to OpenBSD, which utilizes only a gap with 14 bits of entropy. This change breaks both ABI and API and we have bumped the HardenedBSD version up to 26 with this change. We will be doing a new package build to ensure packages are up-to-date with this change.

You can find the git commit here. For more details about how the PaX Team recommends doing stack randomization, take a look here.

RoboAmp 1.01 Released

Due to some changes to google voice, RoboAmp 1.00 (public Defcon 22 release) stopped working. RoboAmp has been updated to adapt to these changes, as well as a few other minor changes. You can get the new version here. If you would like to see more changes to RoboAmp or any of our other SX Labs releases, please drop by for our IRC meeting tomorrow at 4 PM EST.

Site Enhancements

Just a heads up to all, we are working to make the site faster. We've already made some database changes that should have increased the site speed quite a bit. We hope these optimizations will increase the current usage of the forums. We also have plans to move to newer hardware, but we're still working those details out due to our limited budget. Please contact me if you notice any particularly slow areas of the site that you'd like to be faster.

OFACE Roadmap Meeting

For those who are VIP, I have released 0.1.7 and it has now been made available in the SX Labs section of the site for testing.

Also, on May 1st at 6 PM EST I will be doing a meeting to discuss the OFACE Roadmap in IRC. I highly encourage VIP members to attend as well as we want to hear what you think of the Roadmap we are planning.

Major IRC Meeting Tomorrow

Unfortunately shortly after his induction into the SX Crew, Shinobi has gone missing. As a result, n0 has been stepping up to fill his shoes. The high council has finally finished discussing meeting issues, crew issues, and project issues. As a result, we will be having a major IRC meeting tomorrow (04-16-2015) from noon to two (12:00-14:00) EST. We hope that all the crew will be able to attend, as well as many of our more committed community members. If you're a VIP member, please check out the forums for news on some major releases Wink

Introducing secadm 0.2

We're excited to announce the release of secadm version 0.2! We've been working hard on a new star feature: Integriforce.

You can download secadm 0.2 here and the GPG signature here. It was signed with Shawn Webb's GPG key with fingerprint 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE.

Change Log:

  • New feature: Integriforce. executable file integrity through hash checking and enforcement
  • Fix issue linking with prior versions of secadm
  • Fix typos
  • Various cleanups

Announcing Integriforce

This feature provides executable file integrity enforcement. If a rule exists for a given file, that file's hash as defined in the rule is matched against the hash of the file. If the hashes don't match, execution may be disallowed, depending on the configuration settings. Integriforce is an optional, but powerful, feature. Integriforce currently supports SHA1 and SHA256. Both executables and shared libraries are supported. Please note that files that are under Integriforce management cannot be modified or deleted. The ruleset will need to be flushed prior to modifying or deleting the file.

When we did our call for testing (and thank you to those who tested!), only executable files were checked, not their dependencies (shared objects). With HardenedBSD v18 (sysctl hardening.version) and secadm 0.2, we now support checking the dependencies. This required a change in the runtime linker (also known as the RTLD) that calls into Integriforce if it is available. Additionally, there is a new kernel feature sysctl exposed, kern.features.integriforce.

Syndicate content