RageLtMan
d02624bbaf
PaX implements valid_mmap_phys_addr_range in the kernel, and the (return 1) hack in chipsec_km.c has a name collision with it. Add another conditional for exposing the definition predicated on whether __HAVE_ARCH_PAX_OPEN_USERLAND is defined in the kernel headers. If it is, dont redefine the original function.
CHIPSEC: Platform Security Assessment Framework
CHIPSEC is a framework for analyzing the security of PC platforms including hardware, system firmware (BIOS/UEFI), and platform components. It includes a security test suite, tools for accessing various low level interfaces, and forensic capabilities. It can be run on Windows, Linux, Mac OS X and UEFI shell. Instructions for installing and using CHIPSEC can be found in the manual.
NOTE: This software is for security testing purposes. Use at your own risk. Read WARNING.txt before using.
First version of CHIPSEC was released in March 2014: Announcement at CanSecWest 2014
Recent presentation on how to use CHIPSEC to find vulnerabilities in firmware, hypervisors and hardware configuration, explore low level system assets and even detect firmware implants: Exploring Your System Deeper
Projects That Include CHIPSEC
Contact Us
Mailing lists:
- CHIPSEC users: chipsec-users
- CHIPSEC discussion list on 01.org
Follow us on twitter