Skip to content

added instructions to README #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

added instructions to README #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,3 +5,20 @@ This prevents binaries lacking __PAGEZERO from running.
Among other things, it fixes tpwn and renders a _ton_ of bugs unexploitable.

note: some older binaries (10.4?) could also be affected, but I haven't yet encountered a non-malicious binary lacking PAGEZERO.

## How do I use this?

First, git clone the repository.
Then, open the .xcodeproj
Use Xcode to compile the kext (kernel extension)
Simply put the compiled kext in /Library/Extensions


sudo chmod -R 755 /Library/Extensions
sudo chown -R 0:0 /Library/Extensions
sudo nvram boot-args=kext-dev-mode=1

kext-dev-mode=1 doesn't worsen the security of OS X 10.10.5. loading unsigned kexts is doable without it for the bad guys, but having someone sign a kext so I can make a simple installer would be better.

== Public Service Announcement ==
by the way, on twitter, I've suggested to use SUIDGuard instead of NULLGuard, but I've heard there may be a SUIDGuard bypass. haven't seen it myself, but apparently NULLGuard is not vulnerable. so, if you can do the steps above, do them instead of relying just on SUIDGuard. since i am not able to sign this, (I'd be very glad if someone trusted were to send a pull request with a signed build / installer!) it's better to make sure people at least have what is easier to install, since they may just drop the ball completely on self-patching. If you came here to see how to compile & install NULLGuard, then you should probably do so, and possibly get both SUIDGuard and NULLGuard installed. I am not aware of any incompatibility.