Nicolas Iooss
4f6ed29c84
Several improvements * Drop the detection of EFI through kallsyms. This detection is no longer useful since commit2c0c4c9fd1("Using CONFIG_EFI instead of user defined HAS_EFI (#1036)") replaced `HAS_EFI` with `CONFIG_EFI`. * Use `...-objs-y` and `...-objs-$(CONFIG_...)` logic to choose which `cpu.asm` file is being built. This is something that other modules do in Linux kernel source. * Introduce `quiet_cmd_...` and `cmd_...` definition in order to use the build system of the kernel to compile `cpu.asm` with NASM. This should prevent issues like the one mentioned in2210002bab("Fixed build error on latest Ubuntu") from happening again. Moreover this makes the custom clean command `rm -f ${asm-path}/cpu.o` no longer necessary. * Remove variables which become unused after these changes. Now, all that `Makefile` needs is a kernel directory, specified with `KSRC`. This change has been tested on a test system running Ubuntu 20.10 and on GitHub Actions workers running Ubuntu 16.04, 18.04 and 20.04 on Linux 5.4.0-1040-azure. It has also been compile-tested on many other Linux distributions using a work-in-progress GitHub Actions configuration (https://github.com/fishilico/chipsec/actions/runs/661200380).
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
Release Convention
- CHIPSEC uses a major.minor.patch release version number
- Changes to the arguments or calling conventions will be held for a minor version update
Projects That Include CHIPSEC
Contact Us
Mailing lists:
- CHIPSEC users: chipsec-users
- CHIPSEC discussion list on 01.org
Twitter:
- For CHIPSEC release alerts: Follow us at CHIPSEC Release
- For general CHIPSEC info: Follow CHIPSEC