-
Notifications
You must be signed in to change notification settings - Fork 575
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.
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
macOS-related weird errors #170
Comments
I'm not sure why some modules returned ERROR without the full log (preferably with --verbose option). For the FAILED modules, I'd suggest to update the firmware to the latest revision and re-run |
Okay so I re-run with verbose, here is the full logs: iMac 2015:
|
Here is also the version related to the EFI/SMC:
I believe they are up to date since I am using the latest version of macOS. Edit: https://support.apple.com/en-us/HT201518 It looks like my iMac is not even on the Apple EFI/SMC firmwares page. Edit: A benchmark of the same Mac as me from Feb. 2017 is showing the same EFI version: https://browser.primatelabs.com/v4/compute/455770 so I think it's "up to date". |
ERROR results in modules are due to certain functions not implemented in macOS helper yet (cpuid and EFI_supported). Will be adding these functions... For now, I'd recommend booting off of USB drive with Linux and chipsec. |
Due to PR #184 modules which raised exceptions will be now skipped when run on macOS. I'll open a new issue to implement missing functionality these modules rely on so that they can run on macOS. |
Issue #149 tracks this |
Thanks you but what about the FAILED then? I'm unsure using Linux will fix this but I could try when I'll have the time. |
FAILED modules will also be FAILED when you run under Linux. The two modules returned FAILED because they didn't find specific protections they were looking for. common.bios_wp module failed because your Mac doesn't use SMM based protection of EFI firmware. Instead, it apears to be using PR1-PR2 protected ranges (see the second part of bios_wp log) but they don't cover entire EFI region. common.spi_desc module failed because the system doesn't seem to be restricting access to flash descriptor region via permissions defined in the descriptor itself. Based on the log, your Mac appears to be "soft" protection (PR0 range) to protect flash descriptor. This may be ok but without further analysis I cannot tell if it's a sufficient protection or the firmware can be compromised/corrupted. |
Thanks you but considering that it is probably the same results on every Mac I think your script might need some adjustments. |
I have a Mac with different results. |
Hello,
I tried chipsec on my iMac from 2011 and 2015 (SIP was completely disabled then I tried again with "csrutil --without kext" with no success) and on both of these I got the following:
iMac Mid 2011:
iMac Late 2015:
So chipsec.modules.common.bios_wp and chipsec.modules.common.spi_desc failed, here is the details:
So... is it just a false positive or is there a much bigger trouble there?
Regards,
S
The text was updated successfully, but these errors were encountered: